lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2021-05-23T10:37:16Zhttps://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/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/53Update README2020-12-01T16:21:40ZMichelle WeidlingUpdate READMELIDO 1.1 finalMichelle WeidlingMichelle Weidlinghttps://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/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/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/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/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/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 Weidling