lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2020-01-10T09:07:34Zhttps://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/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/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/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/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/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/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/23Add tag names2020-03-27T09:06:35ZMichelle WeidlingAdd tag namesMichelle 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/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/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/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/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/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/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/31Remove termsOfReuse from schema2020-04-08T07:00:39ZMichelle WeidlingRemove termsOfReuse from schemaMichelle 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/32Docs: lidoRecID2020-04-08T13:00:00ZMichelle WeidlingDocs: lidoRecIDMichelle WeidlingMichelle Weidling