lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2022-02-24T09:38:40Zhttps://gitlab.gwdg.de/lido/development/-/issues/143please remove from cc2022-02-24T09:38:40ZMathias Goebelplease remove from cci am getting noticed at your new issues in the cc section. can someone pls remove from the templates? thx.i am getting noticed at your new issues in the cc section. can someone pls remove from the templates? thx.https://gitlab.gwdg.de/lido/development/-/issues/2G21 – display element in relatedWorkSet2021-12-20T14:48:29Zmmarkus1G21 – display element in relatedWorkSetWiki: https://wiki.dnb.de/pages/viewpage.action?pageId=135793641Wiki: https://wiki.dnb.de/pages/viewpage.action?pageId=135793641https://gitlab.gwdg.de/lido/development/-/issues/133Optimize CSS spacing in the accompanying document (terminology recommendations).2021-12-17T12:12:19ZHanna-Lena StolzOptimize CSS spacing in the accompanying document (terminology recommendations).mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/131Introduction text for accompanying document (terminology recommendations)2021-12-17T12:02:06ZHanna-Lena StolzIntroduction text for accompanying document (terminology recommendations)Introduction text for accompanying document (terminology recommendations) would be helpful. Explain, what this document is about etc
Must be implemented in the transformationIntroduction text for accompanying document (terminology recommendations) would be helpful. Explain, what this document is about etc
Must be implemented in the transformationmmarkus1Hanna-Lena StolzJutta Lindenthalmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/132Remove XSD heading complexTypes from page and menu2021-12-17T08:59:11ZHanna-Lena StolzRemove XSD heading complexTypes from page and menuLIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/134Schematron Rules do not apply to sch:assert2021-12-16T17:53:06Zmmarkus1Schematron Rules do not apply to sch:assertThe transformation does only include schematron rules that have sch:extends. A transformation for sch:assert need to be implemented.The transformation does only include schematron rules that have sch:extends. A transformation for sch:assert need to be implemented.mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/130Change element sequence in <place> element2021-11-22T11:15:42ZJutta LindenthalChange element sequence in <place> elementlido:partOfPlace should be the last sub-element within lido:place, otherwise nestings of lido:place are almost anreadable and extremely difficult to edit.lido:partOfPlace should be the last sub-element within lido:place, otherwise nestings of lido:place are almost anreadable and extremely difficult to edit.LIDO 1.1 finalmmarkus1mmarkus12021-11-16https://gitlab.gwdg.de/lido/development/-/issues/128RelatedEventSet and RelatedEvent have the same label2021-11-15T10:42:53ZGudrun KnausRelatedEventSet and RelatedEvent have the same labelIn http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.pdf the element RelatedEventSet has the label Related Event and so does the element Related Event. Shouldn't be the label Related Event Set? (similar to Event Set?)In http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.pdf the element RelatedEventSet has the label Related Event and so does the element Related Event. Shouldn't be the label Related Event Set? (similar to Event Set?)Hanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/116displayDate needed for vitalDatesActor2021-09-23T12:09:39ZGudrun KnausdisplayDate needed for vitalDatesActorIn the EODEM sample file I have found the following:
```
<lido:vitalDatesActor>
<lido:earliestDate>active about 1506</lido:earliestDate>
<lido:latestDate>died 1576</lido:latestDate>
</lido:vitalDatesActor>
```
My first guess w...In the EODEM sample file I have found the following:
```
<lido:vitalDatesActor>
<lido:earliestDate>active about 1506</lido:earliestDate>
<lido:latestDate>died 1576</lido:latestDate>
</lido:vitalDatesActor>
```
My first guess was to change it into something like this:
```
<lido:vitalDatesActor>
** <lido:displayDate xml:lang="en">active between 1506 and 1576</lido:displayDate>**
<lido:earliestDate>1506</lido:earliestDate>
<lido:latestDate>1576</lido:latestDate>
</lido:vitalDatesActor>
```
but a) this it not valid and b) the type of date still needs to be characterized.
So it might look like this:
```
<lido:vitalDatesActor lido:type="http://terminology.lido-schema.org/lido00819">
** <lido:displayDate xml:lang="en">active between 1506 and 1576</lido:displayDate>**
<lido:earliestDate lido:type="estimated_date">1506</lido:earliestDate>
<lido:latestDate lido:type="estimated_date">1506</lido:latestDate>
</lido:vitalDatesActor>
<lido:vitalDatesActor lido:type="ttp://terminology.lido-schema.org/lido00787">
<lido:earliestDate lido:type="estimated_date">1576</lido:earliestDate>
<lido:latestDate lido:type="estimated_date">1576</lido:latestDate>
</lido:vitalDatesActor>
```
What do you think?Jutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/71<gml> further reading: Linking does not work2021-09-02T12:28:52ZHanna-Lena Stolz<gml> further reading: Linking does not workLinking does not work ("[For further documentation on GML refer to](www.opengis.net/gml/)")
<br>XSD correction. Where should the link point? => TODO: research and correct!Linking does not work ("[For further documentation on GML refer to](www.opengis.net/gml/)")
<br>XSD correction. Where should the link point? => TODO: research and correct!Sophie RölleSophie Röllehttps://gitlab.gwdg.de/lido/development/-/issues/118Align description for <administrativeMetadata> and <descriptiveMetadata>2021-09-02T12:22:05ZHanna-Lena StolzAlign description for <administrativeMetadata> and <descriptiveMetadata>Explain different cardinality in root and child elementExplain different cardinality in root and child elementLIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolz2021-08-01https://gitlab.gwdg.de/lido/development/-/issues/123sourceAppellation2021-08-25T08:12:24ZGudrun KnaussourceAppellationA titleSet can contain a title in different languages, each specified by the individual language attribute. In case each translation of the title stems from a different source I need to create a new titleSet for each title, otherwise the...A titleSet can contain a title in different languages, each specified by the individual language attribute. In case each translation of the title stems from a different source I need to create a new titleSet for each title, otherwise the titleSet becomes invalid.
Look at this invalid example:
<lido:titleSet lido:type="http://vocab.getty.edu/aat/300417194">
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="en">
Sketch: The Death of Henry IV and the Proclamation of the Regency</lido:appellationValue>
<lido:sourceAppellation>https://rkd.nl/explore/images/217905</lido:sourceAppellation>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="fr">
L'Apothéose de Henri IV et la proclamation de la régence de Marie de Médicis, le 14 mai 1610</lido:appellationValue>
<lido:sourceAppellation>sampleValue</lido:sourceAppellation>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="nl">
Olieverfschets: De dood en apotheose van Hendrik IV en het overdragen van het regentschap
aan Maria de' Medici, 14 maart 1610</lido:appellationValue>
<lido:sourceAppellation>sampleValue</lido:sourceAppellation>
</lido:titleSet>
In comparison to this valid snippet:
<lido:titleSet lido:type="http://vocab.getty.edu/aat/300417194">
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="en"
>oil sketch: The death and apothesis of Henry IV and the proclamation of the regency of
Maria de' Medici, 14 March 1610 </lido:appellationValue>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="fr">
L'Apothéose de Henri IV et la proclamation de la régence de Marie de Médicis, le 14 mai
1610</lido:appellationValue>
<lido:appellationValue lido:pref="http://terminology.lido-schema.org/lido00169" xml:lang="nl">
Olieverfschets: De dood en apotheose van Hendrik IV en het overdragen van het regentschap
aan Maria de' Medici, 14 maart 1610 </lido:appellationValue>
<lido:sourceAppellation xml:lang="de"
>https://rkd.nl/explore/images/217905</lido:sourceAppellation>
</lido:titleSet>
Is there a chance to make the sourceAppellation element repeatable within the same titleSet?Hanna-Lena StolzRegine SteinJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/119Terminology/Format recommendation: accompanying document2021-08-11T11:23:26ZHanna-Lena StolzTerminology/Format recommendation: accompanying documentDesignations and links have to be consolidated.
[Wiki](https://wiki.dnb.de/pages/viewpage.action?pageId=202447123)Designations and links have to be consolidated.
[Wiki](https://wiki.dnb.de/pages/viewpage.action?pageId=202447123)LIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/70<gml> error in May contain2021-08-11T09:48:12ZHanna-Lena Stolz<gml> error in May containTransformation error in May contain for gml: *. Links don't work (http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#gml
)
<br>**TODO**: Transformation! all external elements should be linkedTransformation error in May contain for gml: *. Links don't work (http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#gml
)
<br>**TODO**: Transformation! all external elements should be linkedmmarkus1Jutta LindenthalSophie Röllemmarkus1https://gitlab.gwdg.de/lido/development/-/issues/100Rename "For an attribute the element holds" in Terminology/Format recommendation2021-08-11T09:45:20ZJutta LindenthalRename "For an attribute the element holds" in Terminology/Format recommendationRename the phrase "For an attribute the element holds" in Terminology/Format recommendation for LIDO elements into:
"For the type attribute"
Example <classification>
Terminology/Format recommendation For the element: Linked open vocabul...Rename the phrase "For an attribute the element holds" in Terminology/Format recommendation for LIDO elements into:
"For the type attribute"
Example <classification>
Terminology/Format recommendation For the element: Linked open vocabulary for Classification
For the type attribute: LIDO Terminology for Classification typemmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/98Delete "For the element" in Terminology/Format recommendation for all LIDO at...2021-08-10T19:31:08ZJutta LindenthalDelete "For the element" in Terminology/Format recommendation for all LIDO attributesTerminology/Format recommendation refers to the described attribute, not to an element. Since the recommendation concerns the attribute only, an explicite reference is unnecessary.Terminology/Format recommendation refers to the described attribute, not to an element. Since the recommendation concerns the attribute only, an explicite reference is unnecessary.mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/124style new class for elements which can not be expanded in tree view/add button2021-08-09T13:26:50ZHanna-Lena Stolzstyle new class for elements which can not be expanded in tree view/add buttonstyle new class ("ground") for elements which can not be expanded in tree view
add button "expand all" and "hide all"style new class ("ground") for elements which can not be expanded in tree view
add button "expand all" and "hide all"LIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/73<actor>: link under further information broken2021-06-29T05:53:29ZHanna-Lena Stolz<actor>: link under further information broken“Equivalents” links differently than the rest,
<br>Transformation error in "Equivalents in other schemas"“Equivalents” links differently than the rest,
<br>Transformation error in "Equivalents in other schemas"LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/72<recordInfoSet>: link in recommendation is broken2021-06-29T05:53:12ZHanna-Lena Stolz<recordInfoSet>: link in recommendation is brokenhttp://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#recordInfoSet
<br>For an attribute the element holds:
LIDO Terminology for Record Metadata Information Set type_ (http://www.lido-schema.org/schema/v1.1/accompanying-docu...http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#recordInfoSet
<br>For an attribute the element holds:
LIDO Terminology for Record Metadata Information Set type_ (http://www.lido-schema.org/schema/v1.1/accompanying-document.html#recordInfosSet_type)
Remove “s” ("recordInfo**s**Set)in the linkHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/122resourceID: Change repeatablilty2021-06-25T09:47:59ZHanna-Lena StolzresourceID: Change repeatabliltyRepeatabilty needs to be adjusted to minOccurs="unbounded"Repeatabilty needs to be adjusted to minOccurs="unbounded"LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolz