-
The `VloConfig.xml` file specifies the locations of a number of components that are parsed and used as vocabularies during import:
``` !xml
...
http://catalog.clarin.eu/ds/ComponentRegistry/rest/r…
-
A workflow (TODO: add link to relevant issue or other description) will be developed (primarily by ACDH) for maintaining facet maps based on manual edits by domain experts, synchronisation with CLAVAS…
-
Add a feature "audioFormat (0-n)" to "speechCorpus":
audioFormat (0-n)
- speechCoding (0-1; c) ()
- samplingFrequency (0-1;f ) (http://hdl.handle.net/11459/CCR_C-2577_73344cc2-f341-8842-bcf7-48e5267a…
-
The "totalSize" fields must hierarchically be under the 'resource' instead of directly under 'collection'
-
Thomas reports the following in the results of the test plan:
>External vocabulary for ISO 639-3 can’t be set: “All items in a vocabulary should have a unique value. Please remove these duplicate val…
-
When editing an item as new, remove the successor header item if it is present. A new component should never be born with a successor set, let alone inherit it.
For the back end part, see https://g…
-
Facilitating for https://github.com/clarin-eric/component-registry-front-end/issues/63, add a call to retrieve the results of 'find-concepts' filtered by concept scheme.
Concepts can be obtained vi…
-
https://trac.clarin.eu/ticket/166
> An imported component specification can have elements without !ValueScheme attributes. In the editor form, this is a required field. When an element has no type se…
-
Currently, the edit option is only available in the private space. However, it should now also be possible to edit 'development' components and profiles that have been published (as draft, see #72)
-
Provenance is defined as single (0-1) now.
Change this into multiple (0-n).
Implication 1: adapt the XML specification in the Clarin component registry
Implication 2: adapt the XML output code in RU…