lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2020-01-15T13:06:02Zhttps://gitlab.gwdg.de/lido/development/-/issues/1G26 – display element for repositorySet2020-01-15T13:06:02Zmmarkus1G26 – display element for repositorySetInternal Wiki page: https://wiki.dnb.de/pages/viewpage.action?pageId=135793700
See commit b7f7ca5f9fe0b53224d3779cfc74c5e3c4dfa3ec
Internal Wiki page: https://wiki.dnb.de/pages/viewpage.action?pageId=135793700
See commit b7f7ca5f9fe0b53224d3779cfc74c5e3c4dfa3ec
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/3G17 has been deferred2020-01-10T09:07:34ZMichelle WeidlingG17 has been deferredG17 has been deferred, so all code concerning this feature should be removed from the code.G17 has been deferred, so all code concerning this feature should be removed from the code.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/4G03/06 obsolete2020-01-10T10:50:19ZMichelle WeidlingG03/06 obsolete"G03/06 – add display and sourceAppellation to conceptComplexType" is marked as obsolete in the wiki. Code concerining this feature should thus be removed from the schema."G03/06 – add display and sourceAppellation to conceptComplexType" is marked as obsolete in the wiki. Code concerining this feature should thus be removed from the schema.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/5G09 (objectMaterialsTech) not fully backwards compatible2020-03-11T08:56:10ZMichelle WeidlingG09 (objectMaterialsTech) not fully backwards compatibleDuring the implementation of G09, `extentMaterialsTech`'s type has been changed to `lido:conceptComplexType` which doesn't allow for text nodes. Hence the current implementation isn't backwards compatible.
**Note:** In several context's...During the implementation of G09, `extentMaterialsTech`'s type has been changed to `lido:conceptComplexType` which doesn't allow for text nodes. Hence the current implementation isn't backwards compatible.
**Note:** In several context's it is necessary to define a type that accepts mixed content, i.e. text nodes and `conceptComplexType`. This issue could be solved when this new type is available.Michelle WeidlingMichelle Weidlinghttps://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/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/8G03 – displayConcept2020-04-02T10:11:17ZMichelle WeidlingG03 – displayConcept**Link to DDB Wiki for further information:**
https://wiki.dnb.de/pages/viewpage.action?pageId=135793619
`lido:displayConcept` should be cancelled in behalf of `skos:concept`.**Link to DDB Wiki for further information:**
https://wiki.dnb.de/pages/viewpage.action?pageId=135793619
`lido:displayConcept` should be cancelled in behalf of `skos:concept`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/9Correct documentation2020-03-11T08:00:17ZMichelle WeidlingCorrect documentationThere are some typos in the docs which should be corrected.There are some typos in the docs which should be corrected.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/10Publikationsstrecke2020-03-11T12:56:54ZMichelle WeidlingPublikationsstreckeFür die Veröffentlichung von LIDOv1.1 soll es eine Publikationsstrecke geben, aus der HTML und PDF erzeugt wird. Hierzu muss die TEI-Quelle mit der aktuellen XSD so gemergt werden, dass wir am Ende nur noch eine Datei haben, aus der
* ...Für die Veröffentlichung von LIDOv1.1 soll es eine Publikationsstrecke geben, aus der HTML und PDF erzeugt wird. Hierzu muss die TEI-Quelle mit der aktuellen XSD so gemergt werden, dass wir am Ende nur noch eine Datei haben, aus der
* das Schema
* HTML und
* PDF
erzeugt werden.Michelle WeidlingMichelle Weidlinghttps://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/12G01 – license information2020-10-28T10:31:02ZMichelle WeidlingG01 – license information* [x] Restriktion für URI einführen (cf. Wiki)
* [x] `rightsHolder` kann raus
* [x] alternative Bezeichnungen zu `reuseCondition` recherchieren
* [ ] `reuseCondition` sollte nicht unter `rightsWorkWrap` erlaubt sein, weil dies implizier...* [x] Restriktion für URI einführen (cf. Wiki)
* [x] `rightsHolder` kann raus
* [x] alternative Bezeichnungen zu `reuseCondition` recherchieren
* [ ] `reuseCondition` sollte nicht unter `rightsWorkWrap` erlaubt sein, weil dies impliziert, dass es sich um Nutzungshinweise für das beschriebene Objekt handeltMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/13SKOS: Restrict namespace2020-04-02T07:12:48ZMichelle WeidlingSKOS: Restrict namespaceOnly `skos:concept` should be allowed (and not every element from the SKOS namespace).Only `skos:concept` should be allowed (and not every element from the SKOS namespace).Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/14G18 – measurements inside event structure2020-04-08T12:50:24ZMichelle WeidlingG18 – measurements inside event structureRename `eventMeasurements`. New element name should be `eventObjectMeasurements`.Rename `eventMeasurements`. New element name should be `eventObjectMeasurements`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/15G19 – add birth, death and activity place to actor element2020-04-09T13:18:57ZMichelle WeidlingG19 – add birth, death and activity place to actor elementImplement `vitalPlaceActor` according to snippet. The LIDO terminology has to be adapted to align `vitalPlaceActor` and `vitalDatesActor` via the `type` attribute.Implement `vitalPlaceActor` according to snippet. The LIDO terminology has to be adapted to align `vitalPlaceActor` and `vitalDatesActor` via the `type` attribute.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/16SKOS: Restrict to conceptComplexType2020-03-23T07:44:21ZMichelle WeidlingSKOS: Restrict to conceptComplexType`skos:concept` should only be used for `conceptComplexType`.`skos:concept` should only be used for `conceptComplexType`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/17Docs: Data values2020-03-31T07:36:00ZMichelle WeidlingDocs: Data valuesData values should be placed in a separate `tei:ab`.Data values should be placed in a separate `tei:ab`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/18Docs: subjectConcept2020-04-08T13:37:18ZMichelle WeidlingDocs: subjectConceptImprove docs to avoid confusion.Improve docs to avoid confusion.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/19Docs: genderActor2020-04-08T06:24:29ZMichelle WeidlingDocs: genderActorDoes `lido:genderActor` refer to a person's sex or her/his gender?Does `lido:genderActor` refer to a person's sex or her/his gender?Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/20Meta Information in TEI Header2020-03-13T13:39:07ZMichelle WeidlingMeta Information in TEI HeaderAdd all relevant meta information in the TEI header.Add all relevant meta information in the TEI header.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/21rightsHolder2020-04-01T12:22:35ZMichelle WeidlingrightsHolder`lido:rightsHolder` is defined twice in the schema. Check.`lido:rightsHolder` is defined twice in the schema. Check.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/22Prepare overview for international WG2020-04-08T13:50:38ZMichelle WeidlingPrepare overview for international WGLIDO v1.1: Änderungen (G's) darstellen für die internationale AG (Michelle) => über GitLab
* Beispiele sollten in SKOS sein
* Michelle bereitet eine Mail mit Änderungen und XML-Snippets vorLIDO v1.1: Änderungen (G's) darstellen für die internationale AG (Michelle) => über GitLab
* Beispiele sollten in SKOS sein
* Michelle bereitet eine Mail mit Änderungen und XML-Snippets vorMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/23Add tag names2020-03-27T09:06:35ZMichelle WeidlingAdd tag namesMichelle WeidlingMichelle Weidlinghttps://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/25owl:sameAs2020-04-01T09:52:21ZMichelle Weidlingowl:sameAsImplement `owl:sameAs` for `actorComplexType`, `placeComplexType`, `legalBodyRefComplexType`.Implement `owl:sameAs` for `actorComplexType`, `placeComplexType`, `legalBodyRefComplexType`.Michelle WeidlingMichelle Weidlinghttps://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/27gml: Validation fails2020-04-09T06:19:46ZMichelle Weidlinggml: Validation failsValidating LIDO records with the 1.1 schema raises validation problems with elements from the `gml` namespace. Same holds for validating with LIDO v1.0 which indicates that the imported GML schema has changed over the course of the years.Validating LIDO records with the 1.1 schema raises validation problems with elements from the `gml` namespace. Same holds for validating with LIDO v1.0 which indicates that the imported GML schema has changed over the course of the years.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/28Mixed Content2020-10-30T06:35:08ZMichelle WeidlingMixed ContentImplement elements with mixed content or free text only according to https://wiki.dnb.de/display/DDBCOMMUNITY/lido%3AtextComplexType.Implement elements with mixed content or free text only according to https://wiki.dnb.de/display/DDBCOMMUNITY/lido%3AtextComplexType.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/29ISO dates for recordMetadataDate2020-04-03T08:57:34ZMichelle WeidlingISO dates for recordMetadataDate`recordMetadataDate` should actually have the type `xs:dateTime` instead of `xs:string`. This change wouldn't be backwards compatible, though. A way to bypass this problem is to generate a Schematron warning/info if `recordMetadataDate` ...`recordMetadataDate` should actually have the type `xs:dateTime` instead of `xs:string`. This change wouldn't be backwards compatible, though. A way to bypass this problem is to generate a Schematron warning/info if `recordMetadataDate` doesn't comply to ISO dates.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/30OWL: Restrict namespace usage2020-04-06T07:34:12ZMichelle WeidlingOWL: Restrict namespace usageOnly `owl:sameAs` should be used. Ensure this with Schematron.Only `owl:sameAs` should be used. Ensure this with Schematron.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/31Remove termsOfReuse from schema2020-04-08T07:00:39ZMichelle WeidlingRemove termsOfReuse from schemaMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/32Docs: lidoRecID2020-04-08T13:00:00ZMichelle WeidlingDocs: lidoRecIDMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/33Update README2020-04-09T11:33:39ZMichelle WeidlingUpdate READMEShould contain a changelog.Should contain a changelog.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/34Docs: Data Values intro update2020-04-08T13:48:24ZMichelle WeidlingDocs: Data Values intro updateThe label shouldn't be verbalized for `dataValues`.The label shouldn't be verbalized for `dataValues`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/35Rename tei:ab[@type = 'definition']2020-04-09T06:51:44ZMichelle WeidlingRename tei:ab[@type = 'definition']It's a `description`, not a `definition`.It's a `description`, not a `definition`.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/36Remove @termType2020-04-09T09:11:15ZMichelle WeidlingRemove @termTypeMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/37Disclaimer2020-04-09T11:44:10ZMichelle WeidlingDisclaimerAdd a disclaimer to the schema.Add a disclaimer to the schema.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/38paintings and sculptures2020-04-29T16:27:29ZGudrun Knauspaintings and sculptureshttps://gitlab.gwdg.de/lido/development/-/issues/39Naming of 'Spectrum'2020-07-20T11:58:37ZMichelle WeidlingNaming of 'Spectrum'All occurrences of 'SPECTRUM' should be renamed to 'Spectrum'.
It was an acronym but nobody used it and even knew what it was.All occurrences of 'SPECTRUM' should be renamed to 'Spectrum'.
It was an acronym but nobody used it and even knew what it was.LIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/40Submitting IIIF resources2020-12-01T16:21:40Zmmarkus1Submitting IIIF resourcesImplement a standard way for submitting IIIF resources as representation of the described cultural heritage object in a LIDO record.
Recommendation from Europeana: https://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Te...Implement a standard way for submitting IIIF resources as representation of the described cultural heritage object in a LIDO record.
Recommendation from Europeana: https://pro.europeana.eu/files/Europeana_Professional/Share_your_data/Technical_requirements/EDM_profiles/IIIFtoEDM_profile_042016.pdf
Recommendation from Linked.Art: https://linked.art/model/digital/#iiif
Further reading:
Discussion on CRM: https://github.com/IIIF/api/issues/1089
Background to EDM work: https://github.com/IIIF/api/issues/558
DDB Use Case:
Map manifests into EDM and pass it to Europeana. LIDO 1.1 finalMichelle Weidlingmmarkus1Michelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/41source attribute for multiple elements2021-05-20T13:19:19Zmmarkus1source attribute for multiple elementsrequirements by graphic arts
a. the attribution of an artwork to a certain artist
b. the relationship of an artwork to other works
In the future we should be able to make different points of view comparable in one data-set, e.g. perso...requirements by graphic arts
a. the attribution of an artwork to a certain artist
b. the relationship of an artwork to other works
In the future we should be able to make different points of view comparable in one data-set, e.g. person A says: This is made by Michelangelo, person B says: No, it was his pupil, but we don’t know the name of this pupil.
In order to solve this, we would need a source attribute at the element <attributionQualifierActor>, but it has to be a published source, otherwise the scientists can’t cite the source.
The second area is the understanding of how one work relates to another. Person A says: This drawing is a preparatory drawing for this print, person B says: No, it is a drawing that further evolves the invention of the print in order to prepare a painting with the same motive.
In order to solve this, we would need a source attribute at the element <relatedWorkRelType>, as mentioned above, it must be a published source.https://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/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/45Draft for accompanying document2020-10-26T10:10:46ZMichelle WeidlingDraft for accompanying documentWe want to create an accompanying document for LIDO v1.1 covering additional information which shouldn't be listed in the schema docs.
At this moment, this includes:
* introductory texts
* listing the following information per element ...We want to create an accompanying document for LIDO v1.1 covering additional information which shouldn't be listed in the schema docs.
At this moment, this includes:
* introductory texts
* listing the following information per element (where applicable):
* further information
* data values
* equivalent elements in other schemas
Cf. https://wiki.dnb.de/pages/viewpage.action?pageId=167039097Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/46GML: switch XSD2020-10-13T11:05:07ZMichelle WeidlingGML: switch XSDCurrently we import the GML XSD available at <http://schemas.opengis.net/gml/3.1.1/base/feature.xsd> which happens to include `base/gml.xsd` twice due to some circumstances. This leads to errors in some processors.
**TODO:**
* [ ] find ...Currently we import the GML XSD available at <http://schemas.opengis.net/gml/3.1.1/base/feature.xsd> which happens to include `base/gml.xsd` twice due to some circumstances. This leads to errors in some processors.
**TODO:**
* [ ] find out reason for using `feature.xsd` instead of `gml.xsd`
* [ ] implement if feasibleLIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/47add type for eventObjectMeasurements2020-10-28T10:28:44ZMichelle Weidlingadd type for eventObjectMeasurementsMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/48Add pref for titleSet2020-10-21T06:13:39ZMichelle WeidlingAdd pref for titleSetDecided on the LIDO working group meeting on 2020-10-20.Decided on the LIDO working group meeting on 2020-10-20.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/49Schema version without QA2020-10-30T14:29:27ZMichelle WeidlingSchema version without QALIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/50type of @lido:measurementsGroup2020-12-01T16:21:40ZMichelle Weidlingtype of @lido:measurementsGroupIs xs:anyURI correct or should we switch to xs:string?Is xs:anyURI correct or should we switch to xs:string?LIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://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/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/53Update README2020-12-01T16:21:40ZMichelle WeidlingUpdate READMELIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/54Schematron: check recordMetadataDate2021-04-14T11:07:15ZMichelle WeidlingSchematron: check recordMetadataDaterecordMetadataDate should at least provide a day.recordMetadataDate should at least provide a day.https://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/56Schematron: split sch_DateTime into date and date+time rule2021-06-21T08:42:50Zmmarkus1Schematron: split sch_DateTime into date and date+time rulerecordMetadataDate needs a full time stamp like sch_dateTime is currently testing for.
earliestDate and latestDate do only need a date (YYYY, MM-YYYY or DD-MM-YYYY) no timestamp.
The rule sch_DateTime needs to splitted into two rules.recordMetadataDate needs a full time stamp like sch_dateTime is currently testing for.
earliestDate and latestDate do only need a date (YYYY, MM-YYYY or DD-MM-YYYY) no timestamp.
The rule sch_DateTime needs to splitted into two rules.https://gitlab.gwdg.de/lido/development/-/issues/57Schematron: Verify IIIF rule2021-04-14T11:15:44Zmmarkus1Schematron: Verify IIIF ruleThere might be an issue with sch_IIIF_Measurements. Users comply that the test does not work properly and triggers for every lido:resourceRepresentation. see MR !60There might be an issue with sch_IIIF_Measurements. Users comply that the test does not work properly and triggers for every lido:resourceRepresentation. see MR !60mmarkus1mmarkus1https://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/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/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/60Remove attribute mostNotableEvent from eventWrap + Documentation2021-04-19T08:11:33ZMarco KlindtRemove attribute mostNotableEvent from eventWrap + DocumentationHistoric discussion mentionend attribute in eventWrap. This is a bug.
The documentation should clarify scope, how to record, and semantic distinction from sortOrder attributeHistoric discussion mentionend attribute in eventWrap. This is a bug.
The documentation should clarify scope, how to record, and semantic distinction from sortOrder attributeMarco 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 Klindthttps://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/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/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/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/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/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/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/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/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/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/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/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/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/92consolidate Data values2021-05-05T14:47:49ZHanna-Lena Stolzconsolidate Data values- *deleted* dataValues "Not applicable"
- *changed* dataValues "Controlled terminology" _into_ "Controlled"
- *changed* dataValues "Controlled list" _into_ "Controlled"
- *changed* dataValues "Controlled format" _into_ "Contr...- *deleted* dataValues "Not applicable"
- *changed* dataValues "Controlled terminology" _into_ "Controlled"
- *changed* dataValues "Controlled list" _into_ "Controlled"
- *changed* dataValues "Controlled format" _into_ "Controlled"
- *deleted* dataValues "Controlled format" _for_ IDs
- *added* dataValues "Controlled" _for_ "formatResource"LIDO 1.1 finalJutta 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 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/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/96revise attributes2021-05-13T08:41:34ZJutta Lindenthalrevise attributesLIDO 1.1 finalJutta LindenthalJutta Lindenthalhttps://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/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/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/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/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/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/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/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/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/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/111Add references for source elements2021-05-25T09:57:43ZJutta LindenthalAdd references for source elementsJutta LindenthalJutta Lindenthalhttps://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/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/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/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/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/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/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/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/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/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 Lindenthalmmarkus1