Minimum Record Recommendation for Museums and Collections (MDS v1.1)

English Translation: Minimum Record Recommendation for Museums and Collections (MDS v1.1) What is the Minimum Record Recommendation? Museums and collections want to share the objects in their depots and exhibition spaces with the public and make object information digitally accessible. In addition to presenting their own online collections, there is also the option of taking part in cultural portals. The show how to improve the discoverability, connectivity and reusability of information about collection objects. The use of standards in FAIR Principles structuring data, as well as the use of standardised vocabularies and common cataloguing regulations, are of crucial importance here. Especially institutions with limited resources hesitate to meet these supposedly (too) high requirements. The Minimum Record Recommendation shows them where they can start to ensure the sustainability and future viability of their data. The Minimum Record Recommendation therefore specifies the most important data elements for the online publication of object information from museums and collections and provides information on how these elements should be filled in. The "Minimum Record" is the smallest possible intersection of relevant data elements that ensures a minimum level of data quality across most disciplines and museum types. In-depth cataloguing can build on this if required. The practical implementation of the Recommendation leads to a consistent coverage of the most important data elements for the identification and description of objects, as well as for the most frequently used search criteria. The focus on the ethical aspects of publishing cultural heritage data. The cataloguing specifications of the Minimum Record CARE Principles Recommendation refer to the CARE Principles where appropriate. These apply in particular to data on collection items from colonial contexts. What are the objectives of the Recommendation? The Minimum Record Recommendation is intended to pave the way for smaller and larger museums and collections to publish their data online and to communicate relevant standards in an easy-to-understand, low-threshold approach. The aim is to raise awareness of data quality in cultural institutions and support them with online publication. The recommendation is intended for practical application in everyday museum work. The Minimum Record Recommendation is intended to support museums in setting the course for more consistent and higher-quality data right from the start. It assists them in gradually integrating controlled vocabularies into their documentation and publication practice, thus preparing their valuable data sets for up-to-date Linked Open Data scenarios. Who is behind it? The Recommendation has been developed by the Minimum Record Working Group. It was initiated in 2022 by the Museum and Media Desks of the German Digital Library (DDB), the Working Group on Digitisation of the Konferenz der Museumsberatungsstellen in den Ländern (KMBL) and digiS Berlin. Members of the working group include representatives from the Institute for Museum Research - Staatliche Museen zu Berlin - Stiftung Preußischer Kulturbesitz, the Fachgruppe Dokumentation of the German Museum Association (DMB), the Coordination Centre for Scientific University Collections in Germany, digiCULT-Verbund eG, museum-digital Deutschland e. V., NFDI4Culture, NFDI4Objects, NFDI4Memory, Museum für Naturkunde Berlin and Übersee-Museum Bremen. Both during the development of the beta version (2023) and the finalisation of the first full version of the Minimum Record Recommendation, which was published in May 2024, representatives from various stakeholder groups, including museum staff, persons working in consultancy and education, software providers and representatives from various cultural heritage portals, were involved and asked for feedback. Feedback welcome! Comments and suggestions for changes are very welcome. They will be considered by the Minimum Record Working Group and may be included in the next version of the Recommendation. Please send your comments to: [email protected] You are welcome to subscribe to our newsletter for useful information and the latest news about the Minimum Record: https://newsletter.museen-in-bayern. de/f/102943-392139/ Data element set Data elements (cataloguing) Data elements that are usually populated during data entry: Object title or name (mandatory) Object type or designation (mandatory) Classification (recommended) Inventory number (mandatory) Object description (recommended) Materials (recommended) Techniques (recommended) Measurements (recommended) Event in object history [element set] (mandatory) Event type (mandatory) Person/corporate body (conditionally mandatory) Date (conditionally mandatory) Place (conditionally mandatory) Subject keyword (recommended) Media file [element set] (mandatory) Link to media file (mandatory) Usage rights of media file (mandatory) Rights holder of media file (conditionally mandatory) Alternative text (recommended) Data elements (export) Data fields that are usually populated during or after export from the local database system: Record ID (mandatory) Record language (mandatory) Record type (mandatory) Repository of object (mandatory) Institution providing record (mandatory) Media file: type of media file (mandatory) Usage rights of metadata record (mandatory) Link to published metadata record (recommended) Record date (recommended) FAQs etc. FAQs (English) Resources and links Press Release (German): Online-Handreichung zur besseren Auffindbarkeit von Objektinformationen aus Museen veröffentlicht Change log (English) Credits and citation Acknowledgements Data elements (cataloguing) Data elements that are usually populated during data entry: Object title or name (mandatory) Object type or designation (mandatory) Classification (recommended) Inventory number (mandatory) Object description (recommended) Materials (recommended) Techniques (recommended) Measurements (recommended) Event in object history [element set] (mandatory) Event type (mandatory) Person/corporate body (conditionally mandatory) Date (conditionally mandatory) Place (conditionally mandatory) Subject keyword (recommended) Media file [element set] (mandatory) Link to media file (mandatory) Usage rights of media file (mandatory) Rights holder of media file (conditionally mandatory) Alternative text (recommended) Object title or name (mandatory) Definition Unique title or name of the object or work for online presentation Other possible database element names Object name Object proper name Text/URI Text Repeatable Yes Obligation level Mandatory Recording notes The object title should describe or identify the object or work as clearly as possible. It should not be identical to the element. The Object type or designation title may have been given by the creator of the object, or it may be a name commonly used in literature for the individual object. If an object title is not available or known, one can be constructed for online publication. If the object title is composed of multiple data elements, it should be concise and clear to ensure digital accessibility. In such cases, a combination of with one of the following pieces of information is recommended: Object type or designation Inve , , or .ntory number Date Technique The element can be repeated to indicate original titles, alternative titles, etc. In natural history, the scientific name should be used as the object title, with the common name optionally included as an alternative title. Both name or title forms must be supplemented with the to create a unique Inventory number title for the object. : The designation of an collection item from colonial contexts in its country of origin or source community is important for identification and CARE findability. These designations should therefore be included and, where appropriate, prioritised. Examples Four Dancing Muses Four-poster bed, 23971-2 Pamphlet, offset print Portrait of actress Maria Anna Löhn (1830-1902) Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element Etruscan lamp with gorgon's head Minimal polyhedral model of Boy's Surface Self-propelled sugar beet harvester by Herriau Monastery complex of the Dominican convent Maria Zuflucht (Weesen) Frigate "Diana", hull model Lymnaea stagnalis, ZMA.MOLL.371629 Pim tocCARE: Expression in LIDO (v1.0 and v1.1) <lido:objectIdentificationWrap> <lido:titleWrap> <lido:titleSet lido:type="http://vocab.getty.edu/aat/300417200"> <lido:appellationValue xml:lang="de">Vier tanzende Musen</lido:appellationValue> <lido:appellationValue xml:lang="en">Four Dancing Muses</lido:appellationValue> </lido:titleSet> <lido:titleSet lido:type="http://vocab.getty.edu/aat/300417227"> <lido:appellationValue xml:lang="de">Tanzende Göttinnen</lido:appellationValue> <lido:appellationValue xml:lang="en">Dancing Goddesses</lido:appellationValue> </lido:titleSet> </lido:titleWrap> </lido:objectIdentificationWrap> Comparison with relevant standards and database models Standard Element Name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata req uirements for data provision Objekttitel Text Yes Mandatory German Digital Library LIDO application profile (DDBLIDO) <titleWrap> Text Yes Mandatory If several titles are provided, they must be labelled so as to make clear which is the preferred title and which are the other titles. In DDB-LIDO, the preferred title in the element <lido:titleSet> is labelled by the type attribute http://vocab.getty.edu/aat or . Additional titles will be displayed /300417200 http://vocab.getty.edu/aat/300417205 with the label "Other title(s)" or "Original title" and have to be labelled as follows: http://voc for "alternate titles" and ab.getty.edu/aat/300417227 http://vocab.getty.edu/aat/300417204 for "original titles" CCC-LIDO Application profile Object title and additional designation for the collection item in the language of origin <titleWrap> Text Yes Mandatory The title (also known as local name, indigenous name, or proper name) is also recommended and must be typed as follows: “titleLanguageOrigin”. DFG Basic Data Record Source Object Title Text Not specified Mandatory DFG Practical Guidelines on Digitisation: LIDO core metadata Title/Object name <titleSet> Text Yes Mandatory Europeana Data Model (EDM) <dc:title> Text Yes Conditionally mandatory In the (object title) OR (object Europeana Data Model <dc:title> <dc:description> description) are mandatory. EODEM application profile Title/Name /lido:titleWrap/ lido:titleSet/lido: appellationValue Text No Mandatory In addition, the <Title_Type> and <Title_Language> elements are mandatory in the EODEM application profile. Categories for the Description of Works of Art (2024) 3.1. Title Text Text Yes Recommend ed CORE element CDWA Lite (2006) 2.1.1 Title Text Yes Mandatory If several titles are specified, 2.1 Title Set is repeated. Spectrum 5.1 Title Text Yes Not specified The obligation level is determined by the institution. digiCULT Titel / Objektname [eng.: Title /Object name] Text Yes Recommend ed digiCULT offers the possibility to label the title (descriptive title, original title, etc.) and thus to ensure a distinction between different types of titles. museumdigital Object title Text Yes Mandatory ID data element mds0001 Object type or designation (mandatory) Definition The object type is the most specific way of describing what an object or work is, specifying as precisely as possible the type of object to which it belongs. Other possible database element names Object name Factual term Text/URI URI (preferred) and/or text (controlled vocabulary) Repeatable Yes Obligation level Mandatory Recording notes The object type indicates what kind of object something is. The term should be taken from a controlled vocabulary. The most specific term in the controlled vocabulary hierarchy should always be used for the object type (as opposed to ). In natural history, the type of taxidermical preparation can Classification be specified in this data element. If the most specific term from the hierarchical ladder of a vocabulary limits the ambiguity of a collection item (e.g. if the indexing institution does CARE: not know the meaning in the country of origin and therefore an unambiguous categorisation is not possible), the superordinate term should be selected in this case. Terminology recommendation Art & Architecture Thesaurus: Objects Facet Integrated Authority File (GND, German National Library), entity type Subject heading sensu stricto. The following search interfaces provide a convenient way to search the GND: (GND-Explorer), (lobid-gnd), (OGND)https://explore.gnd.network/ https://lobid.org/gnd https://swb.bsz-bw.de/DB=2.104/ Wikidata Objektbezeichnungsdatei (For the Object type, the third and possibly the second hierarchy level are particularly suitable.) Examples Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Terminology recommendation Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element URI Preferred term http://vocab.getty.edu/aat/300312262 statuettes (free-standing sculpture) http://vocab.getty.edu/aat/300041402 wood engravings (prints) http://obg.vocnet.org/obg00652 Flugschrift [eng.: Pamphlet] http://obg.vocnet.org/obg00982 Fotoabzug [eng.: Photographic print] https://d-nb.info/gnd/4599991-0 Himmelbett [eng.: Canopy bed] http://vocab.getty.edu/aat/300046012 rings (finger jewelry) https://d-nb.info/gnd/4535319-0 Dermoplastik (Tierpräparat) [eng.: Taxidermy mount] http://vocab.getty.edu/aat/300199921 bread knives http://vocab.getty.edu/aat/300198948 springform pans https://d-nb.info/gnd/4208226-2 Leuchtpistole [eng.: flare pistol] http://www.wikidata.org/entity/Q12760 steam engine http://vocab.getty.edu/aat/300007466 churches (buildings) http://www.wikidata.org/entity/Q73419810 counterfeit coin Expression in LIDO v1.0 <lido:objectWorkTypeWrap> <lido:objectWorkType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">http://vocab.getty.edu/aat /300199921</lido:conceptID> <lido:term xml:lang="de">Brotmesser</lido:term> <lido:term xml:lang="en">bread knives</lido:term> </lido:objectWorkType> </lido:objectWorkTypeWrap> Expression in LIDO v1.1 <lido:objectWorkTypeWrap> <lido:objectWorkType> <skos:Concept rdf:about="http://vocab.getty.edu/aat/300199921"> <skos:prefLabel xml:lang="de">Brotmesser</skos:prefLabel> <skos:prefLabel xml:lang="en">bread knives</skos:prefLabel> </skos:Concept> </lido:objectWorkType> </lido:objectWorkTypeWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata req uirements for data provision Objekttyp Text (controlled vocabulary ) and URI Yes Mandatory German Digital Library LIDO application profile (DDB-LIDO) <objectWorkType> Text (controlled vocabulary ) and URI Yes Mandatory Expression in LIDO (v1.0 and v1.1) <lido:respositoryWrap> <lido:repositorySet lido:type="http://terminology.lido-schema.org/lido00475"> <lido:workID lido:type="http://terminology.lido-schema.org/lido00113">EX 000 230</lido:workID> </lido:repositorySet> </lido:respositoryWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requirements f or data provision (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <repositorySet> / <workID> Text Yes Not mandatory If several inventory numbers are supplied for an object/work (e.g. current and old inventory numbers), these should be typified. This can be done in LIDO using the type attribute of .<workID> CCC-LIDO Application profile Inventory number <repositorySet> / <workID> Text Yes Not mandatory DFG Basic Data Record Source Object Identifier (ID) URI Not specified Mandatory The DFG Basic Data Record allows the assignment of a unique, global and long-term identifier for the analogue source object. DFG Practical Guidelines on Digitisation: LIDO core metadata Repository /location: <repositorySet> / <workID> Text Yes Mandatory, if available Europeana Data Model (EDM) <dc:identifier> Text Yes Recommend ed EODEM application profile Object Identifier /lido: repositoryWrap /lido:repositorySet /lido:workID Text No Mandatory Categories for the Description of Works of Art (2024) 21.2.3. Repository Numbers Text Yes Recommend ed CORE element In , a typification is recommended, e.g. accession 21.2.3.1. Number Type number, shelf number, object identifier or inventory number. CDWA Lite (2006) 14.1.2 Repository Work Identification Number Text Yes Recommend ed Spectrum 5.1 Object number Text No Recommend ed Core element for inventory number, For different kinds of numbers use the element "other number". digiCULT Inventarnummer [eng.: Inventory number] Text Yes Recommend ed The inventory number can either be entered manually in or it digiCULT can be assigned automatically by the system according to a pre-defined scheme. museum-digital Inventory number Text Yes Mandatory In , a suggestion for the inventory number can be museum-digital generated automatically by the system. A consistency check is also performed to avoid duplication of inventory numbers. See also https://de. .handbook.museum-digital.info/ ID data element mds0004 Object description (recommended) Definition Textual description of the object or work Other possible database element names Description Text/URI Text Repeatable Yes Obligation level Recommended (museum-digital: Mandatory) Recording notes The object description should describe the object or work briefly and concisely. It should be written in a way that requires as little prior knowledge as possible and is understandable to a wide audience. The object description should contain as many relevant keywords as possible to make it easier to find the object record in a free text search. If the object description text is subject to special usage rights (e.g. copyright), this should be indicated in a separate data element (in LIDO: , from LIDO v1.1).<lido:objectDescriptionRights> AI writing assistants can be used to generate inclusive description texts. However, the result should always be checked by an editor and amended if necessary. Examples The façade architecture of the cabinet is modelled on ancient theatres. With its ingenious system of compartments and drawers, it was used to store the treasures collected in the Kunstkammer. As well as being functional furniture, the cabinet itself is also a work of art. The ivory panels show extensive imagery: the founders of the four great empires of Antiquity and the deeds of the virtuous ancient hero Hercules. The pull-out writing tablet contains a rotatable world map that refers to the Habsburgs and suggests that the cabinet was made for King Phillip II of Spain. Expression in LIDO v1.0 Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element <lido:objectDescriptionWrap> <lido:objectDescriptionSet> <lido:descriptiveNoteValue xml:lang="de">Die Fassadenarchitektur des Kabinettschranks findet ihr Vorbild im antiken Theaterbau. Mit seinem ausgeklügelten System von Fächern und Schubladen diente er zur Aufbewahrung von gesammelten Kostbarkeiten der Kunstkammer. Über seine Bestimmung zum funktionalen Möbel hinaus ist der Schrank selbst auch als Kunstwerk zu verstehen. Die Elfenbeintafeln zeigen ein umfangreiches Bildprogramm: die Gründer der vier großen Weltreiche des Altertums und die Taten des tugendhaften antiken Helden Herkules. Die ausziehbare Schreibplatte enthält eine drehbare Weltkarte, die auf die Habsburger verweist und vermuten lässt, dass das Kabinettmöbel für König Phillipp II. von Spanien angefertigt worden ist.</lido: descriptiveNoteValue> <lido:descriptiveNoteValue xml:lang="en">The façade architecture of the cabinet is modelled on ancient theatres. With its ingenious system of compartments and drawers, it was used to store the treasures collected in the Kunstkammer. As well as being functional furniture, the cabinet itself is also a work of art. The ivory panels show extensive imagery: the founders of the four great empires of Antiquity and the deeds of the virtuous ancient hero Hercules. The pull-out writing tablet contains a rotatable world map that refers to the Habsburgs and suggests that the cabinet was made for King Phillip II of Spain.</lido:descriptiveNoteValue> </lido:objectDescriptionSet> </lido:objectDescriptionWrap> Expression in LIDO v1.1 (Including <lido:objectDescriptionRights>) <lido:objectDescriptionWrap> <lido:objectDescriptionSet> <lido:descriptiveNoteValue xml:lang="de">Die Fassadenarchitektur des Kabinettschranks findet ihr Vorbild im antiken Theaterbau. Mit seinem ausgeklügelten System von Fächern und Schubladen diente er zur Aufbewahrung von gesammelten Kostbarkeiten der Kunstkammer. Über seine Bestimmung zum funktionalen Möbel hinaus ist der Schrank selbst auch als Kunstwerk zu verstehen. Die Elfenbeintafeln zeigen ein umfangreiches Bildprogramm: die Gründer der vier großen Weltreiche des Altertums und die Taten des tugendhaften antiken Helden Herkules. Die ausziehbare Schreibplatte enthält eine drehbare Weltkarte, die auf die Habsburger verweist und vermuten lässt, dass das Kabinettmöbel für König Phillipp II. von Spanien angefertigt worden ist.</lido: descriptiveNoteValue> <lido:descriptiveNoteValue xml:lang="en">The façade architecture of the cabinet is modelled on ancient theatres. With its ingenious system of compartments and drawers, it was used to store the treasures collected in the Kunstkammer. As well as being functional furniture, the cabinet itself is also a work of art. The ivory panels show extensive imagery: the founders of the four great empires of Antiquity and the deeds of the virtuous ancient hero Hercules. The pull-out writing tablet contains a rotatable world map that refers to the Habsburgs and suggests that the cabinet was made for King Phillip II of Spain.</lido:descriptiveNoteValue> <lido:objectDescriptionRights> <lido:rightsType> <skos:Concept rdf:about="http://creativecommons.org/publicdomain/zero/1.0/"> <skos:prefLabel xml:lang="de">CC0 1.0 Universell</skos:prefLabel> <skos:prefLabel xml:lang="en">CC0 1.0 Universal</skos:prefLabel> </skos:Concept> </lido:rightsType> </lido:objectDescriptionRights> </lido:objectDescriptionSet> </lido:objectDescriptionWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requirements fo r data provision (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <objectDescriptionSet> /<descriptiveNoteValue> Text Yes Conditionally mandatory Recommend ed Mandatory if sub-elements exist. CCC-LIDO Application profile Description <objectDescriptionSet> /<descriptiveNoteValue> Text Yes Recommend ed DFG Basic Data Record Source Object Description URI Not specified Recommend ed DFG Practical Guidelines on Digitisation: LIDO core metadata Object description <objectDescriptionSet> Text and/or URI Yes Recommend ed Europeana Data Model (EDM) <dc:description> Text Yes Conditionally mandatory In (Object title) OR Europeana Data Model <dc:title> <dc: (Object description) are mandatory.description> EODEM application profile Brief Description /lido:objectDescriptionWrap /lido:objectDescriptionSet/ lido: descriptiveNoteValue No Recommend ed Categories for the Description of Works of Art (2024) 18.1. Descriptive Note Text Text No Not mandatory Additional elements are recommended to describe specific aspects: Abstract Description, Pagination Description, Foliation Description, Extent Description, Arrangement Description. CDWA Lite (2006) 17.1 Description/Descriptive Note Set Text Yes Not mandatory Spectrum 5.1 Brief description Physical description Text No Recommend ed "Brief description" is a core element. The obligation level is determined by the institution. digiCULT Beschreibung [eng.: Description] Text Yes Recommend ed In , for legal reasons, when data is made digiCULT available via the OAI interface, the description is not included by default. museum-digital Description Text No Mandatory In the object description is mandatory. museum-digital The text has a minimum length of 25 characters. ID data element mds0005 Materials (recommended) Definition An indication of the materials from which an object or work is made Text/URI Text (controlled vocabulary) and/or URI Repeatable Yes Obligation level Recommended Recording notes This data element indicates the materials from which the object or work was or is made or is composed of. Controlled vocabulary is recommended. This supports better findability in portals. Terminology recommendation Art & Architecture Thesaurus: Materials Facet Integrated Authority File (GND, German National Library): The following search interfaces provide a convenient way to search the GND: https://explore.gnd. (GND-Explorer), (lobid-gnd), (OGND)network/ https://lobid.org/gnd https://swb.bsz-bw.de/DB=2.104/ Wikidata Examples URI Preferred term http://vocab.getty.edu/aat/300011029 silver (metal) https://d-nb.info/gnd/4350482-6 Bast [engl.: Bast] https://d-nb.info/gnd/4144643-4 Bergkristall [engl.: Rock crystal] https://d-nb.info/gnd/4152058-0 Email (Beschichtung) [eng: Enamel and enameling < >]LCSH match https://d-nb.info/gnd/4033676-1 Kunststoff [eng: Plastics < >]LCSH match http://vocab.getty.edu/aat/300015062 tempera http://www.wikidata.org/entity/Q28129555 zinc sheet Contents Definition Text/URI Repeatable Obligation level Recording notes Terminology recommendation Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element https://d-nb.info/gnd/118728372X Elektron (Legierung) [eng: Elektrum < >]LCSH match Expression in LIDO v1.0 <lido:eventMaterialsTech> <lido:materialsTech> <lido:termMaterialsTech lido:type="http://terminology.lido-schema.org/lido00132"> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">http://vocab. getty.edu/aat/300011029</lido:conceptID> <lido:term xml:lang="de">Silber</lido:term> <lido:term xml:lang="en">silver (metal)</lido:term> </lido:termMaterialsTech> </lido:materialsTech> </lido:eventMaterialsTech> Expression in LIDO v1.1 <lido:eventMaterialsTech> <lido:materialsTech> <lido:termMaterialsTech type="http://terminology.lido-schema.org/lido00132"> <skos:Concept rdf:about="http://vocab.getty.edu/aat/300011029"> <skos:prefLabel xml:lang="de">Silber</skos:prefLabel> <skos:prefLabel xml:lang="en">silver (metal)</skos:prefLabel> </skos:Concept> </lido:termMaterialsTech> </lido:materialsTech> </lido:eventMaterialsTech> Example of an event-independent materials specification <lido:objectMaterialsTechWrap> <lido:objectMaterialsTechSet> <lido:materialsTech> <lido:termMaterialsTech lido:type="http://terminology.lido-schema.org/lido00132"> <skos:Concept rdf:about="http://vocab.getty.edu/aat/300011029"> <skos:prefLabel xml:lang="de">Silber</skos:prefLabel> <skos:prefLabel xml:lang="en">silver (metal)</skos:prefLabel> </skos:Concept> </lido:termMaterialsTech> </lido:materialsTech> </lido:objectMaterialsTechSet> </lido:objectMaterialsTechWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata req uirements for data provision (No match) Not applicable Not applicable Not mandatory German Digital Library LIDO application profile (DDB-LIDO) <eventMaterialsTech> / <materialsTech> / <termMaterialsTech> / <term> Text (controlled vocabulary) and optional URI Yes Not mandatory Optional labelling: http://terminology.lido-schema.org for Materials/lido00132 CCC-LIDO Application profile Material/Technique <eventMaterialsTech> / <materialsTech> / <termMaterialsTech> / <term> and <conceptID> Text (controlled vocabulary) and optional URI (AAT) Yes Not mandatory DFG Basic Data Record (No match) Not applicable Not applicable Not mandatory DFG Practical Guidelines on Digitisation: LIDO core metadata Information on materials and techniques relating to event <eventMaterialsTech> Text (controlled vocabulary) and /or URI Yes Mandatory if available Alternatively, the information on material and/or technology in <objectMaterialsTechWrap> / <objectMaterialsTechSet> is also possible independently of the event. Europeana Data Model (EDM) < >dcterms:medium Text (controlled vocabulary) Yes Not mandatory EODEM application profile Material Description /lido:objectMaterialsTechWrap /lido:objectMaterialsTechSet/ lido:displayMaterialsTech/ Text Yes Recommend ed Categories for the Description of Works of Art (2024) 7.5 Materials/Techniques Name Text (controlled vocabulary) Yes Recommend ed 7.1. Materials/Techniques Description is listed as COREElement. Vocabulary recommendation: Art & Architecture Thesaurus or general terms in another controlled vocabulary. CDWA Lite (2006) 8.1.1 Term Materials Techniques Text (controlled vocabulary) Yes Not mandatory Vocabulary recommendation: Art & Architecture Thesaurus. Spectrum 5.1 Material Text (controlled vocabulary) Yes Not specified The obligation level is determined by the institution. digiCULT Material [eng.: Materials] Text (controlled vocabulary) and /or URI Yes Recommend ed museum-digital Materials/Technique Materials Schlagwort (Material) [eng.: tags (material)] Text Yes Recommend ed Materials and techniques can be recorded in museumin different ways: Either in one or in two separate digital data fields; recently it has also become possible to record them as a "categorised keyword". See . this blog post ID data element mds0006 Techniques (recommended) Definition Indication of the technique used in the production, preparation or preservation/storage of the object or work Other possible database element names Production technique Type of preparation Type of storage Text/URI Text (controlled vocabulary) and/or URI Repeatable Yes Obligation level Recommended Recording notes This data element indicates the techniques with which the object was produced, prepared or preserved/stored. Controlled vocabulary is recommended. This supports better findability in portals. Terminology recommendation Art & Architecture Thesaurus: Activities Facet, hierarchy name: Processes and Techniques Integrated Authority File (GND, German National Library): The following search interfaces provide a convenient way to search the GND: https://explore.gnd. (GND-Explorer), (lobid-gnd), (OGND)network/ https://lobid.org/gnd https://swb.bsz-bw.de/DB=2.104/ Wikidata Examples URI Vorzugsbezeichnung https://d-nb.info/gnd/4133335-4 Offsetdruck [eng: Offset printing < >]LCSH match Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Terminology recommendation Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element http://vocab.getty.edu/aat/300206846 striking (metalworking) http://vocab.getty.edu/aat/300053418 heightening http://vocab.getty.edu/aat/300053242 aquatint (printing process) https://d-nb.info/gnd/4012912-3 Drechseln [eng: Turning (Lathe work) < >]LCSH match https://d-nb.info/gnd/4153775-0 Fassmalerei [eng: Polychromy < >]LCSH match http://www.wikidata.org/entity/Q1259197 wood engraving technique http://vocab.getty.edu/aat/300053991 plating (metal coating) http://vocab.getty.edu/aat/300053400 priming (coating process) https://d-nb.info/gnd/7511674-1 Tierpräparation [eng.: Taxidermy] Expression in LIDO v1.0 <lido:eventMaterialsTech> <lido:materialsTech> <lido:termMaterialsTech lido:type="http://terminology.lido-schema.org/lido00131"> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">https://d-nb.info /gnd/4133335-4</lido:conceptID> <lido:term xml:lang="de">Offsetdruck</lido:term> <lido:term xml:lang="en">offset printing</lido:term> </lido:termMaterialsTech> </lido:materialsTech> </lido:eventMaterialsTech> Expression in LIDO v1.1 <lido:eventMaterialsTech> <lido:materialsTech> <lido:termMaterialsTech lido:type="http://terminology.lido-schema.org/lido00131"> <skos:Concept rdf:about="https://d-nb.info/gnd/4133335-4"> <skos:prefLabel xml:lang="de">Offsetdruck</skos:prefLabel> <skos:prefLabel xml:lang="en">offset printing</skos:prefLabel> </skos:Concept> </lido:termMaterialsTech> </lido:materialsTech> </lido:eventMaterialsTech> Example of an event-independent technique <lido:objectMaterialsTechWrap> <lido:objectMaterialsTechSet> <lido:materialsTech> <lido:termMaterialsTech lido:type="http://terminology.lido-schema.org/lido00131"> <skos:Concept rdf:about="https://d-nb.info/gnd/4133335-4"> <skos:prefLabel xml:lang="de">Offsetdruck</skos:prefLabel> <skos:prefLabel xml:lang="en">offset printing</skos:prefLabel> </skos:Concept> </lido:termMaterialsTech> </lido:materialsTech> </lido:objectMaterialsTechSet> </lido:objectMaterialsTechWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata req uirements for data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <eventMaterialsTech> / <materialsTech> / <termMaterialsTech> / <term> Text (controlled vocabulary) and optional URI Yes Not mandatory Optional labelling: http://terminology.lido-schema.org for Techniques/lido00131 CCC-LIDO Application profile Material/Techniques <eventMaterialsTech> / <materialsTech> / <termMaterialsTech> / <term> und <conceptID> Text (controlled vocabulary) and optional URI (AAT) Yes Not mandatory DFG Basic Data Record (No match) Not applicable Not applicable Not mandatory DFG Practical Guidelines on Digitisation: LIDO core metadata Information on materials and techniques relating to event <eventMaterialsTech> Text (controlled vocabulary) and /or URI Yes Mandatory if available Alternatively, the information on material and/or technology in <objectMaterialsTechWrap> / <objectMaterialsTechSet> is also possible independently of the event. Europeana Data Model (EDM) <dcterms:medium> Text (controlled vocabulary) Yes Not mandatory EODEM application profile Material Description /lido:objectMaterialsTechWrap /lido:objectMaterialsTechSet/ lido:displayMaterialsTech/ Text Yes Recommend ed Categories for the Description of Works of Art (2024) 7.5 Materials/Techniques Name Text (controlled vocabulary) Yes Recommend ed 7.1. Materials/Techniques Description is listed as COREElement. Vocabulary recommendation: Art & Architecture Thesaurus or general terms in another controlled vocabulary. CDWA Lite (2006) 8.1.1 Term Materials Techniques Text (controlled vocabulary) Yes Not mandatory Vocabulary recommendation: Art & Architecture Thesaurus. Spectrum 5.1 Technique Text (controlled vocabulary) Yes Not specified The obligation level is determined by the institution. digiCULT Technik [engl.: Technique] Text (controlled vocabulary) and /or URI Yes Recommend ed museum-digital Materials/Technique Technique Keyword (technique) Text Yes Recommend ed Materials and techniques can be recorded in museumin different ways: Either in one or in two separate digital data fields; recently it has also become possible to record them as a "categorised keyword". See . this blog post ID data element mds0007 <lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventType> <skos:Concept rdf:about="http://terminology.lido-schema.org/lido00007"> <skos:prefLabel xml:lang="de">Herstellung</skos:prefLabel> <skos:prefLabel xml:lang="en">Production</skos:prefLabel> </skos:Concept> </lido:eventType> <lido:eventActor> <lido:actorInRole> <lido:actor> <lido:actorID lido:type="http://terminology.lido-schema.org /lido00099">https://d-nb.info/gnd/24495-8</lido:actorID> <lido:nameActorSet> <lido:appellationValue xml:lang="de">Nixdorf Computer AG</lido:appellationValue> <lido:appellationValue xml:lang="en">Nixdorf Computer AG< /lido:appellationValue> </lido:nameActorSet> </lido:actor> </lido:actorInRole> </lido:eventActor> <lido:eventDate> <lido:date> <lido:earliestDate>1983</lido:earliestDate> <lido:latestDate>1983</lido:latestDate> </lido:date> </lido:eventDate> <lido:eventPlace> <lido:place> <lido:placeID lido:type="http://terminology.lido-schema.org/lido00099" >https://sws.geonames.org/2855745/</lido:placeID> <lido:namePlaceSet> <lido:appellationValue xml:lang="de">Paderborn</lido: appellationValue> <lido:appellationValue xml:lang="en">Paderborn</lido: appellationValue> </lido:namePlaceSet> </lido:place> </lido:eventPlace> </lido:event> </lido:eventSet> </lido:eventWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Requirements for data provided (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <eventWrap> Not applica ble Yes (<eventSet>) Conditionally mandatory Recommend ed Mandatory if sub-elements exist. CCC-LIDO Application profile <eventWrap> Not applica ble Yes (<eventSet>) Conditionall y mandatory Recommend ed DFG Basic Data Record (No match, see comment) Not applica ble Not applicable Recommend ed (see comment) The German Research Foundation recommends documenting a central “relevant” event by specifying a location, naming “relevant” persons (with details of their role) and specifying a “time of origin”. DFG Practical Guidelines on Digitisation: LIDO core metadata Event lido:eventSet /lido:event Not applica ble Yes Mandatory if available Europeana Data Model (EDM) (<edm:Event>) Not applica ble Yes Not mandatory Europeana not (yet) uses <edm:Event>. This recommends the report introduction of <edm:Event>. EODEM application profile Object Production Group /lido: eventWrap /lido:eventSet /lido:event Not applica ble No Mandatory EODEM includes a production event (Object Production Group). Categories for the Description of Works of Art (2024) 4 Creation 17.1 Historical /Cultural Events 23 Ownership /Collecting History Not applica ble No/No specification Recommend ed CORE-Element: Creation CDWA Lite (2006) (No match) Not applica ble Not applicable Not applicable The creation of the object is documented in the following elements: 3rd Display Creator (mandatory) and 4th Indexing Creator Wrapper (mandatory), 12th Display Creation Date (mandatory) and 13th Indexing Dates Wrapper (mandatory). Spectrum 5.1 Object production information Acquisition information Object collection information Common Procedural Units Text Yes Not specified The obligation level is determined by the institution. digiCULT Ereignis [eng.: Event] Not applica ble Yes Recommend ed museum-digital Event Not applica ble No Recommend ed Event type (mandatory) Definition Type of event in the history of the object Other possible database element names Type of event Text/URI Text and/or URI Repeatable No, only one Event type per event Obligation level Mandatory Recording notes For specifying the event type, the use of the event type vocabulary from the is recommended. A German and an English preferred term LIDO terminology as well as a persistent URI are provided for each event type. : If nothing more is known about the provenance and date of an object beyond its access to the collection, an appropriate event type should be CARE selected. Gaps in knowledge of the object's history should always be disclosed (e. g. by entering "not documented" or "not known to us" in the "person /entity", "date", "place" data elements). Uncertainties or attributions, e.g. from the surviving collection entry documentation, should be contextualised in a separate data element "Event description" (in LIDO: ).<lido:eventDescriptionSet>/<descriptiveNoteValue> Terminology recommendations LIDO terminology (for eventType) Examples URI Preferred term http://terminology.lido-schema.org/lido00007 Production http://terminology.lido-schema.org/lido00002 Finding (Activity) http://terminology.lido-schema.org/lido01151 Change of physical control or legal title Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Terminology recommendations Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element http://terminology.lido-schema.org/lido00006 Modification (Activity) http://terminology.lido-schema.org/lido00033 Excavation http://terminology.lido-schema.org/lido00011 Use Expression in LIDO v1.0 <lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099" >http://terminology.lido-schema.org/lido00007</lido:conceptID> <lido:term xml:lang="de">Herstellung</lido:term> <lido:term xml:lang="en">Production</lido:term> </lido:eventType> </lido:event> </lido:eventSet> </lido:eventWrap> Expression in LIDO v1.1 <lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventType> <skos:Concept rdf:about="http://terminology.lido-schema.org/lido00007"> <skos:prefLabel xml:lang="de">Herstellung</skos:prefLabel> <skos:prefLabel xml:lang="en">Production</skos:prefLabel> </skos:Concept> </lido:eventType> </lido:event> </lido:eventSet> </lido:eventWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requi rements for data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <eventType> / <conceptID> Text (controlled vocabulary) and URI No Conditionally mandatory Recommend ed Mandatory if <eventWrap> exists. The event type cannot be repeated within an event. Any number of events can be assigned to an object. CCC-LIDO Application profile <eventType> / <conceptID> Text (controlled vocabulary) and URI No Conditionally mandatory Recommend ed DFG Basic Data Record (No match, see comment) Not applicable Not applicable Recommend ed The German Research Foundation recommends documenting a central “relevant” event by specifying a location, naming a “relevant” person (with details of their role) and specifying a “time of origin”. Depending on the context, this is “production”, “find” or “collecting”. DFG Practical Guidelines on Digitisation: LIDO core metadata Event lido:eventSet/lido: event/lido:eventType Text (controlled vocabulary) and URI No Mandatory if available Europeana Data Model (EDM) ../edm:Event/edm: hasType Text and/or URI Yes Not mandatory Europeana not (yet) uses <edm:Event>. This report recommends the introduction of <edm:Event>. EODEM application profile Object Production Group /lido:eventType/lido: conceptID /lido:eventType/lido: term Text (controlled vocabulary) and/or URI No Mandatory EODEM includes a production event (Object Production Group). Categories for the Description of Works of Art (2024) 4 Creation 17.1.1 Event Type 23 Ownership /Collecting History Text (controlled vocabulary) No Recommend ed/Not mandatory CORE element: Creation Event Type: Vocabulary recommendation: Art & Architecture , in particular the hierarchies Events <Thesaurus http://vocab.getty.edu > and Associated Concepts < /hier/aat/300054722 http://vocab.getty. >edu/hier/aat/300055126 CDWA Lite (2006) (No match) Not applicable Not applicable Not applicable Spectrum 5.1 (No match for a number of relevant events, see comment) Procedure title Text Yes Not specified The event type can be derived from the element sets Object , ,production information Acquisition information Object collection and other Spectrum procedures.information The obligation level is determined by the institution. digiCULT (Data element name is determined by the event type) Text (controlled vocabulary) and URI No Recommend ed museum-digital (Data element name is determined by the event type) Text (controlled vocabulary) and URI No Recommend ed Museum-digital database provides its own vocabulary for event types: .https://event-types.museum-digital.org/ ID data element mds0009 Person/corporate body (conditionally mandatory) Definition In the history of the object, the person or corporate body involved in the event described Other possible database element names Artist Producer Organisation Name of the person involved Name of the institution Owner Text/URI Text and/or URI Repeatable Yes Obligation level At least one event in the history of the object is mandatory. In addition to the Event type, each event must have at least one "who", "where" or "when". Recording notes It is recommended to specify names of persons/corporate bodies both in a text element and separately using URIs from authority files. There are various recommendations for specifying preferred names, depending on the application. An important reference is the (GND). Integrated Authority File In the case of data delivery to the , the delivery of URIs from the is strongly recommended for the German Digital Library Integrated Authority File identification of persons and corporate bodies. It is recommended that the role played by the person/corporate body mentioned in the described event in the object history is specified in a separate element. If this is not possible, the role specification should be added to the name in such a way that it can be extracted rule-based during export, e.g. "Last name, first name (role: [role name])". If the person/corporate body that produced the object cannot be identified, a separate data element (in LIDO: ) should be used to specify the <lido:culture> geographical, stylistic or cultural attribution of the object, if possible. Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Terminology recommendation Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element : CARE Knowledge gaps in the object's history should always be disclosed (e.g. by stating “not documented” or “not known to us” in the data elements “Person/entity”, “Date”, “Location”). Uncertainties or attributions that originate, for example, from the surviving collection entry documentation should be contextualized in a separate data element “Event description” (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>). If the persons/corporate bodies involved can be researched and identified retrospectively, but do not have a unique identifier in the , collaborative Integrated Authority File knowledge databases such as are suitable for generating unique identifiers.Wikidata Terminology recommendation Integrated Authority File (GND, German National Library): The following search interfaces provide a convenient way to search the GND: https://explore.gnd. network/ (GND-Explorer), (lobid-gnd), (OGND). German Digital Library: Preferred name in https://lobid.org/gnd https://swb.bsz-bw.de/DB=2.104/ Entity is decisive.Facts Union List of Artist Names (for persons and corporate bodies active in various functions in the arts) Virtual International Authority File Wikidata Examples URI Preferred name https://d-nb.info/gnd/1048652033 Hinghaus, Walter http://vocab.getty.edu/ulan/500593279 Zippel, Eva http://www.wikidata.org/entity/Q5594 Antonello da Messina https://d-nb.info/gnd/118521713 Commodus, Romisches Reich, Kaiser [eng.: Commodus, Emperor of Rome, 161-192] https://d-nb.info/gnd/119904489X Kotys II., Bosporanisches Reich, König [eng.: Cotys II, Bosporan Kingdom] https://d-nb.info/gnd/2120183-3 Gilbert & George http://vocab.getty.edu/ulan/500524769 Royal Porcelain Manufactory, Berlin https://d-nb.info/gnd/83740-4 Artaria & Fontaine à Mannheim (Firma) [engl.: Artaria & Fontaine, Bookseller in Mannheim] https://d-nb.info/gnd/24495-8 Nixdorf Computer AG Expression in LIDO (v1.0 and v1.1) <lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventActor> <lido:actorInRole> <lido:actor> <lido:actorID lido:type="http://terminology.lido-schema.org/lido00099">https://dnb.info/gnd/24495-8</lido:actorID> <lido:nameActorSet> <lido:appellationValue xml:lang="de">Nixdorf Computer AG</lido: appellationValue> <lido:appellationValue xml:lang="en">Nixdorf Computer AG</lido:appellationValue> </lido:nameActorSet> </lido:actor> </lido:actorInRole> </lido:eventActor> </lido:event> </lido:eventSet> </lido:eventWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata re quirements for data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <eventActor> Text (controlled vocabulary) and/or URI Yes Conditionally mandatory Mandatory if sub-elements exist. GND IDs are the basis for creating or linking to entity in pages, for instance on persons or corporate bodies, the portal. In the CCC-Lido application profile, only values from controlled vocabularies (GND) are transferred to the ‘Person/organisation’ search filter. CCC-LIDO Application profile who <eventActor> Text (controlled vocabulary) and/or URI (GND) Yes Conditionall y mandatory DFG Basic Data Record Source Object Relevant Person Text (controlled vocabulary) and/or URI Yes Recommend ed DFG Practical Guidelines on Digitisation: LIDO core metadata Identifiable actors involved in the event <eventSet> / <event> / <eventActor> Text (controlled vocabulary) and/or URI Yes Mandatory if available The DFG Practical Guidelines on Digitisation recommend that additional information on the cultural context in the LIDO-Element is provided, <culture> especially if no specific producer or user of the object can be named. Europeana Data Model (EDM) <dc:creator> <dc:contributor> <dc:publisher> <edm:agent> Text (controlled vocabulary) and/or URI Yes Recommend ed EODEM application profile Maker Identifier, Maker Sort Name /lido:eventActor/lido:actorInRole /lido:actor/lido:actorID /lido:eventActor/lido:actorInRole /lido:actor/ lido:nameActorSet/lido: appellationValue Text (controlled vocabulary) and/or URI Yes Not mandatory Categories for the Description of Works of Art (2024) Production: 4.1. Creator Description and sub-elements Commissioning: 4.5 Commissioner Excavation: 17.3.3 Excavator Other events: 17.1.5. Event Agent Text (controlled vocabulary) Yes Recommend ed CORE elements: 4.1.3 Creator Identity and 4.1.4 Creator Role Vocabulary recommendation: Union List of Artist Names and other standardised files on persons and corporate bodies. CDWA Lite (2006) 4.1.1.1 Name of Creator Text (controlled vocabulary) Yes Mandatory If several creators are specified, 4.1.1 Name Creator Set is repeated. Vocabulary recommendation: Union List of Artist Names and other standard files on persons and corporate bodies. Spectrum 5.1 Organisation information Person information Procedure manager People information Text (controlled vocabulary) Yes Not specified There are specified elements for information on persons and organisations in the element sets Object production information, Acquisition information, Object collection information and other Spectrum procedures. The obligation level is determined by the institution. digiCULT Künstler/Hersteller/Vorbesitzer etc. (actorInRole) [engl.: Artist /Producer/Previous owner etc. (actorInRole)] Text (controlled vocabulary) and/or URI Yes Recommend ed museum-digital Who? Text (controlled vocabulary) and URI Yes Recommend ed ID data element mds0010 Date (conditionally mandatory) Definition Date (precise date or time period) when the event in the object history occurred Other possible database element names Date / Period Times Date of production Date of origin Text/URI Text (Date format; requested) ISO 8601 Repeatable No Obligation level At least one event in the history of the object is mandatory. In addition to the Event type, each event must have at least one "who", "where" or "when". Recording notes Date entries are made in standardized format (preferably ).ISO 8601 Time spans are specified in two separate data elements. The first data element contains the earliest possible or known date and the second data element contains the latest possible or known date on which the event in the history of the object occurred. Date information can also be entered in free text form (for uncertain information, periods/epochs, etc.). This is recorded in a separate data field (in LIDO: <lido:displayDate> for verbal information or <lido:periodName> for periods/epochs respectively). : CARE Knowledge gaps in the object's history should always be disclosed (e.g. by stating “not documented” or “not known to us” in the data elements “Person/entity”, “Date”, “Location”). Uncertainties or attributions that originate from the surviving documentation of the collection entry, for example, should be contextualized in a separate data element “Event description” (in LIDO: <lido:eventDescriptionSet>/<descriptiveNoteValue>). Format recommendation ISO 8601 Extended Date/Time Format (EDTF) Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Format recommendation Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element Examples 1801/1900 1969-07-21/1969-08-15 -377/-299 1983/1987 1983 1596/1605 Expression in LIDO (v1.0 and v1.1) <lido:eventWrap> <lido:eventSet> <lido:event> <lido:eventDate> <lido:date> <lido:earliestDate>1983</lido:earliestDate> <lido:latestDate>1983</lido:latestDate> </lido:date> </lido:eventDate> </lido:event> </lido:eventSet> </lido:eventWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requi rements for data provision (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <eventDate> Text No Conditionally mandatory Mandatory if sub-elements exist. CCC-LIDO Application profile when <eventDate> Text No Conditionally mandatory DFG Basic Data Record Source Object Time of Origin Text Not specified Recommend ed DFG Practical Guidelines on Digitisation: LIDO core metadata Time period of event <eventDate> Text No Mandatory, if available The DFG Practical Guidelines on Digitisation require additional date information in text form where such information is available, in which any inaccuracies can be expressed. The LIDO element <eventDate> /<displayDate> is used for this purpose. An indication of the period of the event in the LIDO element <periodName> is recommended. Europeana Data Model (EDM) <dc:date> <dcterms:created> <dcterms:issued> <edm:TimeSpan> Text and/or URI Ja Not mandatory EODEM application profile Earliest Production Date und Latest Production Date /lido:eventDate/lido: date/lido:earliestDate und /lido:latestDate Text No Not mandatory Corresponds largely to the elements 12. Element: Display Creation Date and 13.1.2 Sub-element: Earliest Date as well as 13.1.3 Sub-element: Latest Date in CDWA Lite for the dating of the object's production. <lido:objectRelationWrap> <lido:subjectWrap> <lido:subjectSet> <lido:subject lido:type="http://terminology.lido-schema.org/lido00525"> <lido:subjectConcept> <skos:Concept rdf:about="http://vocab.getty.edu/aat/300008626"> <skos:prefLabel xml:lang="de">Landschaft (Lebensraum)</skos: prefLabel> <skos:prefLabel xml:lang="en">landscapes (environments)</skos: prefLabel> </skos:Concept> </lido:subjectConcept> </lido:subject> </lido:subjectSet> </lido:subjectWrap> </lido:objectRelationWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata re quirements f or data provision (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <subjectCo ncept> Text (control led vocabu lary) and URI Yes Conditionally mandatory Mandatory if sub-elements exist. CCC-LIDO Application profile (No match) Not applica ble Not applicable Not applicable DFG Basic Data Record Source Object Type of Content Text and/or URI Not specified Recommend ed In the , "Source Object Type of Content" is only recommended in the DFG Basic Data Record 'digital-mix' category. This only partly corresponds to the "Subject keyword" data element. DFG Practical Guidelines on Digitisation: LIDO core metadata Theme / Content <subjectSet> Text and/or URI Yes Mandatory if available In the , the indexing of general terms in the LIDO DFG Practical Guidelines on Digitisation element <subjectConcept> or of individual terms for persons/corporate bodies in <subjectActor>, places in <subjectPlace>, events in <subjectEvent>, objects in <subjectObject> or dates in <subjectDate> is mandatory if the information is available. Europeana Data Model (EDM) dc:subject Text (control led vocabu lary) and/or URI Yes Conditionally mandatory In the Europeana Data Model <dc:subject> (subject keyword/classification) OR <dc:type> (objec t type) OR <dcterms:spatial> (keyword [place/location depicted/represented]) OR <dcterms: temporal>(keyword [time depicted/as subject]) are mandatory. EODEM application profile (No match) Not applica ble Not applicable Not mandatory Categories for the Description of Works of Art (2024) 16.2. General Subject Terms 16.3. Specific Subject Terms Text (control led vocabu lary) Yes Recommend ed CORE-Element: 16.2. General Subject Terms) Vocabulary recommendation: , Art & Architecture Thesaurus Iconclass or general terms in another controlled vocabulary or standard vocabularies for persons, places, etc. CDWA Lite ( 2006) 15.1.2 Inde xing Subject Term Text (control led vocabu lary) Yes Recommend ed Vocabulary recommendation: , Art & Architecture Thesaurus Iconclass or general terms in another controlled vocabulary or standard vocabularies for persons, places, etc. Spectrum 5.1 Content - concept Content - activity Content - person Content - place Content - object Text (control led vocabu lary) Yes Not specified More elements for differentiated content indexing are available under Object description .information The obligation level is determined by the institution. digiCULT Darstellung [eng.: Representat ion] Ikonographi e [eng.: Iconograph y] Text (control led vocabu lary) and/or URI Yes Recommend ed The data element "Representation" in is is a kind of element set consisting of digiCULT iconography, depicted place, depicted person, depicted date and annotation. museumdigital Keyword or relation Text (control led vocabu lary) and/or URI Yes Recommend ed museum-digital recommends that keywords should be used in singular, lemmatised form; no diminutives or word formations on '-like' or '-shaped' should be used, and keywords should not be concatenated or embedded in hierarchical structures. See: https://de.handbook.museum- . In PUQI, a data quality measurement procedure and manual for improving data digital.info quality in museum-digital, three to nine keywords are recommended. does not Museum-digital make a distinction between “keyword” and “subject category”, contrary to the Minimum Record Recommendation. ID data element mds0013 Media file [element set] (mandatory) Data elements (cataloguing) Link to media file (mandatory) Usage rights of media file (mandatory) Rights holder of media file (conditionally mandatory) Alternative text (recommended) Data elements (export) Media file: type of media file (mandatory) Link to media file (mandatory) Definition Digital representation (e.g. digital image, video, 3D object, audio file) of the cultural heritage object, which is accessed via a direct stable link Other possible database element names Link to the digital object ID digital copy Medium Image Text/URI URI Repeatable Yes Obligation level Mandatory Recording notes The media file should be made available via a persistent URL. If a link cannot be provided, an alternative delivery method for the media file should be agreed with portals or other data recipients. If different images, videos, etc. are available, several media files may be provided. In this case, the file with the best available quality should be selected. If necessary, additional media files for subtitles, audio description and transcription can be provided for reasons of digital accessibility of audio and video files. : Sensitive items, such as religious or ritual artefacts, that are not appropriate for viewing or should be reserved for a specific group of people, CARE may not be published with an image. A placeholder image may be used instead (see expressions in LIDO). Institutions should consult with people from the communities of origin. Ideally, ethical considerations should be documented in the database. Examples https://fotothek.slub-dresden.de/fotos/df/pos-2019-a/0000000/df_pos-2019-a_0000108.jpg http://skd-online-collection.skd.museum/imagescreate/image?id=1218449&type=gross https://brandenburg.museum-digital.de/data/brandenburg/images/63/67099-ex_002_213/wolkensituation_6b_919_m/wolkensituation-6b-919-m-67099.jpg http://www.tierstimmenarchiv.de/recordings/Pavo_cristatus_Kr0063_01_short.mp3 (Audio) https://st.museum-digital.de/singleimage?resourcenr=1954&noiiif=1 (3D) Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element Expression in LIDO (v1.0 and v1.1) <lido:resourceWrap> <lido:resourceSet lido:sortorder="1"> <lido:resourceRepresentation lido:type="http://terminology.lido-schema.org/lido00464"> <lido:linkResource lido:formatResource="image/png">https://www.bruecke-museum.de/ds-images /61779_front.png</lido:linkResource> </lido:resourceRepresentation> </lido:resourceSet> </lido:resourceWrap> CARE: Example from the portal "Collections in Colonial Contexts": <lido:resourceWrap> <lido:resourceSet lido:sortorder="1"> <lido:resourceRepresentation lido:type="http://terminology.lido-schema.org/lido00467"> <lido:linkResource lido:formatResource="text/html">https://ccc.deutsche-digitale-bibliothek.de/< /lido:linkResource> </lido:resourceRepresentation> </lido:resourceSet> </lido:resourceWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata r equirements for data provision Vorschaubild [eng.: Preview image] Link zum digitalen Objekt: Mediendatei [eng.: Digital object link: media file] URI Yes Conditionally mandatory (see Comment) Either a link to the or to the or to the media file object in the media viewer objec is mandatory. A preview image is also mandatory for audio and t in context video files and 3D objects. German Digital Library LIDO application profile (DDB-LIDO) <resourceSet> / <resourceRepresentat ion> / <linkResource> URI Yes Conditionally mandatory (see Comment) Mandatory if is not available. A preview image is also <recordInfoLink> mandatory for audio and video files and 3D objects. CCC-LIDO Application profile <resourceSet> / <resourceRepresentat ion> / <linkResource> URI Yes Conditionally mandatory (see Comment) DFG Basic Data Record Digital copy identier (ID) URI Not specified Mandatory The "Digital Copy Identifier (ID)" should resolve as a LOD URI for the digitised item. DFG Practical Guidelines on Digitisation: LIDO core metadata Representations: <resourceSet> / <resourceRepresentat ion> URI Yes Mandatory if available Europeana Data Model (EDM) <edm:isShownBy> URI Yes Conditionally mandatory In the (EDM) EITHER <edm:isShownBy> OR <edm:Europeana Data Model isShownAt> must be available. EODEM application profile Image /lido:resourceWrap /lido:resourceSet/ lido: resourceRepresentati on/lido:linkResource Text or URI No Mandatory Categories for the Description of Works of Art (2024) (No equivalent) Not applica ble Not applicable Not applicable A persistent URL is not provided for in the Categories for the Description of . Instead, the media file can be identified in various elements of Works of Art group 26.2 Image Label/Identification https://www.getty.edu/publications /categories-description-works-art/categories/object-architecture-group/26/#s26- .2 CDWA Lite (2006) 22.1.1 Link Resource Text No Not mandatory Spectrum 5.1 Reproduction number Text No Not specified The obligation level is determined by the institution. digiCULT Medium URI Yes Recommend ed museum-digital Image, PDF, Video, Audio, 3D-object URI Yes Mandatory ID data element mds0014 Usage rights of media file (mandatory) Definition Indication of copyright status and usage rights of the digital representation Other possible database element names Legal status of media file Terms of use media file Licence Rights information media file Legal status of the image Rights table Text/URI URI + optionally text (controlled vocabulary) Repeatable No, only one rights statement per media file Obligation level Mandatory Recording notes This data element specifies a valid rights notice or licence for the media file. This indicates the extent to which the media file may be used. If you are planning to deliver data to the , you have to select a licence or rights statement from German Digital Library Rechteangaben in der Deutschen [eng.: Rights statements in the German Digital Library].Digitalen Bibliothek The rights to the cultural heritage object (e.g. a painting) are included in the media file that digitally represents the object. If the cultural heritage object is (still) protected by copyright, the author and the holder of the rights of use of the cultural heritage object must always be stated. This is done in a separate data element (in LIDO: ). If the cultural heritage object is in the public domain and is not a three-dimensional <lido:rightsWorkSet> / <lido:rightsHolder> object (for such objects, reproduction may involve a threshold of originality), no new rights will normally arise in the digital representation or media file. Further information can be found in the publication [eng.: In motion. In Bewegung. Die Rechtsfibel für Digitalisierungsprojekte in Kulturerbe-Einrichtungen The legal primer for digitisation projects in cultural heritage institutions]. In addition, the can be contacted with legal NFDI4Culture Legal Helpdesk questions relating to the publication of digitised cultural material. The of the German Digital Library is available to answer rlegal department legal questions elated to the delivery of data to the German Digital Library. Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Lists Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element : In the case of collection items from colonial contexts, the primary cultural sovereignty lies with the communities of origin. The „CARE Traditional “ or „ “ supplement and provide information about procedural arrangements for Knowledge (TK) Labels Biocultural (BC) Labels Creative Commons Licenses accessing this material and/or about uses that have been deemed generally acceptable. Labels are applied by cultural and knowledge institutions in partnership with communities (see expression in LIDO). Lists Rechteangaben in der Deutschen Digitalen Bibliothek [eng.: Rights statements in the German Digital Library] Rights statements of rightsstatements.org Creative Commons licenses list Examples URI Vorzugsbezeichnung https://creativecommons.org/publicdomain/mark/1.0/ Public Domain Mark 1.0 Universal https://creativecommons.org/publicdomain/zero/1.0/ CC0 1.0 Universal http://rightsstatements.org/vocab/InC/1.0/ In Copyright Expression in LIDO v1.0 <lido:resourceWrap> <lido:resourceSet> <lido:rightsResource> <lido:rightsType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099" >https://creativecommons.org/publicdomain/mark/1.0/</lido:conceptID> <lido:term xml:lang="de">Public Domain Mark 1.0 Universell</lido:term> <lido:term xml:lang="en">Public Domain Mark 1.0 Universal</lido:term> </lido:rightsType> </lido:rightsResource> </lido:resourceSet> </lido:resourceWrap> :CARE <lido:resourceWrap> <lido:resourceSet> <lido:rightsResource> <lido:rightsType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099" lido:source="Local Contexts">https://localcontexts.org/label/tk-multiple-communities/</lido:conceptID> <lido:term>TK Multiple Communities (TK MC)</lido:term> </lido:rightsType> <lido:creditLine xml:lang="en"> Responsibility and ownership over this material is spread across several distinct communities. Use will be dependent upon discussion and negotiation with the multiple communities named herein [name N.N. and community name N.N.]. Decisions about use will need to be decided collectively. As an external user of this material you are asked to recognize and respect cultural protocols in relation to the use of this material and clear your intended use with the relevant communities. </lido:creditLine> </lido:rightsResource> </lido:resourceSet> </lido:resourceWrap> Expression in LIDO v1.1 <lido:resourceWrap> <lido:resourceSet> <lido:rightsResource> <lido:rightsType> <skos:Concept rdf:about="https://creativecommons.org/publicdomain/mark /1.0/"> <skos:prefLabel xml:lang="de">Public Domain Mark 1.0 Universell</skos:prefLabel> <skos:prefLabel xml:lang="en">Public Domain Mark 1.0 Universal</skos:prefLabel> </skos:Concept> </lido:rightsType> </lido:rightsResource> </lido:resourceSet> </lido:resourceWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requirements for data provision Rechtsstatus für das Digitale Objekt [Rights status of digital object] URI No Mandatory A licence or rights statement must be selected from the Rechteangaben in der Deutschen .Digitalen Bibliothek German Digital Library LIDO application profile (DDB-LIDO) <rightsResource> / <rightsType>/ <conceptID> URI No Mandatory CCC-LIDO Application profile <rightsResource> / <rightsType>/ <conceptID> URI No Mandatory DFG Basic Data Record Digital Copy Terms of Use URI Not specified Mandatory DFG Practical Guidelines on Digitisation: LIDO core metadata <resourceSet> / <rightsResource> Text (controlled vocabulary) and /or URI Yes Mandatory if available Europeana Data Model (EDM) <edm:rights> URI No Mandatory It is mandatory for the element to <edm:rights> contain a value from https://pro.europeana.eu ./page/available-rights-statements EODEM application profile (No match) Not applicable Not applicable Not applicable Categories for the Description of Works of Art (2024) 26.2.12 Image Copyright /Restrictions Text Not specified Not mandatory Rights to the cultural heritage object: 22.1 Copyright Statement CDWA Lite (2006) 22.1.5 Rights for Resource Text Yes Not mandatory Rights to the cultural heritage object: 20th Rights for Work Spectrum 5.1 Right reference number Right type Text (controlled vocabulary) Yes Not specified The obligation level is determined by the institution. digiCULT Lizenztyp [eng.: License type] Text (controlled vocabulary) and URI No Recommend ed museum-digital Rechtsstatus der Abbildung [eng.: Rights status of image] URI No Mandatory ID data element mds0015 Rights holder of media file (conditionally mandatory) Definition Holder of usage rights of the digital representation Other possible database element names Rights holder of media file Rights holder of the digital copy Rights holder of the image Text/URI Text and/or URI Repeatable Yes Obligation level Mandatory if the media file is not in the public domain Recording notes This data element is used to specify the author or holder of the usage rights of the media file. If both of these are available, they must be entered in separate elements. This data element is mandatory for media files that are not in the public domain. If the media file is in the public domain, the author may be named, but not the rights holder. If necessary, e. g. the photographer or those involved in digitization may also be provided in a separate data element (in LIDO: ). If the author or photographer is not known, this can be indicated (e.g., by stating "not documented").<lido:resourceSource> : In the case of collection items from colonial contexts, the primary cultural sovereignty lies with the communities of origin. Please note the CARE information on the (see LIDO expression). Usage rights of the media file Terminology recommendations and lists International Standard Identifier for Libraries and Related Organisations (ISIL) Integrated Authority File (GND, German National Library). The following search interfaces provide a convenient way to search the GND: https://explore.gnd. network/ (GND-Explorer), https://lobid.org/gnd (lobid-gnd), https://swb.bsz-bw.de/DB=2.104/ (OGND) Wikidata Examples Contents Definition Other possible database element names Text/URI Repeatable Obligation level Recording notes Terminology recommendations and lists Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element <lido:recordWrap> <lido:recordID lido:type="http://terminology.lido-schema.org/lido00100">61779</lido:recordID> </lido:recordWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requirements for data provision Identifikator für den Datensatz Text No Mandatory German Digital Library LIDO application profile (DDB-LIDO) <lidoRecID> <recordID> Text No Mandatory CCC-LIDO Application profile <lidoRecID> <recordID> Text No Mandatory DFG Basic Data Record Metadata Record Identifier (ID) URI Not specified Mandatory The identifier is required in the form of a LOD URI. Example: https://hdl.handle.net/21.11107/2a42a7c0-075c41b4-b838-6b12f7a06685 DFG Practical Guidelines on Digitisation: LIDO core metadata Identifiers for LIDO dataset and object <lidoRecID> and <recordID> Text Yes Mandatory Europeana Data Model (EDM) <ore:Aggregation> / @rdf:about <edm: aggregatedCHO> Text or URI No Mandatory Either a LOD URI or an internal identifier is expected. EODEM application profile LIDO Record ID <lidoRecID> und <recordID> Text No Mandatory Categories for the Description of Works of Art (2024) 25.7. Object/Work Record ID Text (kontrollierte s Format) No Not mandatory CDWA Lite (2006) 21.1 Record ID Text Yes Mandatory Spectrum 5.1 (No match) Not applicable Not applicable Not applicable digiCULT ID Datensatz [eng.: ID of record] Text No Mandatory museum-digital record-ID Text No Mandatory ID data element mds0018 Record language (mandatory) Definition Indication of the language of the metadata record Other possible database element names Language labelling Language attributes Language of the entry Internal language abbreviation Text/URI Text (controlled format; two-letter language codes preferred)ISO-639-1 Repeatable No Obligation level Mandatory Notes This data element indicates the language in which the record is available. It is required for compatibility of the Minimum Record Recommendation with the LIDO harvesting format. If certain free-text structured information, such as the or an , is also available in other languages, this is indicated Object title or name Object description separately for the corresponding individual data elements. The language labelling of individual data elements will usually have priority over the general language labelling of the data record in the processing of individual elements in portals. In addition to the language of the dataset and the language labelling of individual data field values, the language of the cultural heritage object can be specified. This is mandatory when delivering data to Europeana for cultural heritage objects with the media type "Text", and it is is implemented in the LIDO element with the type attribute='language' for data deliveries to via the . In Europeana EDM, <lido:classification> Europeana German Digital Library the language of the cultural heritage object is indicated in the EDM element .<dc:language> In LIDO, the language is not indicated by an element, but by the xml:lang attribute. Two-character language codes should be used for language labelling, if available for the language in question. Alternatively, three-character language codes may be used. This follows the recommendations of and W3 Europeana . Lists ISO-639-1 (two-letter language codes) preferred. As an alternative, / (three-letter language codes) can also be used.ISO 639-2 ISO 639-3 Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Lists Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element Examples de en fr fa nr mas Expression in LIDO (v1.0 and v1.1) <lido:descriptiveMetadata xml:lang="de"> <lido:administrativeMetadata xml:lang="de"> <lido:objectIdentificationWrap> <lido:titleWrap> <lido:titleSet> <lido:appellationValue xml:lang="de">Bildnis der Schwester Agathe</lido: appellationValue> <lido:appellationValue xml:lang="en">Portrait of the Artist’s Sister Agathe</lido:appellationValue> <lido:appellationValue xml:lang="fr">Portrait de sa soeur</lido: appellationValue> </lido:titleSet> </lido:titleWrap> </lido:objectIdentificationWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requirements fo r data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <descriptiveMetadata xml: lang> and <administrativeM etadata xml:lang> Not applicable : attribute No Mandatory Language labelling is mandatory in LIDO at record level. Therefore, it is also mandatory in the DDB-LIDO application profile. DFG Basic Data Record (No match) Not applicable Not applicable Not applicable DFG Practical Guidelines on Digitisation: LIDO core metadata <descriptiveMetadata xml: lang> and <administrativeMetadata xml:lang> Not applicable : attribute No Mandatory (s ee comment) Language labelling is mandatory in LIDO at record level. Therefore, it is also mandatory in the LIDO core metadata of the .DFG Practical Guidelines on Digitisation Europeana Data Model (EDM) <edm:language> Text (controlle d vocabular y) No Mandatory (s ee comment) The element is completed by the Europeana Data Ingestion Team at the time of import, based on the language of the data partner. In EDM, it is also strongly recommended to indicate the language of each element. Like LIDO, EDM provides the language attribute xml:lang using the standard for ISO-639-2 this purpose. In EDM it is also mandatory to label the language of the cultural heritage object for text objects (letters, postcards, brochures, etc.). This is done in the <dc:language> element. EODEM application profile Record Language /lido:descriptiveMetadata /@xml:lang /lido:administrativeMetadata /@xml:lang Text (controlle d vocabular y) No Mandatory Spectrum 5.1 (No match) Not applicable Not applicable Not applicable Spectrum provides the following object-related language information: , , Object name/title language Content – language In , .scription language Text language digiCULT /lido:descriptiveMetadata /@xml:lang /lido:administrativeMetadata /@xml:lang Not applicable : attribute No Mandatory museum-digital Language Text (controlle d vocabular y) No Mandatory The language for content and navigation is selected automatically, but can also be controlled using language selectors. ID data element mds0019 Record type (mandatory) Definition Type of data record regarding whether it describes a single object or a group of objects Other possible database element names Data record type Single object/object group Text/URI Text (controlled vocabulary) and URI Repeatable No Obligation level Mandatory Notes This data element indicates whether the record is for a single object or a group of objects. It is required to ensure compatibility of the Minimum Record Recommendation with the LIDO harvesting format. For single objects, the element value should be (= Item-http://terminology.lido-schema.org/lido00141 level record). Examples URI Preferred term http://terminology.lido-schema.org/lido00141 Item-level record http://terminology.lido-schema.org/lido00453 Group-level record Expression in LIDO v1.0 Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element <lido:recordWrap> <lido:recordID lido:type="http://terminology.lido-schema.org/lido00100">00039758</lido:recordID> <lido:recordType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">http://terminology.lido-schema. org/lido00141</lido:conceptID> <lido:term xml:lang="de">Einzelobjekt (Katalogisierungsebene)</lido:term> <lido:term xml:lang="en">Item-level record</lido:term> </lido:recordType> </lido:recordWrap> Expression in LIDO v1.1 <lido:recordWrap> <lido:recordID lido:type="http://terminology.lido-schema.org/lido00100">00039758</lido:recordID> <lido:recordType> <skos:Concept rdf:about="http://terminology.lido-schema.org/lido00141"> <skos:prefLabel xml:lang="de">Einzelobjekt (Katalogisierungsebene)</skos:prefLabel> <skos:prefLabel xml:lang="en">Item-level record</skos:prefLabel> </skos:Concept> </lido:recordType> </lido:recordWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requirements for data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <recordType> / <conceptID> URI No Mandatory CCC-LIDO Application profile <recordType> / <conceptID> URI No Mandatory DFG Basic Data Record (No match) Not applicable Not applicable Not applicable The assumes that only "individual DFG Basic Data Record objects" are recorded. The record type is therefore not listed as a separate data element. DFG Practical Guidelines on Digitisation: LIDO core metadata Dataset: <recordType> Text (controlled vocabulary) and URI No Mandatory Europeana Data Model (EDM) (No match) Not applicable Not applicable Not applicable EODEM application profile LIDO Record Type Identifier und LIDO Record Type Keyword /lido:recordWrap/ lido:recordType/lido: conceptID und /lido:term Text (controlled vocabulary) and URI No Mandatory Categories for the Description of Works of Art (2024) 1.1. Catalog Level Text (controlled vocabulary) Not specified Recommend ed CORE element CDWA Lite (2006) 21.2 Record Type Text (controlled vocabulary) No Mandatory Spectrum 5.1 (No match) Not applicable Not applicable Not applicable The (numerical value) can be used to Number of objects generate information about the record type. The obligation the level of Number of objects is determined by the institution. digiCULT Text (controlled vocabulary) and URI No Mandatory museum-digital single object / object group Text and URI No Mandatory ID data element mds0020 Repository of object (mandatory) Definition Name of the institution holding the cultural heritage object Other possible database element names Institution Museum Collection Museum location Name of the museum Assigned museum Text/URI Text (controlled vocabulary) and URI Repeatable Yes Obligation level Mandatory Notes A unique identifier for the institution is required. The preferred identifier is the International Standard Identifier for Libraries and Related Organisations (ISIL) . This data element refers to the institution holding the object. In addition, a free text entry of the institution name is helpful for display in portals. Terminology recommendations and lists International Standard Identifier for Libraries and Related Organisations (ISIL) Integrated Authority File (GND, German National Library): The following search interfaces provide a convenient way to search the GND: https://explore.gnd. network/ (GND-Explorer), https://lobid.org/gnd (lobid-gnd), https://swb.bsz-bw.de/DB=2.104/ (OGND) Wikidata Examples Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Terminology recommendations and lists Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element URI Preferred name https://ld.zdb-services.de/resource/organisations/DE-MUS-016119 Berlinische Galerie - Landesmuseum für Moderne Kunst, Fotografie und Architektur https://ld.zdb-services.de/resource/organisations/DE-MUS-859718 Deutsches Stuhlbaumuseum Rabenau / Sachsen e.V. https://ld.zdb-services.de/resource/organisations/DE-MUS-403018 Industriemuseum Elmshorn https://d-nb.info/gnd/2134213-1 Hochschule der Künste Berlin. Archiv https://d-nb.info/gnd/1043476709 Kulturstiftung des Hauses Hessen Expression in LIDO (v1.0 and v1.1) <lido:repositoryWrap> <lido:repositorySet lido:type="http://terminology.lido-schema.org/lido00475"> <lido:repositoryName> <lido:legalBodyID lido:type="http://terminology.lido-schema.org/lido00099">https://ld. zdb-services.de/resource/organisations/DE-MUS-048017</lido:legalBodyID> <lido:legalBodyName> <lido:appellationValue xml:lang="de">Städel Museum</lido:appellationValue> <lido:appellationValue xml:lang="en">Städel Museum</lido:appellationValue> </lido:legalBodyName> </lido:repositoryName> </lido:repositorySet> </lido:repositoryWrap> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requi rements for data provision (No match) Not applicable Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <repositorySet> / <repositoryName> / <legalBodyName> Text No Conditionally mandatory Mandatory if is available<namePlaceSet> CCC-LIDO Application profile Current location <repositorySet> / <repositoryName> / <legalBodyName> Text No Conditionally mandatory Mandatory if a is available. If the <namePlaceSet> value is missing in the data, the name of the location is added via the registration. The value appears in the ‘Current location’ search filter. DFG Basic Data Record Source Object Institution Text and/or URI Not specified Mandatory In addition to our recommendation, the DFG Basic recommends to indicate the collection Data Record to which the object is assigned. DFG Practical Guidelines on Digitisation: LIDO core metadata Repository/location: <repositorySet> / <repositoryName> / <legalBodyName> Text No Mandatory if available Europeana Data Model (EDM) (No match) Not applicable Not applicable Not applicable EODEM application profile Lender Identifier and Lender Name (repository) /lido:repositoryWrap/lido:repositorySet/ lido:repositoryName/lido:legalBodyID und /lido:legalBodyName/lido: appellationValue Text and URI No Mandatory Categories for the Description of Works of Art (2024) 21.2. Repository/Geographic Location Text (controlled vocabulary) Not specified Recommend ed CORE-Element CDWA Lite (2006) 14.1.1 Location/Repository Name Text (controlled vocabulary) No Mandatory If several facilities are specified, 14.1 Location /Repository Set is repeated. Spectrum 5.1 Organisation’s main body (if applicable also ) with Organisation’s sub-body Org anisation’s reference number Text (controlled vocabulary) and URI No Not specified The obligation level is determined by the institution. digiCULT Museum Text (controlled vocabulary) and URI No Mandatory In , the ISIL is used to automatically assign digiCULT the custodian institution. museum-digital Name of museum (with address, coordinates and ideally ISIL) Text (controlled vocabulary) and URI No Mandatory If the holding institution is not the same as the institution that created the record, in museum-digital the 'Whereabouts' tab can also be used to indicate the location of the object. ID data element mds0021 Usage rights of metadata record (mandatory) Definition Indication of copyright status and usage rights of the metadata record Other possible database element names Legal status metadata Terms of use metadata set Metadata licence Text/URI URI + optionally text (controlled vocabulary) Repeatable No Obligation level Mandatory Notes This data element specifies a valid rights notice or licence for the metadata record. This indicates the extent to which the object information may be used. If you are planning to deliver data to the German Digital Library, you must select a licence or rights statement from Rechteangaben in der Deutschen [eng.: Rights statements in the German Digital Library].Digitalen Bibliothek If the object description text is subject to intellectual property rights, the corresponding legal status should be indicated in a separate data field (in LIDO: <lid , from LIDO v.1.1) (see also ). o:objectDescriptionRights> Object description Lists Rechteangaben in der Deutschen Digitalen Bibliothek [eng.: Rights statements in the German Digital Library] Rightsstatements.org Creative Commons Licenses Examples URI Preferred term Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Lists Examples Expression in LIDO v1.0 Expression in LIDO v1.1 Comparison with relevant standards and database models ID data element https://creativecommons.org/publicdomain/zero/1.0/ CC0 1.0 Universal https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA 4.0 - Attribution-Noncommercial-Sharealike 4.0 International Expression in LIDO v1.0 <lido:recordRights> <lido:rightsType> <lido:conceptID lido:type="http://terminology.lido-schema.org/lido00099">https://creativecommons.org /publicdomain/zero/1.0/</lido:conceptID> <lido:term xml:lang="de">CC0 1.0 Universell</lido:term> <lido:term xml:lang="en">CC0 1.0 Universal</lido:term> </lido:rightsType> </lido:recordRights> Expression in LIDO v1.1 <!-- Without naming of rights holder --> <lido:recordRights> <lido:rightsType> <skos:Concept rdf:about="https://creativecommons.org/publicdomain/zero/1.0/"> <skos:prefLabel xml:lang="de">CC0 1.0 Universell</skos:prefLabel> <skos:prefLabel xml:lang="en">CC0 1.0 Universal</skos:prefLabel> </skos:Concept> </lido:rightsType> </lido:recordRights> <!-- With naming rights holder --> <lido:recordRights> <lido:rightsType> <skos:Concept rdf:about="https://creativecommons.org/licenses/by-nc-sa/4.0/"> <skos:prefLabel xml:lang="de">CC BY-NC-SA 4.0 - Namensnennung-Nicht kommerziell 4.0 International</skos:prefLabel> <skos:prefLabel xml:lang="en">CC BY-NC-SA 4.0 - Attribution-NonCommercial 4.0 International</skos:prefLabel> </skos:Concept> </lido:rightsType> <lido:rightsHolder> <lido:legalBodyID lido:type="http://terminology.lido-schema.org/lido00099" lido:source="ISIL (ISO 15511)">https://ld.zdb-services.de/resource/organisations/DE-MUS-031316</lido:legalBodyID> <lido:legalBodyName> <lido:appellationValue xml:lang="de">Schlesisches Museum zu Görlitz</lido: appellationValue> <lido:appellationValue xml:lang="en">Silesian Museum in Görlitz</lido:appellationValue> </lido:legalBodyName> </lido:rightsHolder> </lido:recordRights> Comparison with relevant standards and database models Standard Element name Text/URI Repeatable Obligation level Comment German Digital Library: Metadata requirements for data provision Rechtsstatus der Metadaten [eng.: Rights status of metadata] URI No Mandatory When contributing data to the , it is German Digital Library expected that the so-called core metadata (object information about the object) is not protected by copyright (CC0 1.0 Universal Public Domain Dedication). Object description texts with a different legal status will be indicated in the <objectDescriptionRights> element in the DDB . LIDO application profile German Digital Library LIDO application profile (DDB-LIDO) <recordRights> / <rightsType> / <conceptID> URI No Mandatory CCC-LIDO Application profile Legal status metadata <recordRights> / <rightsType> / <conceptID> URI No Mandatory DFG Basic Data Record Metadata Record Terms of Use URI Not specified Mandatory DFG Practical Guidelines on Digitisation: LIDO core metadata Dataset: <recordRights> Text and/or URI Yes Mandatory if available Europeana Data Model (EDM) (No match) Not applicable Not applicable Not mandatory For datasets contributed to Europeana, the legal status of the metadata is expected to be in the public domain (Public Domain or ) Mark CC0 1.0 Universal EODEM application profile (No match) Not applicable Not applicable Not mandatory Categories for the Description of Works of Art (2024) (No match) Not applicable Not applicable Not applicable CDWA Lite (2006) (No match) Not applicable Not applicable Not applicable Spectrum 5.1 Rights out reference number Rights out type Text (controlled vocabulary) and URI No Not specified The obligation level is determined by the institution. digiCULT Rechtsstatus der Metadaten [eng.: Rights status of metadata] Text und URI No Mandatory The licence is preset by default for every museum and is CC0 1.0 in .Universal digiCULT museum-digital Metadata rights (status) Text (controlled vocabulary) and URI No Mandatory The licence is preset by default for every museum and is CC BYin , if no other license is selected.NC-SA museum-digital ID data element mds0024 Link to published metadata record (recommended) Definition Persistent link to a presentation of the object which is publicly available on the web Other possible database element names Object in context Permalink object Source link Text/URI URI Repeatable Yes Obligation level Recommended (Europeana: Mandatory) Notes In order to achieve sustainability according to the FAIR principles, the link must be persistent and lead to a publicly accessible object page on the web. Portals can use this link to allow their users to view the object/work in the collection's web database presentation. Examples https://sammlung-digital.lindenmuseum.de/de/objekt/kamm_6664 https://ikmk.smb.museum/object?id=18237616 Expression in LIDO (v1.0 and v1.1) <lido:recordWrap> <lido:recordInfoSet> <lido:recordInfoLink xml:lang="de">https://sammlung-digital.lindenmuseum.de/de/objekt/kamm_6664</lido: recordInfoLink> </lido:recordInfoSet> </lido:recordWrap> Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requirements for data provision Objekt im Kontext [eng.: Object in context] URI No Conditionally mandatory (see comment) For data contributions to the German Digital Library, a direct and persistent link to an online presentation of the object at the data provider is mandatory if there is no link to the or to the media file object in .the media viewer German Digital Library LIDO application profile (DDB-LIDO) <recordInfoSet> / <recordInfoLink> URI No Conditionally mandatory (see comment) Mandatory if <resourceSet> / <resourceRepresentation> / <linkResource> is not available In contrast to the Minimum Record Recommendation, this element may not be repeated in the or in the CCC-LIDO DDB-LIDO application profile application profile. CCC-LIDO Application profile Show original at data partner <recordInfoSet> / <recordInfoLink> URI No Not mandatory DFG Basic Data Record Source object: Additional information or context information Text and/or URI Yes Recommend ed The data element Source object: Additional information or context information in the may correspond to the link to DFG Basic Data Record the published metadata record, but other additional information may also be provided. DFG Practical Guidelines on Digitisation: LIDO core metadata Dataset: <recordInfoSet> / <recordInfoLink> URI Yes Mandatory if available Europeana Data Model (EDM) <ore:Aggregation> / < edm:isShownAt> URI No Mandatory EODEM application profile (No match) Not applica ble Not applicable Not applicable Categories for the Description of Works of Art (2024) (No match) Not applica ble Not applicable Not applicable CDWAlite (2006) 21.4.2 Record Info Link Text Yes Not mandatory Spectrum 5.1 (No match) Not applica ble Not applicable Not applicable digiCULT <recordInfoSet> / <recordInfoLink> URI No Not mandatory museum-digital Web link URI No Not applicable ID data element mds0025 Record date (recommended) Definition Export date of the record Other possible database element names Timestamp Status of the information Export date Text/URI Text (date format required)ISO 8601 Repeatable No Obligation level Recommended Notes Dating of the data record in accordance with contributes to transparency and allows the timeliness of the information provided to be assessed. ISO 8601 The export creation date should be provided. A modification date may be provided in a separate element, but must be clearly distinguishable from the export creation date. Examples 2023-02-25 2015-09-01T17:21:05 Expression in LIDO (v1.0 and v1.1) Note on the export creation date: The type attribute of <lido:recordInfoSet> holds the value " " (LIDO record)http://terminology.lido-schema.org/lido00470 and the type attribute of <lido:recordMetadataDate> holds the value " " (created)http://terminology.lido-schema.org/lido00472 Contents Definition Other possible database element names Text/URI Repeatable Obligation level Notes Examples Expression in LIDO (v1.0 and v1.1) Comparison with relevant standards and database models ID data element <lido:recordWrap> <lido:recordInfoSet lido:type="http://terminology.lido-schema.org/lido00470"> <lido:recordMetadataDate lido:type="http://terminology.lido-schema.org/lido00472">2015-09-01T17: 21:05</lido:recordMetadataDate> </lido:recordInfoSet> </lido:recordWrap> Comparison with relevant standards and database models Standard Element name Text /URI Repeatable Obligation level Comment German Digital Library: Metadata requirements fo r data provision (No match) Not applica ble Not applicable Not applicable German Digital Library LIDO application profile (DDB-LIDO) <recordInfoSet > / <recordMetada taDate> Text (controll ed format) No Recommend ed The type attribute of <recordInfoSet> holds the value "http://terminology.lido- " (LIDO record) and the type attribute schema.org/lido00470 of <recordMetadataDate> holds the value "http://terminology.lido-schema.org " (created)./lido00472 CCC-LIDO Application profile (No match) Not applica ble Not applicable Not applicable DFG Basic Data Record Metadata Record Date Text (controll ed format) No Mandatory DFG Practical Guidelines on Digitisation : LIDO core metadata (No match) Not applica ble Not applicable Not applicable Europeana Data Model (EDM) (No match) Not applica ble Not applicable Not applicable EODEM application profile Export Date /Timestamp Text (controll ed format) No Mandatory Categories for the Description of Works of Art (2024) (No match) Not applica ble Not applicable Not applicable An export date is not provided in the , but a date for data record CDWA creation is: 25.5. Cataloging Date CDWA Lite (2006) (No match) Not applica ble Not applicable Not applicable An export date is not provided in , but a date for record creation or CDWA Lite modification is: 21.4.5 Record Metadata Date Spectrum 5.1 Recording date Text (date format) No Recommend ed Core element. The creation and each modifikation of the data record is documented in the change history. The obligation level is determined by the institution. digiCULT (No match) Text (controll ed format) Yes Mandatory Various timestamps are generated automatically in , including digiCULT Metadata-Creation, Metadata-Modification, LIDO-Record-Modification. museum-digital Status of information Text (controll ed format) Yes Mandatory The record is automatically dated when exported. Different archive versions can be created and retrieved. ID data element mds0026 FAQs (English) What is the Minimum Record Recommendation for Museums and Collections? The Minimum Record Recommendation specifies the most important data elements for the online publication of object information from museums and collections and provides information on how these elements should be filled in. The "minimum record" represents the smallest possible intersection of important data elements across most disciplines and museum types. In-depth cataloguing can build on this if required. The Recommendation ensures a minimum level of data quality and added value for users of the object information through compatibility with relevant standards and a focus on controlled vocabularies. Who is the Minimum Record Recommendation for Museums and Collections intended for? The Minimum Record Recommendation is aimed directly at museum staff, as well as museum consultants and those involved in education and training, who are active in communicating standards for online publication of object information. It is also explicitly aimed at database software providers. By incorporating the recommendation into their software products and services, they can ensure that the online publication of object data is technically supported in accordance with standards. Who develops the Minimum Record Recommendation? The Recommendation is being developed by the Minimum Record Working Group. It was initiated in 2022 by the Museum and Media Desks of the German Digital Library (DDB), the Working Group on Digitisation of the Konferenz der Museumsberatungsstellen in den Ländern (KMBL) and digiS Berlin. Members of the working group include representatives from the Institut für Museumsforschung - Staatliche Museen zu Berlin - Stiftung Preußischer Kulturbesitz, the Fachgruppe Dokumentation of the German Museum Association (DMB), the Coordination Centre for Scientific University Collections in Germany, digiCULT-Verbund eG, museum-digital Deutschland e. V., NFDI4Culture, NFDI4Objects, NFDI4Memory, Museum für Naturkunde Berlin and Übersee-Museum Bremen. Both during the development of the beta version (2023) and the finalisation of the first full version of the Minimum Record Recommendation, which was published in May 2024, representatives from various stakeholder groups, including museum staff, persons working in consultancy and education, software providers and representatives from various cultural heritage portals, were involved and asked for feedback. Inhalt What is the Minimum Record Recommendation for Museums and Collections? Who is the Minimum Record Recommendation for Museums and Collections intended for? Who develops the Minimum Record Recommendation? What are the objectives of the Recommendation? What is the vision behind it? What are the application scenarios for the Minimum Record Recommendation? What is new in version 1.0 compared to the beta version? Why is the Minimum Record Recommendation LIDO-compliant? Why has the Minimum Record Recommendation not been mapped to EAD or MARC or METS/MODS? Why is the Minimum Record Recommendation a LIDO application profile and what does it mean? What is the purpose of the tables at the end of the data element pages? What is the purpose of the LIDO snippets on the data element pages ("Expression in LIDO")? Why are the LIDO snippets shown in both LIDO v1.0 and LIDO v1.1? What does "Other possible database element names" mean? What is Linked Open Data? What is the role of controlled vocabularies here? What principles are the vocabulary recommendations on the element pages based on? How do the FAIR Principles relate to the Minimum Record Recommendation? What role do the CARE Principles play in the Minimum Record Recommendation? What role does digital accessibility play in the Minimum Record Recommendation? How is the Minimum Record Recommendation relevant to AI? Does the Minimum Record Recommendation focus primarily on the cataloguing or publication of object information from museums and collections? Why is the Data element set divided into "Data elements (cataloguing)" and "Data elements (export)"? What about data elements that are important for digital collection management - why are they not included in the Minimum Record Recommendation? Why so many data elements - shouldn't there be fewer for a Minimum Record? Why are the requirements of the German Digital Library (DDB) and Europeana portals mentioned several times? What if I do not plan to submit data to the DDB and Europeana? Is the Minimum Record Recommendation still relevant for me/my institution? Why is an event mandatory in the object history? What if my database is not event-based? My object information is only available in German. Why do I need to indicate the language of the record? The objects I want to publish are to be catalogued within a specific discipline. Is the Minimum Record Recommendation still relevant to me? Why does the Minimum Record Recommendation suggest that my museum's object information should appeal to a wide audience? What does it mean when a software provider supports the Minimum Record Recommendation? Are there different levels? When I enter data into my museum database, will I receive information on which data elements are mandatory/recommended and how they should be filled in? Who can I contact if I have questions about using the Minimum Record Recommendation? What are the objectives of the Recommendation? The Minimum Record Recommendation is intended to pave the way for smaller and larger museums and collections to publish their data online and to communicate relevant standards in an easy-to-understand, low-threshold approach. The aim is to raise awareness of data quality in cultural institutions and support them with online publication. The recommendation is intended for practical application in everyday museum work. The Minimum Record Recommendation is intended to support museums in setting the course for more consistent and higher-quality data right from the start. It assists them in gradually integrating controlled vocabularies into their documentation and publication practice, thus preparing their valuable datasets for up-to-date Linked Open Data scenarios. What is the vision behind it? The vision of the Minimum Record Recommendation for Museums and Collections is that data from museums can be linked beyond individual institutions and can be found and reused online by the widest possible audience, within the limits of the law. In this way, more people should become aware of and benefit from the work of museums in their leisure, school, work and research. What are the application scenarios for the Minimum Record Recommendation? Application scenarios for the Minimum Record Recommendation include the online publication of object information from museums and collections in online collections of individual institutions, but also the provision via cultural portals such as the German Digital Library and Europeana, as well as via data interfaces. The Recommendation is also intended to facilitate future integration into the and the Culture Data Space Common European Data Space for . The Minimum Record Recommendation can support the preparation of object information for these scenarios.Cultural Heritage What is new in version 1.0 compared to the beta version? New features since the beta version include notes on digital accessibility, consideration of the needs of the natural history and numismatic communities, and advice on compliance with the CARE Principles. In addition, many examples have been added and, where appropriate, persistent URIs have been included. In addition to the snippets, snippets are now provided to explain the features of the data elements in the LIDO data LIDO v1.0 LIDO v1.1 exchange format. Why is the Minimum Record Recommendation LIDO-compliant? LIDO is a standard of the the International Council of Museums (ICOM CIDOC) for the publication of International Committee on Documentation of information on objects of material culture (see also ). It is mainly developed by the German-speaking LIDO Working Group in the LIDO for cultural objects Documentation Section of the German Museums Association. LIDO is based on the CIDOC CRM ontology and allows objects to be described in a structured way using controlled vocabularies (see also ). Another feature of LIDO is that information about the history of an object is organised LIDO Primer into individual events. As a data exchange format, LIDO is well suited for ensuring the interoperability or connectivity of object information, thus preparing datasets for Linked Open Data. It has been shown that LIDO is not always easy to understand due to its language (XML-based) and structure (high degree of nesting, repeating element sets). In some cases, LIDO - a highly complex and flexible standard - exceeds the specific needs and capacities of museums and collections. The aim of the Minimum Record Recommendation is to take advantage of LIDO's benefits (structuring, controlled vocabulary integration, broad international acceptance) and to focus on the smallest possible intersection of data elements that are important for online publication across most disciplines and museum types. The explanation of the data elements in a generally comprehensible language and the integration of data element names from a large number of databases should make it easier to get started. Why has the Minimum Record Recommendation not been mapped to EAD or MARC or METS /MODS? The Minimum Record Recommendation focuses on the publication of object information from museums and collections. Objects from archives or libraries, even those affiliated with museums, are not included. Especially when publishing object information from museums, there is an increased need for guidance on standardised provision, which the Recommendation seeks to address. Why is the Minimum Record Recommendation a LIDO application profile and what does it mean? Application profiles define which components of LIDO must be included in a data record to meet the requirements of specific use cases (see also LIDO ). LIDO offers a large number of possible elements and attributes. In most use cases, some of these are not required and a selection is made as to training which ones should be used. Application profiles may be stricter than the , but not more relaxed. If an element is mandatory in LIDO, it must also be mandatory in the LIDO specification application profiles. This also applies to the Minimum Record Recommendation. For example, the object title is mandatory in the Minimum Record Recommendation, just as it is in LIDO. In contrast to LIDO, the inventory number of the object is mandatory in the Minimum Record Recommendation because it is listed as an important data element in the relevant guidelines for museum cataloguing. What is the purpose of the tables at the end of the data element pages? The Minimum Record Recommendation is based on a comparison of the relevant standards for digital cataloguing and online publication of objects from museums and collections (including , , The DFG Basic Data Record DFG Practical Guidelines on Digitisation: LIDO core metadata Europeana Data Model). data element catalogues of the two federated databases digiCULT and museum-digital were also included. The resulting concordance can be found on the individual data element pages of the Minimum Record Recommendation. With regard to (digital) cataloguing, the guidelines of the German Museum Association for basic cataloguing were taken into account (Datenfeldkatalog zur [eng.: Data Element Catalogue for Basic Indexing] (1993), [eng.: Guidelines Grundinventarisation Leitfaden für die Dokumentation von Museumsobjekten for the Documentation of Museum Objects] (2011), [eng.: Digital Basic Cataloguing. 10 Principles] (2022). As the Digitale Grunderfassung. 10 Grundsätze data element mentioned therein are not formally specified, these guidelines are not listed in the concordance tables. What is the purpose of the LIDO snippets on the data element pages ("Expression in LIDO")? The LIDO snippets (excerpts from a complete LIDO data record, expressed in so-called code blocks in XML language) show how the respective data element is translated into LIDO. This helps all those - museum staff or external service providers - who export data from the local database. Exporting in LIDO XML format is more suitable than in Excel or CSV format for making data available to portals or via data interfaces. In addition to the LIDO snippets, the page provides a sample data record in Excel, CSV and XML formats that meets the Resources and Links requirements of the Minimum Record. Why are the LIDO snippets shown in both LIDO v1.0 and LIDO v1.1? LIDO was released in in 2010 and in in 2021. LIDO is backwards compatible. This means that records created in v1.0 will always version 1.0 version 1.1 be valid LIDO records. Version 1.1 offers helpful new features compared to version 1.0, e. g. controlled vocabularies can be integrated in a more differentiated way via the SKOS namespace and can be better analysed automatically. In the future, the German Digital Library will also be able to accept LIDO v1.1 data contributions. Since this is not yet the case, and since an important requirement of the Minimum Record Recommendation is that datasets conforming to the Minimum Record meet the requirements of the German Digital Library and Europeana, v1.0 snippets will be offered alongside v1.1 snippets, to support data contributions to the German Digital Library. What does " mean?Other possible database element names" In addition to the data element names used in the Minimum Record Recommendation, other common data element names are listed for each data element to illustrate the applicability of the Recommendation to cataloguing practice across the spectrum of the museum and collections landscape. The Minimum would be grateful for information about other common data element names that have not yet been included. Record Working Group What is Linked Open Data? What is the role of controlled vocabularies here? Linked Open Data (LOD) describes a network of data that originates from different sources - sources can be museum databases, for example - and is linked together. The public provision of data is crucial for linking. The data can be made available through data interfaces (these interfaces can be provided by the institutions themselves; cultural portals also usually offer different interfaces, e.g. OAI interfaces or APIs). The data must be provided in a machineinterpretable format (e.g. XML). In addition, URIs should be used wherever possible to identify terms. For example, in an LOD-compliant dataset, the object type or object designation should be described via a persistent link from a published controlled vocabulary. Suitable controlled vocabularies in this case are the , the , or the [eng.: Object Designation File]. As an Art and Architecture Thesaurus Integrated Authority File Wikidata Objektbezeichnungsdatei XML-based data exchange format, LIDO is ideal for publishing data for Linked Open Data. What principles are the vocabulary recommendations on the element pages based on? The Minimum Record Recommendation almost exclusively recommends controlled vocabularies that are suitable for various cultural heritage objects across disciplines and museum types as far as possible. The recommended vocabularies themselves comply with the guidelines of the FAIR principles: They have persistent identifiers in the form of URIs, are well documented and editorially maintained. They also contain clearly defined terms. The terms of use are clearly regulated by law. The vocabulary is equipped with a license that is as open as possible for machine evaluation. Some technical requirements must also be met: The vocabulary is available in certain machine-evaluable formats and is addressable via interfaces that are openly accessible on the Internet. There is also a whole range of terminologies that provide good content coverage of the documented objects in a subjectspecific context. Even if such vocabularies are not explicitly mentioned in the Minimum Record Recommendation, they can be used if the FAIR criteria mentioned (largely) apply to them. How do the FAIR Principles relate to the Minimum Record Recommendation? The , published in 2016, promote making research data discoverable, accessible, interoperable and reusable. Object information from FAIR Principles museums can be regarded as research data in that the recording and cataloguing of collection objects should follow scientifically standardised specifications and involves research activity. In addition, cataloguing information from museums provides important sources for research. As research is one of the pillars of museum work according to the ICOM Museum Definition, the FAIR Principles are also highly relevant to the work of museums in the context of digital transformation. The FAIR Principles should not be taken synonymous with the idea of open data. Rather, the FAIR Principles state that data should be made available as openly as possible and as closed as necessary (to meet legal requirements, for example). Nevertheless, the FAIR Principles provide important guidelines for the implementation of Linked Open Data. One aim of the Minimum Record Recommendation is to enable museums and collections to comply with the FAIR Principles in their publication practices and to make their object information available for Linked Open Data. Compatibility with the LIDO data format is an important step in this direction. What role do the CARE Principles play in the Minimum Record Recommendation? Credits and Citation Minimum Record Working Group As part of the Minimum Record Working Group, the following persons have been involved in the development of the current version of the Minimum Record Recommendation: Name Institution 1Ando, Marita Museum für Völkerkunde zu Leipzig 2Bernhard, Anne-Marie Museumsverband Hessen e. V. 3Böhm, Elisabeth Dr. digiCULT-Verbund eG 4Diepenbrock, Nora Museum Desk of the German Digital Library, Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 5Frech, Andreas Universitätsbibliothek der Ludwig-Maximilians-Universität München 6Götsch, Stephanie (former working group coordination) Museum Desk of the German Digital Library, Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 7Gerber, Anja Klassik Stiftung Weimar and NFDI4Objects 8Gnyp, Anna Humboldt-Universität Berlin and SODa 9Greisinger, Sybille Landesstelle für die nichtstaatlichen Museen in Bayern 10 Grotrian, Etta Dr. Übersee-Museum Bremen 11 Hagel, Frank von Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz and Documentation Section of the German Museum Association 12 Kailus, Angela (former working group member) Deutsches Dokumentationszentrum für Kunstgeschichte – Bildarchiv Foto Marburg, Philipps-Universität Marburg and NFDI4Culture 13 Koch, Anne-Katrin Museumsverband Rheinland-Pfalz e. V. 14 Krause, Celia Deutsches Dokumentationszentrum für Kunstgeschichte – Bildarchiv Foto Marburg, Philipps-Universität Marburg and NFDI4Culture 15 Kudlinski, Vera Museumsverband Hessen e. V. 16 Marchini, Chiara (working group coordination) Museum Desk of the German Digital Library, Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 17 Nowicki, Anna-Lena Forschungsund Kompetenzzentrum Digitalisierung Berlin (digiS) 18 Purschwitz, Anne Dr. Martin-Luther-Universität Halle-Wittenberg and NFDI4Memory 19 Quade, Lisa Museum Desk of the German Digital Library (Portal Collections from Colonial Contexts), Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 20 Reichert, Rebekka Humboldt-Universität Berlin und SODa 21 Rohde-Enslin, Stefan Dr. Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 22 Rölle, Sophie Media Desk of the German Digital Library, Sächsische Landesbibliothek - Staatsund Universitätsbibliothek Dresden 23 Schäfer, Domenic Dr. (former working group coordination) formerly Institut für Museumsforschung, now Head Office of the GBV (VZG) 24 Schlösser, Magdalene Institut für Museumsforschung - Staatliche Museen zu Berlin - Preußischer Kulturbesitz 25 Städing, Lukas digiCULT Verbund eG 26 Stricker, Martin Coordination Centre for Scientific University Collections in Germany, Hermann von Helmholtz-Zentrum für Kulturtechnik, Humboldt-Universität zu Berlin 27 Thorn, Caitlin Museum für Naturkunde, Leibniz Institute for Evolution and Biodiversity Science, Berlin 28 Wagner, Sarah Dr. Friedrich-Alexander-Universität Erlangen-Nürnberg and NFDI4Objects 29 Wassermann, Sarah Dr. Museumsverband des Landes Brandenburg e. V. 30 Winkler, Alexander Forschungsund Kompetenzzentrum Digitalisierung Berlin (digiS) Citation note The Minimum Record Recommendation is published under the Licence and is thus released into the public domain, as the CC0 1.0 Universal Minimum Record Working Group has waived all copyright and related rights worldwide to the extent legally possible. The recommendation can be cited as follows: Minimum Record Working Group, Minimum Record Recommendation v1.1 (2025), CC0 1.0 Universal Wiki: www.minimaldatensatz.de PDF: https://doi.org/10.5281/zenodo.12759620 Acknowledgements The Minimum Record Working Group would like to thank the following persons for their feedback, advice and support (as of May 2024): Institution Name 1Arbeitsstelle für Standardisierung, German National Library Barbara Pfeifer 2Arbeitsstelle für Standardisierung, German National Library Chantal Köppl 3Arbeitsstelle für Standardisierung, German National Library Mathias Manecke 4Arbeitsstelle für Standardisierung, German National Library Sarah Hartmann 5Arbeitsstelle für Standardisierung, German National Library Barbara Fischer 6Architekturmuseum, Technische Universität Berlin Dr. Hans-Dieter Nägelke 7Axiell ALM Germany GmbH Dirk Witthaut 8Axiell ALM Germany GmbH Rene van den Heuvel 9Badisches Landesmuseum Mario Lampe 10 CD-Lab Bonn (VINO) Ulrich Gloede 11 Coordination Centre for Scientific University Collections in Germany Sarah Elena Link 12 Corpus Nummorum, Berlin-Brandenburgische Akademie der Wissenschaften Dr. Ulrike Peter 13 Corpus Nummorum, Berlin-Brandenburgische Akademie der Wissenschaften PD Dr. Vladimir Stolba 14 Deutsche Fotothek - Sächsische Landesbibliothek - Staatsund Universitätsbibliothek Dresden Dr. Jens Bove 15 Deutsche Fotothek - Sächsische Landesbibliothek - Staatsund Universitätsbibliothek Dresden Dr. Simone Fleischer 16 Deutsches Dokumentationszentrum für Kunstgeschichte, Bildarchiv Foto-Marburg, Philipps-Universität Marburg Christian Bracht 17 Deutsches Dokumentationszentrum für Kunstgeschichte, Bildarchiv Foto-Marburg, Philipps-Universität Marburg Dr. Gudrun Knaus 18 Deutsches Dokumentationszentrum für Kunstgeschichte, Bildarchiv Foto-Marburg, Philipps-Universität Marburg Klaus Bulle 19 Digitales Kunstund Kulturarchiv Düsseldorf (d:kult) Tamara Tolnai 20 Ethnologisches Museum und Museum für Asiatische Kunst, Staatliche Museen zu Berlin Anna Seidel 21 Europeana Henning Scholz 22 Förderverein des Freilichtmuseums am Kiekeberg e. V. (FirstRumos Museumssoftware) Lars Steinberg 23 Forschungsund Kompetenzzentrum Digitalisierung Berlin (digiS) Marco Klindt 24 Freilichtmuseum Roscheider Hof Helge Klaus Rieder 25 German Digital Library, Head Office Dr. Julia Spohr 26 German Digital Library, Service Desk & Data Management Claudia Effenberger 27 German Digital Library, Service Desk & Data Management Denise Baumgart 28 German Digital Library, Service Desk & Data Management Eleonore Emsbach 29 German Digital Library, Service Desk & Data Management Jennifer Treu 30 Germanisches Nationalmuseum Robert Nasarek 31 Göttingen State and University Library Barbara Fichtl 32 Göttingen State and University Library Timo Schleier 33 Heidelberg University Library, heidICON Nicole Sobriel 34 Herder Institute for Historical Research on East Central Europe Felix Köther 35 Hochschule für Technik und Wirtschaft Berlin Prof. Dr. Dorothee Haffner 36 Humboldt-Universität, Mediathek - Bildsammlungen des Instituts für Kunstund Bildgeschichte Dr. Georg Schelbert 37 Institut für Museumsforschung Kathrin Grotz 38 Institut für Museumsforschung Prof. Dr. Patricia Rahemipour 39 Joanneum Research (Imdas Pro) Silvia Russegger 40 Joanneum Research (Imdas Pro) Werner Preininger 41 Jüdisches Museum Frankfurt Sonja Thäder 42 Landesmuseum Württemberg Hanna Warth-Geraci 43 Landesmuseum Württemberg Noreen Klingspor 44 LEO-BW Jens Lill 45 mindscreen GmbH Annett Farnetani 46 Münzkabinett Berlin Dr. Angela Berthold 47 Museum für Naturkunde, Berlin Mareike Petersen 48 Museum für russlanddeutsche Kulturgeschichte, Detmold Nico Wiethof 49 Museum Wiesbaden PD Dr. Thomas Hörnschemeyer 50 museum-digital Deutschland e. V. Joshua Enslin 51 Museumsverband Hessen Bettina von Andrian (freiberuflich) 52 Museumsverband Hessen Hauer und Krause (freiberuflich) 53 MusIS-Verbund Dr. Werner Schweibenz 54 The National Gallery, London Rupert Shepherd 55 Pausanio GmbH & Co.KG Prof. Dr. Holger Simon 56 Programmfabrik GmbH (EasyDB) Sebastian Klarmann 57 Robotron Datenbank-Software GmbH (robotron*Daphne) Ulrich Servos 58 Saarländischer Museumsverband Sabine Geith 59 Sächsische Landesstelle für Museumswesen Johanna Jürgens 60 Sammlungsdinge Patrick McDonough 61 Solvatec (BeeCollect) 62 Städtische Museen Freiburg Jochen Dietel 63 Stiftung für Kunst, Kultur und Geschichte, Winterthur Sonja Gasser 64 Stiftung Historischer Museen Hamburg Doreen Wand 65 zetcom Informatikdienstleistungs AG (MuseumPlus) Jette Klein-Berning