lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2021-06-25T07:40:20Zhttps://gitlab.gwdg.de/lido/development/-/issues/59Change <p> to <tei:p> in header2021-06-25T07:40:20Zmmarkus1Change <p> to <tei:p> in header<p> needs to be changed to <tei:p> to be tei compliant. The change needs to done in all LIDO.xsds and in the publication workflow for HTML and PDF.<p> needs to be changed to <tei:p> to be tei compliant. The change needs to done in all LIDO.xsds and in the publication workflow for HTML and PDF.LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/75Change sentence terminology recommendations for type attribute2021-06-21T14:13:40ZHanna-Lena StolzChange sentence terminology recommendations for type attributeChange sentence from: _For an attribute the element holds_ to _For the type attribute the element holds_.
Except for: placeComplexTypeChange sentence from: _For an attribute the element holds_ to _For the type attribute the element holds_.
Except for: placeComplexTypeLIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/99Do not show Description of attributes in elements (except for type attributes)2021-06-21T14:07:50ZJutta LindenthalDo not show Description of attributes in elements (except for type attributes)1. Do not show Description of attributes in elements (except for type attributes)
2. Delete Terminology/Format recommendation for these attributes
Example <[place](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#place)...1. Do not show Description of attributes in elements (except for type attributes)
2. Delete Terminology/Format recommendation for these attributes
Example <[place](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#place)>
Attributes (except type attributes) are described seperately. There is no need to show descriptions for attributes in the element's description. Further reasons to abandon the display of attribute annotations:
- Since "Data values" does not distinguish between elements and attributes, the reference may be ambiguous.
- Only a seamingly arbitrary selection of attributes is shown.LIDO 1.1 finalhttps://gitlab.gwdg.de/lido/development/-/issues/68eventDescriptionSet2021-06-21T12:50:24ZHanna-Lena StolzeventDescriptionSet In description of the type attribute link on CDWA does NOT open as a new tab.
<br>tei: ref check whether attribute for differentiation link external / internal is possible
<br>Add under further reading?
<br> Same under [inscriptions](ht... In description of the type attribute link on CDWA does NOT open as a new tab.
<br>tei: ref check whether attribute for differentiation link external / internal is possible
<br>Add under further reading?
<br> Same under [inscriptions](http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#inscriptions)mmarkus1Hanna-Lena Stolzmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/117display element for extentActor needed2021-06-20T15:00:37ZGudrun Knausdisplay element for extentActor neededcontrolled vocabulary in this case is less precise than the possibility to express the extent of participation with a longer sentence. Sample data values:
"Bronzeabguss nachträglich vom Künstler mit Ölfarbe bemalt"
"der Himmel im Bild ...controlled vocabulary in this case is less precise than the possibility to express the extent of participation with a longer sentence. Sample data values:
"Bronzeabguss nachträglich vom Künstler mit Ölfarbe bemalt"
"der Himmel im Bild wurde vom Restaurator 1876 von neuzeitlicher Übermalung befreit".mmarkus1Hanna-Lena Stolzmmarkus1https://gitlab.gwdg.de/lido/development/-/issues/63objectPublishedID: Description: Explain, why it is necessary and useful that ...2021-06-16T08:40:52ZMartin Strickermartin.stricker@hu-berlin.deobjectPublishedID: Description: Explain, why it is necessary and useful that element is repeatable* See: http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#objectPublishedID
* Internal Wiki: WG session 2021-04-14 https://wiki.dnb.de/display/DDBCOMMUNITY/2021-04-14
Coordinate task with question of QA rule "[Data Qualit...* See: http://www.lido-schema.org/schema/v1.1/lido-v1.1-public-beta.html#objectPublishedID
* Internal Wiki: WG session 2021-04-14 https://wiki.dnb.de/display/DDBCOMMUNITY/2021-04-14
Coordinate task with question of QA rule "[Data Quality] @pref: Discern preferred and alternative elements"LIDO 1.1 finalMartin Strickermartin.stricker@hu-berlin.deMartin Strickermartin.stricker@hu-berlin.dehttps://gitlab.gwdg.de/lido/development/-/issues/77Adapt description for display elements2021-06-03T07:08:43ZHanna-Lena StolzAdapt description for display elementsFor some/most display elements there should be a link to the subsequent index element/sFor some/most display elements there should be a link to the subsequent index element/sLIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/112resourceSource2021-05-28T17:15:49ZGudrun KnausresourceSourceWhat kind of type attributes are available for the element resourceSource? No terms in X-Tree or Wiki found.What kind of type attributes are available for the element resourceSource? No terms in X-Tree or Wiki found.Hanna-Lena StolzJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/111Add references for source elements2021-05-25T09:57:43ZJutta LindenthalAdd references for source elementsJutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/55Schematron: check if measurementValue has integer2021-05-23T10:37:16ZMichelle WeidlingSchematron: check if measurementValue has integerCf. https://wiki.dnb.de/display/DDBCOMMUNITY/Protokoll+2020-10-27Cf. https://wiki.dnb.de/display/DDBCOMMUNITY/Protokoll+2020-10-27https://gitlab.gwdg.de/lido/development/-/issues/108sourceActorInRole- type attribute needed2021-05-21T05:19:10ZGudrun KnaussourceActorInRole- type attribute neededhttp://balilabs.de/rr/edlido.html?e=Beispielschnipsel_attribution.xml
In order to give a hint, whether the source is an uri or just a text (whether printed or not), shall we introduce a type attribute for any kind of source element? (no...http://balilabs.de/rr/edlido.html?e=Beispielschnipsel_attribution.xml
In order to give a hint, whether the source is an uri or just a text (whether printed or not), shall we introduce a type attribute for any kind of source element? (not sure)
Might also be relevant for:
sourceRelatedWorkSet/sourceAppellation/sourceRepositorySet/sourceDescriptiveNote/sourceMaterialsTechHanna-Lena StolzJutta LindenthalHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/95harmonization of the description of complex types2021-05-20T06:28:16ZHanna-Lena Stolzharmonization of the description of complex typesSometimes the description of the complex types is starting with "A Wrapper". This should be harmonized into "Contains..."Sometimes the description of the complex types is starting with "A Wrapper". This should be harmonized into "Contains..."LIDO 1.1 finalHanna-Lena StolzHanna-Lena Stolzhttps://gitlab.gwdg.de/lido/development/-/issues/52Establish flow for mering into main2021-05-19T16:34:09ZMichelle WeidlingEstablish flow for mering into mainLIDO 1.1 finalmmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/11Add application profiles2021-05-19T12:08:42ZMichelle WeidlingAdd application profiles* [ ] add IDs* [ ] add IDshttps://gitlab.gwdg.de/lido/development/-/issues/44Update header for publication2021-05-19T12:06:20ZMichelle WeidlingUpdate header for publicationThe header of the schema has to be updated. Also, the change history and excess comments have to be deleted.The header of the schema has to be updated. Also, the change history and excess comments have to be deleted.LIDO 1.1 finalhttps://gitlab.gwdg.de/lido/development/-/issues/58Omitt documentation in xsd2021-05-19T12:03:34Zmmarkus1Omitt documentation in xsdMove extended documentation from "master" xsd to e.g. "*-full-documentation.xsd.
Reason: Each change on documentation results in change on version.Move extended documentation from "master" xsd to e.g. "*-full-documentation.xsd.
Reason: Each change on documentation results in change on version.mmarkus1mmarkus1https://gitlab.gwdg.de/lido/development/-/issues/101Replace "for a single" by "for one" where appropriate2021-05-13T11:11:44ZJutta LindenthalReplace "for a single" by "for one" where appropriateThe phrase "for a single [entity] ..." in the sense of "one [entity] per element" may be ambiguous. Therefore the phrase is replaced by "for one [entity] ...".The phrase "for a single [entity] ..." in the sense of "one [entity] per element" may be ambiguous. Therefore the phrase is replaced by "for one [entity] ...".Jutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/96revise attributes2021-05-13T08:41:34ZJutta Lindenthalrevise attributesLIDO 1.1 finalJutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/94change ID description2021-05-05T15:47:49ZJutta Lindenthalchange ID description- *deleted* term "unique" in description for repeatable identifiers
- *changed* for repeatable identifiers only
- *added* "Repeated for identifiers from different authority files or other sources.", or the like
- *deleted* dataValue "Con...- *deleted* term "unique" in description for repeatable identifiers
- *changed* for repeatable identifiers only
- *added* "Repeated for identifiers from different authority files or other sources.", or the like
- *deleted* dataValue "Controlled format", remains of issue 92Jutta LindenthalJutta Lindenthalhttps://gitlab.gwdg.de/lido/development/-/issues/93change link labels2021-05-05T15:14:21ZJutta Lindenthalchange link labels*changed* natural language Labels in "Terminology/Format recommendation" into URI labels, aligning with "Equivalents in other schemas"*changed* natural language Labels in "Terminology/Format recommendation" into URI labels, aligning with "Equivalents in other schemas"LIDO 1.1 finalJutta LindenthalJutta Lindenthal