lido-development issueshttps://gitlab.gwdg.de/lido/development/-/issues2021-04-14T08:48:41Zhttps://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/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/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/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/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/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/26Add "DataValues" as docs element2020-10-30T14:29:57ZMichelle WeidlingAdd "DataValues" as docs elementLIDO 1.1 finalhttps://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/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/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=135794398