lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2020-12-01T16:21:40Zhttps://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/49Schema version without QA2020-10-30T14:29:27ZMichelle WeidlingSchema version without QALIDO 1.1 finalMichelle 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/47add type for eventObjectMeasurements2020-10-28T10:28:44ZMichelle Weidlingadd type for eventObjectMeasurementsMichelle 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/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/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/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/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/38paintings and sculptures2020-04-29T16:27:29ZGudrun Knauspaintings and sculptureshttps://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/36Remove @termType2020-04-09T09:11:15ZMichelle WeidlingRemove @termTypeMichelle 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/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/33Update README2020-04-09T11:33:39ZMichelle WeidlingUpdate READMEShould contain a changelog.Should contain a changelog.Michelle WeidlingMichelle Weidlinghttps://gitlab.gwdg.de/lido/development/-/issues/32Docs: lidoRecID2020-04-08T13:00:00ZMichelle WeidlingDocs: lidoRecIDMichelle 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/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/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/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 Weidling