LIDO issueshttps://gitlab.gwdg.de/groups/lido/-/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/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/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/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/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/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/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/102measurementValue: Allow2021-06-28T07:02:10ZSophie RöllemeasurementValue: AllowSee google doc: https://docs.google.com/document/d/1vfDOE6Qya641kzfPHzuzHN19ybGNsC_iv3Iaf0fwunE/edit# (row <measurementValue)
See [Wiki](https://wiki.dnb.de/x/4zDVCg)
See [Wiki] (https://wiki.dnb.de/x/4lfVCg)
@p.mklindt mentioned that i...See google doc: https://docs.google.com/document/d/1vfDOE6Qya641kzfPHzuzHN19ybGNsC_iv3Iaf0fwunE/edit# (row <measurementValue)
See [Wiki](https://wiki.dnb.de/x/4zDVCg)
See [Wiki] (https://wiki.dnb.de/x/4lfVCg)
@p.mklindt mentioned that it would be quiet difficult to accept decimals, cause it would be almost impossible to analyze varying kinds of those values to note them. I rememer now, we all agreed with this and M. Weidling wanted to add rules for that in schematron.
If this is still a topic and accurate, we have emphasize, that that would be a diffenrance the recommendation of CDWA.
CDWA: Description überarbeiten. Auszug aus CDWA für 6.3. Dimensions Value: "Whole numbers or decimal fractions only. It is recommended to use numbers that refer metric units in this controlled field, however, local practice may vary."Martin Strickermartin.stricker@hu-berlin.deMarco KlindtSophie RölleMartin Strickermartin.stricker@hu-berlin.dehttps://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/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/69Schema documentation links in accompanying-document.html2021-04-16T12:57:18ZHanna-Lena StolzSchema documentation links in accompanying-document.htmle.g.http://www.lido-schema.org/schema/v1.1/accompanying-document.html#titleSet_type
<br>"[Go to the schema documentation for titleSet_type](http://schema.lido-schema.org/v1.1/lido-v1.1-public-beta.html#titleSet_type)"
Clarify: Where sh...e.g.http://www.lido-schema.org/schema/v1.1/accompanying-document.html#titleSet_type
<br>"[Go to the schema documentation for titleSet_type](http://schema.lido-schema.org/v1.1/lido-v1.1-public-beta.html#titleSet_type)"
Clarify: Where should these links point.There is no generic description of the type attributes. Maybe take out the linkhttps://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/66objectRelationWrap: mandatory: yes2021-08-10T19:32:13ZHanna-Lena StolzobjectRelationWrap: mandatory: yesSpecified as a mandatory field. Check transformation for mandatory.Specified as a mandatory field. Check transformation for mandatory.LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://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/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 Klindt