Mapping LIDO v0.7 to CIDOC-CRM v5.0.1
Maria Koutraki , Martin Doerr
Institute of Computer Science, FORTH-ICS
P.O. Box 1385, GR71110, Heraklion, Crete, Greece
{kutraki, martin}@ics.forth.gr
Working paper, ICS-FORTH, March 2010
The need to describe an extremely heterogeneous environment in the Cultural Heritage area and more specifically in the museum sector, led to the emergence of several metadata schemata. To a certain degree museums expose minimalmetadata in Dublin Core. However,satisfactory museum metadata are very complex, and a general agreement has been made inthe form of the CIDOC CRM (ISO21127:2006), which declares rich common semantics ofmetadata elements in an RDF compatible form, but does not, by itself, prescribe the use ofany fields. CIDOC-CRM is a formal ontology that defines cultural heritage documentation concepts and the relationships between those concepts, and it is intended to facilitate the integration, mediation and interchange of heterogeneous cultural heritage information [
Only recently, most important international stakeholders in the museum sectorhave agreed on an explicit format for harvesting museum data, called LIDO(Lightweight Information Describing Objects). It is CRMcompatible and is already underpinned by the production of large data sets in this format bythe European Project ATHENA[
This document defines a mapping from LIDO v0.7 to CIDOC-CRM v5.0.1. The mapping of the two modelsis defined as a sufficient specification to transform each instance of the source model into an instance of the target model with the same meaning. In this case, we regard LIDO as the source model while CIDOC-CRM is the target model.LIDO contains many elements that are categorized in two basic categories, the Descriptive Metadata and the Administrative Metadata. These elements contain the information about the object which is described. Each of these elements and sub-elements of LIDO, are mapped in one or more triples in CIDOC-CRM. For example the first LIDO element “RecID” is mapped as the triple: “E19 Physical ObjectP70 is documented inE31 Document”. “E19 Physical Object” is a CIDOC-CRM Domain class, “P70 is documented in” is a CIDOC-CRM property and “E31 Document” is a CIDOC-CRMRange class.
Identifier
1)RecID
Category
2)Category
Descriptive Metadata
Object Classification Wrap
3)Object Work Type/term
4)Object Work Type/conceptID
5)Classification/term
6)Classification/conceptID
Object Identification Wrap
7)TitleSet/appelationValue
8)TitleSet/sourceAppellation
9)Inscriptions
10)Repository Name/Legal Body ID
11)Repository Name/ Legal Body Name/Appellation Value
12)Repository Name/ Legal Body Weblink
13)Repository Location / Name Place Set/Appellation Value
14)Repository Location / Name Place Set/sourceAppellation
15)Repository Location / Place ID
16)Repository Location/Part of Place
17)Repository Location/Place Classification/term
18)DisplayState
19)Display Edition
20)SourceDisplayStateEdition
21)Descriptive Note Value
22)Source Descriptive Note
23)Display Object Measurements
24)Measurements Set
25)Extent Measurements
26)Qualifier Measurements
27)Format Measurements
28)Shape Measurements
29)Scale Measurements
Event Wrap
30)Display Event
31)Event Type/term
32)Event Type (condition =” Herstellung” (Production))
33)Event ID
34)Role in Event/term
35)Role in Event/conceptID
36)Event Name/Appellation Value
37)Event Name/sourceAppellation
38)Display Actor in Role
39)Name Actor / Appelation Value
40)Name Actor / sourceAppelation
41)Actor ID
42)Nationality Actor/term
43)Nationality Actor/conceptID
44)Vital Dates Actor
45)Gender Actor
46)Role Actor/term
47)Attribution Qualifier Actor
48)Extent Actor
49)Culture/term
50)Display Date
51)Earliest Date
52)Latest Date
53)Period Name/term
54)Display Place
55)Name Place set / Appellation value
56)Name Place set /sourceAppellation
57)PartOfPlace
58)Place Classification/term
59)Place ID
60)Event Method/term
61)Display Materials Tech
62)Term Materials Tech/term
63)Extent Materials Tech
64)Source Materials
65)Descriptive Note Value
66)Source Descriptive Note
Object Relational Wrap
67)Display Subject
68)Extent Subject
69)Subject Concept/ Concept ID
70)Subject Concept/term
71)Subject Actor/Display Actor
72)Subject Date/Display Date
73)Subject Event/Display Event
74)Subject Place/Display Place
75)Subject Object
76)Display Object
77)Object Web Resource
78)Object ID
79)Object Note
80)Related WorkRel Type
Administrative Metadata
Rights Work Wrap
81)Rights Type
82)Rights Date/ earliest Date
83)Rights Date/ latest Date
84)Rights Date/ Period Name/term
85)Rights Holder/Legal Body ID
86)Rights Holder/Legal Body Name/Appellation Value
87)Rights Holder/Legal Body Web link
88)Credit Line
Record Wrap
89)Record ID
90)Record Type
91)Record Source/Legal Body ID
92)Record Source/Legal Body Name/Appellation Value
93)Record Source/Legal Body Web link
1