lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2022-03-29T07:35:43Zhttps://gitlab.gwdg.de/lido/development/-/issues/146lido:term: add reference to attributes in HTML documentation2022-03-29T07:35:43ZAngela Kailuslido:term: add reference to attributes in HTML documentationhttp://lido-schema.org/schema/v1.1/lido-v1.1.html#term does not hold any references to the attributes that may be used with this element.
Add links to fitting attributes:
http://lido-schema.org/schema/v1.1/lido-v1.1.html#addedSearchTer...http://lido-schema.org/schema/v1.1/lido-v1.1.html#term does not hold any references to the attributes that may be used with this element.
Add links to fitting attributes:
http://lido-schema.org/schema/v1.1/lido-v1.1.html#addedSearchTerm
http://lido-schema.org/schema/v1.1/lido-v1.1.html#encodinganalog
http://lido-schema.org/schema/v1.1/lido-v1.1.html#label
http://lido-schema.org/schema/v1.1/lido-v1.1.html#prefhttps://gitlab.gwdg.de/lido/development/-/issues/145resourceRelType: Terminology recommendation link adresses wrong element, add ...2022-03-11T15:07:38ZAngela KailusresourceRelType: Terminology recommendation link adresses wrong element, add terminology recommendationhttps://lido-schema.org/schema/v1.1/lido-v1.1.html#resourceRelType: Terminology recommendation link adresses the wrong element, resourceType. Correct terminology recommendation for resourceRelType does not exist yet .
Add sequence in t...https://lido-schema.org/schema/v1.1/lido-v1.1.html#resourceRelType: Terminology recommendation link adresses the wrong element, resourceType. Correct terminology recommendation for resourceRelType does not exist yet .
Add sequence in terminology recommendation, link up correctly.https://gitlab.gwdg.de/lido/development/-/issues/144nationalityActor: broken link in HTML documentation2022-03-10T18:56:12ZAngela KailusnationalityActor: broken link in HTML documentationhttps://lido-schema.org/schema/v1.1/lido-v1.1.html#nationalityActor
Link in Sequence "For the type attribute:
LIDO Terminology for Type of Nationality Actor" creates error "Not Found.
The requested URL was not found on this server."https://lido-schema.org/schema/v1.1/lido-v1.1.html#nationalityActor
Link in Sequence "For the type attribute:
LIDO Terminology for Type of Nationality Actor" creates error "Not Found.
The requested URL was not found on this server."https://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/142linkResource_type: Add and link terminology recommendation for codec resource2022-02-24T09:39:21ZAngela KailuslinkResource_type: Add and link terminology recommendation for codec resourceIn http://lido-schema.org/schema/v1.1/lido-v1.1.html#linkResource there is a link to http://lido-schema.org/documents/terminology-recommendation.html#codecResource, but the sequence does not exist in the terminology recommendation.
Ad...In http://lido-schema.org/schema/v1.1/lido-v1.1.html#linkResource there is a link to http://lido-schema.org/documents/terminology-recommendation.html#codecResource, but the sequence does not exist in the terminology recommendation.
Add sequence in terminology recommendation, link up as specified above.
# Severity
How much impact does this bug have on further development?
* [x] Minor
* [ ] Major
* [ ] Critical
* [ ] Blockerhttps://gitlab.gwdg.de/lido/development/-/issues/141recordInfoSet_type: Link up existing terminology recommendation2022-02-24T09:39:08ZAngela KailusrecordInfoSet_type: Link up existing terminology recommendation# Description
https://lido-schema.org/schema/v1.1/lido-v1.1.html#recordInfoSet does not contain a terminology recommendation for the type attribute. The recommendation is available.
Specify if the type attribute is required or optional....# Description
https://lido-schema.org/schema/v1.1/lido-v1.1.html#recordInfoSet does not contain a terminology recommendation for the type attribute. The recommendation is available.
Specify if the type attribute is required or optional.
## I expected the following to happen:
Adapt text and link up to http://terminology.lido-schema.org/recordInfoSet_type. Necessary for consistency of LIDO documentation and user support.
# Severity
How much impact does this bug have on further development?
* [ ] Minor
* [x] Major
* [ ] Critical
* [ ] Blocker
# Related Tickets
Add related issues if applicable.https://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/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/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/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/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/129Source for eventDate2021-10-27T13:27:41ZGudrun KnausSource for eventDateThe dating of an event, especially the production of an object, is often controversial. Most of the time it cannot be derived from the object itself, but must be taken from a literary source. Therefore, it is desirable to cite this sourc...The dating of an event, especially the production of an object, is often controversial. Most of the time it cannot be derived from the object itself, but must be taken from a literary source. Therefore, it is desirable to cite this source within the eventDate element.https://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/127Clarify scope and description of creditLine element2021-11-12T11:45:28ZMarco KlindtClarify scope and description of creditLine elementsee https://wiki.dnb.de/pages/resumedraft.action?draftId=217523724&draftShareId=bd8bf4af-712c-467a-b6cc-10ad55c8b911see https://wiki.dnb.de/pages/resumedraft.action?draftId=217523724&draftShareId=bd8bf4af-712c-467a-b6cc-10ad55c8b911Marco KlindtMarco Klindthttps://gitlab.gwdg.de/lido/development/-/issues/126Content of tei:ab type="furtherReading" not properly separated in HTML output2021-10-14T08:38:09ZDetlev BalzerContent of tei:ab type="furtherReading" not properly separated in HTML output# Description
If `tei:ab type="furtherReading"` contains multiple `tei:ref` elements, then these are transformed into a single `a class="further-reading-link"` element, leading to a concatenation of link targets in the HTML view.
## I e...# Description
If `tei:ab type="furtherReading"` contains multiple `tei:ref` elements, then these are transformed into a single `a class="further-reading-link"` element, leading to a concatenation of link targets in the HTML view.
## I expected the following to happen:
This snippet from the XSD
```
<tei:ab type="furtherReading">
<tei:ref target="https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html">CDWA 8. Inscriptions/Marks
</tei:ref> >
<tei:ref target="https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html#transcription">8.1. Inscription Transcription or Description
</tei:ref>
</tei:ab>
```
should be rendered in HTML as follows:
```
<a class="further-reading-link"
href="https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html
target="_blank">CDWA 8. Inscriptions/Marks 8.1</a> >
<a class="further-reading-link"
href="https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html#transcription"
target="_blank">8.1. Inscription Transcription or Description</a>
```
## On the contrary, I observed:
```
<a class="further-reading-link"
href="https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html
https://www.getty.edu/research/publications/electronic_publications/cdwa/11inscriptions.html#transcription"
target="_blank"> CDWA 8. Inscriptions/Marks 8.1. Inscription Transcription or Description</a>
```
# How to reproduce the bug
Occurs in every run of the HTML transformation.
# Severity
How much impact does this bug have on further development?
* [ ] Minor
* [X] Major
* [ ] Critical
* [ ] Blocker
# Related Tickets
Add related issues if applicable.
/cc @mgoebel, @hynek, @mrodzismmarkus1Hanna-Lena StolzJutta Lindenthalmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/125Description formatResource Attribute2021-08-06T09:31:41ZHanna-Lena StolzDescription formatResource AttributeSpecify in the schema description that the attribute (using media types) can be used, but is not really necessary.Specify in the schema description that the attribute (using media types) can be used, but is not really necessary.LIDO 1.1 finalMarco KlindtMarco Klindthttps://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/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/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 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 finalmmarkus1mmarkus1