cceh / imdi-environment-for-cmdi-maker Goto Github PK

When adding a local used content language or actor language (ISO codes qaa-qtz), the user should get the chance to specify a custom name for this language, just like in the ELDP environment.

feature request: optional preservation of hyphens in Session Names (following thwe discussion with Swintha via the support mailing list)

When generating Sessions output with the CMDI profile "imdi-session",
invalid XMLs are generated.
When developing the app, I oriented myself towards Arbil, not realizing that Arbil produces invalid XML too, when not checking for XML conformance and patch invalidites manually.
imdi_cmdi_generator.js should take the XSD of the "imdi-session" profile as template, not XML files produced by Arbil.

imdi-session XSD: http://catalog.clarin.eu/ds/ComponentRegistry/rest/registry/profiles/clarin.eu:cr1:p_1271859438204/xsd

This does not concern IMDI files or CMDI Corpus files.

"undefined Actors importiert" when actors file (actors.json) attempts to be imported.

Description:
1# cvc-complex-type.3.2.2: Attribute 'mimeType' is not allowed to appear in element 'ResourceType'.
2# cvc-complex-type.2.4.a: Invalid content was found starting with element {"http://www.clarin.eu/cmd/":Session}'. One of '{"http://www.clarin.eu/cmd/":IsPartOfList}' is expected.
The element type "Resources" must be terminated by the matching end-tag "".
3# cvc-complex-type.2.4.a: Invalid content was found starting with element '{"http://www.clarin.eu/cmd/":Description}'. One of '{"http://www.clarin.eu/cmd/":descriptions}' is expected.
4# cvc-enumeration-valid: Value '' is not facet-valid with respect to enumeration '[Unknown, Unspecified, Original, Analysis, Translation, Commentary, Criticism, Annotation]'. It must be a value from the enumeration.

display environment version.

imdi_generator.js:147 Uncaught TypeError: Cannot read property 'age' of undefined at imdi_generator.js:147 at forEach (helpers.js:536) at createSession (imdi_generator.js:143) at imdi_generator.js:425 at forEach (helpers.js:536) at new imdi_environment.imdi_generator (imdi_generator.js:423) at Object.imdi_environment.workflow.(:8080/anonymous function).my.generate (http://localhost:8081/src/js/imdi_output.js:193:21) at Object.imdi_environment.workflow.(:8080/anonymous function).my.view (http://localhost:8081/src/js/imdi_output.js:136:6) at Object.my.view (app.js:708) at HTMLDivElement.<anonymous> (app.environments.js:271)

You can use the resources-tab to create new sessions based on selected files. This basically adds the file names to the resources-section of the new session.

Additionally, when choosing to "create one session per file" along with the option "EAF" the file name of the EAF-file (without file extension) is automatically filled in to the session-name-field of the profile.
This makes it significantly easier to manage the collection especially when creating large numbers of sessions.

I expect the same behaviour when using the function "create one session per file" with the options "selected files", "WAV", "MP4" or "MPG". Instead those options result in the creation of "unnamed sessions". see screenshots below.

I suspect this is an IMDI-environment issue because the described expected behaviour is 'correctly' implemented in the ELDP-environment.

Value '' is not facet-valid with respect to enumeration '[Unknown, Unspecified, Africa, Asia, Europe, Australia, Oceania, North-America, Middle-America, South-America]'. It must be a value from the enumeration.

ELAR sent us a cmp-file Nov 28 to illustrate the problem.
I can recreate the problem. I was unable to export as zip archive.
Nothing happens when you click the button.

When i delete a couple of session it suddenly works. May be has something to do with the number of sessions.

The XML-Output generated by the CMDI Maker when producing CMDI files from the imdi-session profile is missing the ref-attribute that refers to the respective element in the header section

more like
<WrittenResource ref="res_q942398232548023042390429034">
instead of just
<WrittenResource>

EAF and PFSX mimetypes should be recognized for uploaded files.
An overview of accepted files types and formats can be found at: [https://www.mpi.nl/corpus/html/lamus/apa.html](MPI-archive Filetype and Fileformats)