crm and skos in the digicult-network - gbv...1. cidoc-crm and museumdat/lido • mission 2010:...
TRANSCRIPT
DAI Workshop Berlin, 23.11.2010 Frank Dührkohp, Axel Vitzthum
CRM and SKOS in the digiCULT-Network
• is an interdisciplinary project for digital collection
and publication of inventories of museums in the
German Federal States of Schleswig-Holstein,
Hamburg and Saarland.
• operates with a combined data management:
- separate recording of data by each museum
- integration of all records in a common data pool
- result: joint access and publication (internet)
• offers all museums controlled vocabularies.
digiCULT works with a hierarchical co-reference
Network for the museums (vocabularies and
persons are reachable over Webservice).
digiCULT
digiCULT.meta
digiCULT.DokBase digiCULT.xTree
digiCULT.xTree:Hierarchical co-referencing:Central web-based tool foradministration of lists and classifications. Alignment of norm data, multilingualism etc. to ensure consistent practice
digiCULT.DokBase:
Local collection
management softwarefor single workstations and networks
digiCULT.meta:
global metadata
container for XML-Data
Technical Configuration: 3 main Modules
WWW
www.bam-portal.de
www.europeana.eu
WebService
museumdat
- museumvok-XML- SKOS RDF
www.museen-nord.de
www.museen-saarland.de
CollectionManagement Software / Excel-files
museumvok-Webservice
participating disciplines / thematic areas inin more then in 70 Museums
Archaeological Museums
Art Museums
Botanical Gardens
Computer Collection
Geological and Mineralogical
Museums
Medical and PharmaceuticalCollection
Museums of Cultural History
Museum of Fire Fighting
Theatre History Collections
Zoological Museum
Common Library Network GBV
• GBV Common Library Network of the German States Bremen,
Hamburg, Mecklenburg-Vorpommern, Niedersachsen, Sachsen-
Anhalt, Schleswig-Holstein, Thüringen and the Foundation of
Prussian Cultural Heritage
• Union Catalogue (GVK) with Online Resources 30 million records with 64 million holdings
– Secondary information databases
– 170 Local Library catalogues (OPACs)
– Different Portal Solutions
• Software PICA (CBS/LBS) of OCLC / Metadata format MAB, MARC
21, PICA+
• strategic goal of the GBV: enrichment and linkage of scientific
information
– support of the information infrastructure for research and
teaching
– not only availability of the literature, also the “digital cultural
heritage”
••VZGVZG
GGööttingenttingen
Outline
1. CIDOC-CRM and museumdat/LIDOcross-domain data modelling of Intranet Hamburg and the future web-based collection tool digiCULT.web
2. xTree + SKOScollaborative work on vocabularies
3. digiCULT Accumulatormetadata enrichment: where museumdat meets SKOS
4. Archaeological items for the worldGBV-digiCULT and Europeana
1. CIDOC-CRM and museumdat/LIDO
• Mission 2010: building Intranet for 4 Museums with 200000 items
cross-domain data modelling of Intranet Hamburg
• with different collections:– Archaeology– Art– Cultural History– Geological– Technical History
• and 3 different Collection Management Systems
More Informations: http://www.mai-tagung.de/Maitagung+2009/mertensmerkelpptmai2009.pdf„Wenn die Scherben online gehen“ by Kathrin Mertens + Michael Merkel (Xanten, Mai 2009):
MuseumPlus
Faust
digiCULT.DokBase
CRM / museumdat-LIDOExample Kragenflasche
Object Work TypeKragenflasche
dating of Production-4000 - -2800
Period NameNeolithic
Find spotCemetery Ohlsdorf(Hamburg)
FinderCemetery staff
CultureFunnelbeaker culture
Kragenflasche in CRM
Source: Jutta Lindenthal
Kragenflasche
E22 Man-Made Object
P1 is identified by E41 Appellation P2 has type
P10 falls within Neolithikum Neolithic@en
P108 was produced by E12 Production
E4 Period
P4 has time-span
P79 beginning is qualified by E62 String -4000
P80 end is qualified byE62 String -2800
E52 Time-Span
P2 has type
P81 ongoing throughout E61 Time Primitive -5500 bis - 2200
P32 used general technique
E55 Type
E55 Type Design orProcedure Type
aufgebaut, gebrannt, geritzt
E55 Type
P45 consists ofE57 Material
P2 has typeTon clay@en
P43 has dimensionE54 Dimension
height (E54), has unit cm (E58), has value 13 (E60)diamenter (E54), has unit cm (E58), has value 9,6 (E60)weight (E54), has unit gr (E58), has value 268 (E60)
P8 witnessedE4 Period
P2 has typeTrichterbecherkultur Funnelbeaker culture@en
P10 falls within Kupfersteinzeit Copper Age@enE4 Period
P2 has typeE55 Type
Friedhofs-verwaltung
E5 EventE40 Legal Body
P11 had participant
P131 ist identified byE82 Actor Appellation
P14.1 in the role ofE55 Type Finder
P12 was present at
P2 has typeFund
P7 took place atE53 Place
P87 is identified by E44 Place Appellation HH-Ohlsdorf
E53 Place
P89 falls withinE53 Place
P87 is identified byE48 Place name Hamburg-Ohlsdorf
P87 is identified by E48 Place Name Friedhof Ohlsdorf Hamburg-Ohlsdorf / Waldfriedhof
Hamburg
Hansestadt Hamburg
SWD
P89 falls withinE53 Place
P87 is identified byE48 Place name
P139 has alternative form
P71 is listed in E32 Authority Document
P87 is identified byE47 Spatial Coordinates 53.550556°, 9.993333°
P2 has type E55 Type Parkfriedhof
P127 has broader termE55 Type Friedhof graveyard
Source: Jutta Lindenthal
Kragenflasche in museumdat/LIDO only events, no identifier
- museumdat/LIDO+CRM: Kragenflasche, Production event- similar structure
E22 Man Made Object
„Kragenflasche“
E12 Production
P108 was produced by
E52 Time Span
P79 beginningis qualified by E62 String
„-4000“
P4 has time-span
E62 String
„-2800“
P2 has type
E4Period
P10 falls within
E55 Type
„Neolithic“
P80 end is qualified by
- museumdat/LIDO+CRM: Kragenflasche, Find event, place- similar structure
E53Place
E48 Place Name
„Friedhof Ohlsdorf“
P87 is identified by
E53Place
E48 Place Name
„Ohlsdorf“
E53Place
E48 Place Name
„Hamburg“
P87 is identified by
P87 is identified by
P89 falls within
P89 falls within
Sketch Structure Intranet Hamburg
Event
Place
date
0..1
Production
Use
Find
Excavation
Modification
Acquisition
Transformation
...
has Type
0..1
Actor
0..n
1..nwork ID
has type
preferred
alternative
0..n
has role
Künstler
Hersteller
Finder
Schiff
Sammler
Mitwirkende
...
Spatial
Coordinates
identifier
identifier
0..1
0..1
identifier
0..1
has type
personalName
corporateName
has Type
Classification
Objektbezeichnung
Taxonomien
Sachgruppe
Mineral
Stil
1..n
identifier
MatTech
0..n
extent
0..1
identifier 0..n
Display
Material
0..1
Measurement
display
1
resources0..n
Titel
1..n
preferred
alternative
has typeDescription
0..n
Description
Object History
...
has type
relatedWorks
0..n
Time-span
periodName
1
has Type
Material
Techniqie
identifier
1
Intranet Hamburg
2. xTree + SKOS
What is SKOS
• Simple Knowledge Organisation Systems (SKOS) is a family of
formal languages designed for representation of thesauri,
classification schemes, taxonomies, subject-heading systems,
folksonomies or any other type of structured controlled vocabulary.
• SKOS is currently developed within the W3C framework.
• some Vocabularies:
– Agrovoc
– AAT (Art & Architecture Thesaurus)
– DDC (Dewey Decimal Classification)
– Eurovoc
– ICONCLASS
– LCSH (Library of Congress Subject Headings)
– RAMEAU (Répertoire d'autorité-matière encyclopédique et alphabétique unifié)
– SWD (Schlagwortnormdatei)
– TGN (Thesaurus of Geographic Names)
– UNESCO Thesaurus
based on Wikipedia@en
more then 40 Vocabularies are used by digiCULT
SWD, ULANdigicult Artists
SWDdigicult Botanists
-Meteoritical systematic
UNESCO International Stratigraphic ChartGeological eras
Strunz ClassificationMineral systematic
-Technique Archeology
-Material Archeology
-Objectworktype Archeology
SWD, TGNPlaces
Züricher SystematikMedicine
SWDStyle
SWDTechnique
SWDMaterial
ICONCLASS, SWD Ikonographie
Schlagwortnormdatei (SWD, by Dt. Nationalbib.) Hessische Systematik
(subject group)
semantic mapping
http://de.wikipedia.org/w/index.php?title=Datei:StoneMoney.JPG&filetimestamp=20061025214904
stone money
Example: SKOS-mapping
Example: SKOS Graph „stone money“
Some often used SKOS elements:• Concept• Lexical properties (prefLabel, altLabel, hiddenLabel)• Semantic relations (broader, narrower, related)• Documentation (notes, including definition, scope note)• Semantic mapping (Cross-references between concepts indifferent concept schemes)
Example: SKOS Graph „stone money“
Motivation xTree
• create collaborative knowledge
• share vocabulary items in XML or RDF between software applications usingWebservice and REST
• Connect content/metadata to concepts/terms (e.g. museumdat to museumvok)
• using SKOS RDF to transport knowledge to Semantic Web, so informationget expressed in a machine readable way
• Mapping different concept schemes together (for example museum basedvocabularies with library based)
maindata base
nominationdata base
webbased,protected area
application 3
application 2
application 1
editorial system
collaborative work on vocabularies in different collection systems
xTree
We
bse
rvic
e /
RE
ST
what is xTree?
xTree• is a central, web-based tool to administrate
vocabularies (e.g. thesauri, classifications, lists, taxonomies, folksonomies)
• It is compatible with the data model of DD 8723-5 conforming to the British Standard BS 8723-2. Moreover, the xTree model is semanticallyinteroperable with ANSI/NISO Z39.19-2005, ISO 2788, and DIN 1463-1.
• has a multi-lingual Datamodel• the editional system is usable with common web-
browser software (e.g. Firefox 3, Internet Explorer 8)• is easy to handle (e.g. drag and drop)
„stone money“ in xTreetree on the left, selected concept on the right
Translating the AAT
• It is planned to translate the AAT into German mainly by experts and expert groups.
• The hierarchie „Visual and Verbal Communication“ has been loaded into xTree(2688 Concepts)
• The Institut für Museumsforschung (IfM) and Bildarchiv Foto Marburg (Deutsches Dokumentationszentrum für Kunstgeschichte) aredoing a test run of translating a part of VaVC
3. Accumulatorwhere content comes together
museumdat
digiCULT.DokBaseFaustMuseumPlus
museumdat
Intranet Hamburg
How to bring Metadata together?Problems for Data Integration
• Museums using different CollectionManagement Systems (or Excel). à digiCULT solution: use of CRM / CRM Core andmuseumdat-LIDOMapping to museumdat-LIDO should be donein the local collection management systems by the domain experts (non-semanticexperts).
• Co-reference– different terms referring the same concept
„fei“ and „stone money“ are referring to the same thing
– different names referring the same person / organisation. The string „Emil Nolde“ represents the same Person like the string „Emil Hansen“
à digiCULT solution: use of xTree / SKOS / Accumulator
• different Semantic– for one person it‘s the production, for the other it‘s the usageà digiCULT solution: xTree / SKOS / Accumulatoruntil now: simple rules while importing.future ?: cross-refrencing domain vocabulariesto organisation based vocabulary and
then mapping to museumdat-LIDO
Metadata
Index
Portals
www
digiCULT.DokBaseFaustMuseumPlus
Szenario 1:
how content comes
together?
Metadata
Index
many Institutions with a diversity of collectionsand different collection management systems
Portals
www
Szenario 1:
how content comes
together?
Metadata
Index
Result:different semantic withmany formats (XML, Excel)
a lot of work by doing mapping
or chaosPortals
www
digiCULT.DokBaseFaustMuseumPlus
Metadata
Index
loc
alA
pp
lica
tion
s
museumdat museumdat
Szenario 2mapping Collections to museumdat/LIDO by „Non-Semantic Experts“:we have often the same semantic with one format
digiCULT.DokBaseFaustMuseumPlus
digiCULT.meta
Index
A B C
XSLT
Szenario 3using Accumulator:A: Mapping XML/Excel-Data to museumdatB, C: refinement by mapping museumdat to museumdat
digiCULT.meta
Index
A B C
xTree
museumdat
SKOS based Webservice
Szenario 4using terminology services what happens ???
metadata enrichment
…<lido:classification>
<lido:conceptID lido:type="URL">http://www.getty.edu/AAT/300191668</lido:conceptID><lido:term xml:lang="de">Steingeld</lido:term>
</lido:classification>…
museumdat
digiCULT.meta
Index
- Steingeld- Rai- stone money- fei- fé
SKOS RDF over Webservice
<skos:Concept rdf:about="http://www.getty.edu/AAT/300191668"><skos:prefLabel xml:lang="en">stone money</skos:prefLabel><skos:prefLabel xml:lang="de">Steingeld</skos:prefLabel><skos:altLabel xml:lang="en">Rai</skos:altLabel><skos:altLabel xml:lang="en">fei</skos:altLabel><skos:altLabel xml:lang="en"> fé</skos:altLabel><skos:broader rdf:resource="http://www.getty.edu/AAT/300037316" />
</skos:Concept>
WWW
digiCULT.meta
XSLT
museumvok-WS
Using vocabulary in the digiCULT Network, Intranet Hamburg: Connecting museumdat to museumvok
museumdat-XML +
Domain Specific D
ata
museumvok-WS (http, SOAP, XML)
XML / JSONIndexDB
Intranet Hamburg
museumdat-XML
Museumsportal Nord,Europeana, BAM, Prometheus
Collection Management Systems:
Webbased xTree
Central web-based administration of lists and classifications Alignment of norm data, multilingualism etc. to ensure consistent practice
editionalStaff
global Metadata-Container for museumdat-XML and Domain Specific Data
Dokbase.gd, MuseumPlus, Faust
since 2007, only digiCULT internal:
insertVocItem
2010: updateVocItem, deleteVocItem
4. Archaeological items for the world
Sesterz in Museumsportal Saarland
Sesterz in Europeana
From „museumdat“ to „PICA+“– Museen Nord
From „museumdat“ to „PICA+“– museumdat
<?xml version="1.0" encoding="ISO-8859-1"?><museumdat:museumdatWrap xmlns="http://museum.zib.de/museumdat" xmlns:museumdat="http://museum.zib.de/museumdat" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://museum.zib.de/museumdat museumdat-v1.0.xsd" museumdat:relatedencoding="MuseumPlus" museumdat:langencoding="RFC 3066" xml:lang="de"><museumdat:museumdat><museumdat:descriptiveMetadata><museumdat:objectClassificationWrap>
<museumdat:objectWorkTypeWrap><museumdat:objectWorkType >Kragenflasche</museumdat:objectWorkType>
</museumdat:objectWorkTypeWrap></museumdat:objectClassificationWrap><museumdat:identificationWrap><museumdat:titleWrap><museumdat:titleSet>
<museumdat:title museumdat:type="Originaltitel">Kragenflasche</museumdat:title></museumdat:titleSet> </museumdat:titleWrap>
<museumdat:inscriptionsWrap/><museumdat:repositoryWrap><museumdat:repositorySet museumdat:type="current"><museumdat:repositoryName>Archäologisches Museum Hamburg | Helms Museum, Stiftung Historische Museen Hamburg
</museumdat:repositoryName><museumdat:workID museumdat:type="Inventarnummer">MFV 1893-237</museumdat:workID><museumdat:workID museumdat:type="Magazin Nummer">temp47861</museumdat:workID><repositoryLocationName>Archäologische Sammlung/Dauerausstellung (2009)/Tod EG</repositoryLocationName>
</museumdat:repositorySet></museumdat:repositoryWrap>
</museumdat:identificationWrap><museumdat:descriptionWrap><museumdat:displayMaterialsTech>Material: Ton, Technik: aufgebaut, gebrannt, geritzt</museumdat:displayMaterialsTech><museumdat:descriptiveNoteWrap><museumdat:descriptiveNoteSet type="Beschreibung"><museumdat:descriptiveNote>xyz</museumdat:descriptiveNote>
</museumdat:descriptiveNoteSet></museumdat:descriptiveNoteWrap>
</museumdat:descriptionWrap>….
From „museumdat“ to „PICA+“ – concordance museumdat àààà Pica+
<museumdat:style> $SStyle
museumdat:termsourceID=
601.10 048H/00$6
4255
museumdat:termsource=
xTree
museumdat:imported= no 048H/00 4255 $CDID
Naturalismus 048H/00$a
4255
</museumdat:style>
<museumdat:style> $SStyle
museumdat:termsource=
SWD 048H/00$C
4255 $CSWD
museumdat:termsourceID=
4041365-2" 048H/00$7
4255 zusaetzlich $6
museumdat:imported= yes
Naturalismus 048H/00$a
4255
</museumdat:style>
From „museumdat“ to „PICA+“ – PICA+
From „museumdat“ to „PICA+“ – GBV digiCULT
Interoperability via metadata exchange – Viamus
Interoperability via metadata exchange – GBV digiCULT
Interoperability via metadata exchange – OPAL Niedersachsen
The next step: Sharing knowledge via CIDOC-CRM
• Problems
– Longterm-perservation of internet resources
• Virtual Antique Museum 2004
• Pharos-Online 2003
– Loss of information
– Connection of internet resources
• Solution ????
– convert data via CIDOC-CRM
– share data via open interfaces
– use data via CMS
– enrich data via „Web 2.0“
• digiCULT Museen Schleswig-HolsteinAxel VitzthumE-Mail: [email protected]
http://www.digicult-sh.de/http://www.museen-sh.de/
• Verbundzentrale des GBV (VZG)Frank Dührkohp
E-Mail: [email protected]
http://www.gbv.de/vgm/
thank you