lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2021-06-21T08:42:56Zhttps://gitlab.gwdg.de/lido/development/-/issues/423D content2021-06-21T08:42:56Zmmarkus13D contentWith reference to what Kate Fernie pointed out in the 3D content in Europeana task force Report (pp. 28-29), the main problem with LIDO with regard to 3D is that there is no direct relation between a certain resource representing the obj...With reference to what Kate Fernie pointed out in the 3D content in Europeana task force Report (pp. 28-29), the main problem with LIDO with regard to 3D is that there is no direct relation between a certain resource representing the object and a certain event it was involved in. So it might be worth considering adding a relatedResourceSet (including a resource ID) in the EventSet and/or a relatedEventSet in the resourceSet. It would not only help with 3D content, but also with ex. conservation-related events/resources (before-after images of a conservation event) etc.
It would also be very interesting to know what you are planning to do with regard to updating the LIDO vocabulary.https://gitlab.gwdg.de/lido/development/-/issues/26Add "DataValues" as docs element2020-10-30T14:29:57ZMichelle WeidlingAdd "DataValues" as docs elementLIDO 1.1 finalhttps://gitlab.gwdg.de/lido/development/-/issues/62Add documentation for how to use schematron rules2021-04-14T08:54:01ZMarco KlindtAdd documentation for how to use schematron rulesCreate first steps documentation for how to handle schematron within a 1.1 validation workflow.Create first steps documentation for how to handle schematron within a 1.1 validation workflow.Marco KlindtMarco Klindthttps://gitlab.gwdg.de/lido/development/-/issues/24Add links to CDWA full2020-10-30T14:30:06ZMichelle WeidlingAdd links to CDWA fullLIDO 1.1 finalhttps://gitlab.gwdg.de/lido/development/-/issues/83Add missing dataValues section in PDF2021-06-28T12:20:49Zmmarkus1Add missing dataValues section in PDFThe dataValues (tei:ab type="dataValues") are currently missing in the PDF version. Cf. the HTML tranformation.The dataValues (tei:ab type="dataValues") are currently missing in the PDF version. Cf. the HTML tranformation.https://gitlab.gwdg.de/lido/development/-/issues/106adjust labels for set elements2021-09-02T12:46:55ZHanna-Lena Stolzadjust labels for set elementsSome elments will be described as "A set...." and therefore will get a suitable label (see: subjectActor vs. subjectObject) A list of the elements for which the label will be adjusted will follow shortly.Some elments will be described as "A set...." and therefore will get a suitable label (see: subjectActor vs. subjectObject) A list of the elements for which the label will be adjusted will follow shortly.LIDO 1.1 finalHanna-Lena StolzGudrun KnausHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/7Allow foreign attributes and elements in LIDO2020-10-28T10:36:11ZMichelle WeidlingAllow foreign attributes and elements in LIDO**Link to DDB Wiki for further information:** TBD
**Use case:**
For some application profile it is useful to augment certain LIDO elements with their own attributes and/pr elements, i.e. nodes with a non-LIDO namespace. This comes in ha...**Link to DDB Wiki for further information:** TBD
**Use case:**
For some application profile it is useful to augment certain LIDO elements with their own attributes and/pr elements, i.e. nodes with a non-LIDO namespace. This comes in handy e.g. for automatically enrich data with information from authority files. However, inserting foreign nodes isn't valid in the current schema.
**Note:** Similar to allowing SKOS in certain contexts.https://gitlab.gwdg.de/lido/development/-/issues/61beta.xsd references rules in beta-qa.xsd2021-04-14T08:48:41ZMarco Klindtbeta.xsd references rules in beta-qa.xsd...beta.xsd references rules in ...beta-qa.xsd.
Solution: remove rules sch_pref and sch_alternate.
Side effects?...beta.xsd references rules in ...beta-qa.xsd.
Solution: remove rules sch_pref and sch_alternate.
Side effects?Marco KlindtMarco Klindthttps://gitlab.gwdg.de/lido/development/-/issues/74Change sequence for owl:sameAs to last element2021-05-20T07:19:20ZTimo SchleierChange sequence for owl:sameAs to last elementThe `owl:sameAs` Element was introduced in the following "compleyTypes":
* `lido:actorComplexType`
* `lido:placeComplexType`
* `lido:legalBodyRefComplexType`
* `lido:dateSetComplexType`
* `lido:rightsHolderComplexType`
In the LIDO 1.1. ...The `owl:sameAs` Element was introduced in the following "compleyTypes":
* `lido:actorComplexType`
* `lido:placeComplexType`
* `lido:legalBodyRefComplexType`
* `lido:dateSetComplexType`
* `lido:rightsHolderComplexType`
In the LIDO 1.1. beta version `owl:sameAs` is the first element in sequence, but should be moved to the last position as a new element and for pragmatic reasons ("same as after the description of the entity").Hanna-Lena StolzTimo SchleierHanna-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/107Consistent description of the elements based on defined formal criteria2021-06-25T13:06:40ZHanna-Lena StolzConsistent description of the elements based on defined formal criteria- **A wrapper** is a container element that is not repeatable and cannot have any attributes other than a language attribute. The description is introduced with "A wrapper ...".
- **A set** is a container element that is (usually) repea...- **A wrapper** is a container element that is not repeatable and cannot have any attributes other than a language attribute. The description is introduced with "A wrapper ...".
- **A set** is a container element that is (usually) repeatable and can have attributes. The description is introduced with "A set ...".
- An **index element** is an element that can contain values, often as skos: Concept, that can be included in the indexate as such. Data values should be "Controlled". The description is introduced with "An index element ...".
- A **text element** is an element that can contain values. Data values should always be "Free text". The description is introduced with "A text element ...".LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://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/97Crosswalk: Complete TODOs2021-06-28T06:51:22ZJulia RösselCrosswalk: Complete TODOsWithin the Crosswalk missing information is marked by "TODO". These need to be collected and completed within the Crosswalk-File.
[Metadata-Crosswalk_TODOs.xlsx](/uploads/d90254af9683c0f3663a2ee84a8c7b5b/Metadata-Crosswalk_TODOs.xlsx)Within the Crosswalk missing information is marked by "TODO". These need to be collected and completed within the Crosswalk-File.
[Metadata-Crosswalk_TODOs.xlsx](/uploads/d90254af9683c0f3663a2ee84a8c7b5b/Metadata-Crosswalk_TODOs.xlsx)Hanna-Lena StolzJulia RösselHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/51Crosswalk: handle multiple element definitions2020-10-30T10:39:14ZMichelle WeidlingCrosswalk: handle multiple element definitionsTwo elements, `lido:actor` and `lido:lido` are defined several times, depending on the complexType they are part of.
Should the crosswalk reflect this? If so: how?Two elements, `lido:actor` and `lido:lido` are defined several times, depending on the complexType they are part of.
Should the crosswalk reflect this? If so: how?https://gitlab.gwdg.de/lido/development/-/issues/67Crosswalk: missing elements2021-06-04T15:08:17ZHanna-Lena StolzCrosswalk: missing elementsadd measurementsGroup and ConceptID to metadata-crosswalk.xmladd measurementsGroup and ConceptID to metadata-crosswalk.xmlLIDO 1.1 finalhttps://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/104Design and Implement hierarchical view of the LIDO structure2021-08-27T08:11:32Zmmarkus1Design and Implement hierarchical view of the LIDO structureThe current LIDO documentation is based on an alphabetical list grouped by elements, complex types, attributes and Schematron rules. This is great for users who want to look up a specific element/complexType/attribute/Schematron rule. Th...The current LIDO documentation is based on an alphabetical list grouped by elements, complex types, attributes and Schematron rules. This is great for users who want to look up a specific element/complexType/attribute/Schematron rule. This is a disadvantage especially for users who orientate themselves on the basis of a typical XML structure.
The aim is to develop a hierarchical tree view based on an LIDO XML structure. This view should become a new link based navigation in addition to the current HTML documentation.LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/6G10 - additional separate rights information for object description2020-10-29T13:52:17ZMichelle WeidlingG10 - additional separate rights information for object description**Link to DDB Wiki for further information:**
https://wiki.dnb.de/pages/viewpage.action?pageId=135794398**Link to DDB Wiki for further information:**
https://wiki.dnb.de/pages/viewpage.action?pageId=135794398https://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/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
* [ ] Blocker