BM extensions to CRM
Developed by Seme4 as part of BM collection data mapping to RDF in the CRM schema

There are currently no attachments on this page.

BMX Description

very informative description of the mapping, shows the complexity of museum data.
detailed description of the developed CRM extension ontology (BMX).
[^bm-extensions.ttl]: BMX ontology definition. It's RDFS only, not OWL
http://crm.rkbexplorer.com: live links to CRM & BMX classes
http://collection.britishmuseum.org/: live links to BM objects
(was http://bm2.rkbexplorer.com during development)
instructive usage guide for the CRM

D1 - BM to ResearchSpace- Conversion Process and Schema.pdf, Ian Millard, Seme4. "Recommended process for converting data from a Collections Management System in the Cultural Heritage domain into Open Linked Data"

demonstrate feasibility for converting the entire Collections data from the British Museum into Linked Data
Describes the developed ETL tool "makeRDF": based on config files, uses xpath, similar to xslt but simpler
nice intro to CRM
recommended URI allocation:
http://collection.britishmuseum.org/object/PPA1818832 : artifact (non information resource)
http://collection.britishmuseum.org/object/PPA1818832.html : html representation (information resource for humans)
http://collection.britishmuseum.org/object/PPA1818832.rdf : rdf representation (information resource for computers)
http://collection.britishmuseum.org/object/PPA1818832/production : info about production (who when where created it)
etc
14Gb of XMLs exported from BM's collection system (Merlin). Took several weeks (SSL says it'd have been faster if they knew better)
Merlin is a C/C++ system with a proprietary OO database
BM has 2M objects, 560k of them have images. The CRM RDF has maybe 100 triples per object
RDF takes between 12 and 24 hours to assert depending on the triple store employed
BM's Merlin model is based on the SPECTRUM standard for Museum Documentation. The functionality of other museum collection systems is also based on SPECTRUM