1 / 19

Multidisciplinary Research Mapping with CIDOC CRM

This project explores the implementation of CIDOC CRM in a relational database to map and analyze multidisciplinary research activities, focusing on the history of mining. It includes archaeology, history, linguistics, surveying, archeometallurgy, ethnology, mineralogy, botany, archeozoology, and dendrochronology.

egallagher
Download Presentation

Multidisciplinary Research Mapping with CIDOC CRM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Overview • Conceptual part • Background - Multidisciplinary project • Mapping - Identify classes and properties of the CRM • Use TYPE (E55) class for specialization • Implementation part • System Architecture • Relational database – structure, table group • User Interface for node and tree navigation • GIS integrationwithexample

  2. Background - Multidisciplinary project Research on the history of mining activities from prehistoric to modern times • Archaeology • History • Linguistics • Surveying and Geoinformation • Archeometallurgy • Ethnology • Mineralogy • Botany • Archeozoology • Dendrochronology

  3. Mapping - Identify CRM classes and properties iscomposedof (P46) PhysicalObject (E19) isformerorcurrentlocation (P53) Physical Feature (E26) Place (E53) was measuredby (P39), usedspecificobject (P16) has Type (P2) refersto (P67) Research Activity (E7,E16) carried out by (P14) Information Object (E73) Type (E55) Person (E21)

  4. Use TYPE(E55) for specialization - structured in CRM classes Research Activity (E7) Type (E55) Excavation Research Activity (E7) Measurement (E16) Dendrochronologicalanalysis Information Object (E73) PhysicalObject (E19) Physical Feature (E26) Pollen analysis Person (E21) Place (E53) xyz Appellation(E41) Survey

  5. Example of an Excavation Classes: Place (E53) Physical Feature (E26) Type (E55) PhysicalObject (E19) Research Activity (E7) Person (E21) Information Object (E73) Instances: Mauk F Schwarzenberg Moos woodentrough Schwarzenberg Moos excavationsite artefact PollenMaukF troughscan pollenanalysis Weinold, Grimm,.. Goldenberg, Töchterle,.. Nicolussi, Pichler,.. laserscanning MaukF Survey ExcavationMaukF survey Mauk F Dendro excavation Hanke, Moser dendrochronologicalanalysis Oeggl, Breitenlecher,.. terrainMaukF excavationMaukF terrain model pollenMauk F trough 3D modell excavationreport pollenprofile 3D Modell

  6. System Architecture GIS Content Management System Database CRM structured data non-structured data spatial data

  7. Relational database structure • Spatialdata • Objectrelations (Properties) Place (E53) Ontology P53 hasformerorcurrentlocation Point (E47) Classes Line (E47) P7 tookplaceat Class hierarchy Polygon (E47) Properties P46 iscomposedof • Thesaurus Objectinstances P39 measured Type (E55) Physical Feature (E26) P39 measured PhysicalObject (E19) P14 carried out by Research Activity (E7) Terms P2 has Type Person (E21) Information Object (E73) xyz P67 refersto xyz Appellation (E41) P2 has Type

  8. CIDOC CRM relational DB representation Classes Class hierarchy Properties Domain Range

  9. CIDOC CRM views Class hierarchy with parent classes All properties of E26 Physical feature

  10. Ontology creates a Network Schwarzenberg Moos Mauk F Schwarzenberg Moos woodentrough excavationsite Goldenberg, Töchterle,.. Oeggl, Breitenlecher,.. PollenMaukF troughscan pollenanalysis laserscanning MaukF Survey Mauk F Dendro ExcavationMaukF survey dendrochronologicalanalysis excavation Hanke, Moser Weinold, Grimm,.. terrainMaukF excavationMaukF terrain model pollenMauk F trough 3D modell excavationreport pollenprofile Nicolussi, Pichler,.. 3D Modell

  11. Database – Node Interface Object relations (Properties) Typ (E55) PhysicalObject (E19) woodentrough Place (E53) Mauk F Schwarzenberg Moos Information Object (E73) Research Activity (E7) Physical Feature (E26)

  12. Network to Tree Place asentrypointtothenetwork -> Places aretherootsofthetree Place (E53) Schwarzenberg Moos Physical Feature (E26) Mauk F Schwarzenberg Moos PhysicalObject (E19) woodentrough trough 3D modell Research Activity (E7) Person (E21) troughscan Information Object (E73) Moser Hanke Information Object (E73) excavationMaukF Research Activity (E7) ExcavationMaukF Person (E21) Goldenberg Töchterle dendroMaukF Research Activity (E7) Person (E21) Nicolussi Pichler Place (E53) Mauk E Physical Feature (E26) Mauk E Mining tunnel PhysicalObject (E19) MaukEcharcole

  13. DB Interface - Tree Interface Schwarzenberg Moos Mauk F Schwarzenberg Moos woodentrough Mauk E excavation trough 3D modell Goldenberg excavationMaukF Goldenberg

  14. CRM Data in GIS Amountofobjects E7 Research Activity E26 Physical Feature E73 Information Object E19 PhysicalObject

  15. Example: Show collaboration at research sites • Goal: a map with the amount of research activities at one place, showing the participation of project parts • Guidelinestodataentry • Quality control woodentrough Mauk F Schwarzenberg Moos Schwarzenberg Moos artefact excavationsite Mauk F Dendro ExcavationMaukF dendrochronologicalanalysis excavation Nicolussi, Pichler,.. Goldenberg, Töchterle PP13 PP06

  16. Map

  17. Conclusion • Results • CRM is very useful to model multidisciplinary research • CIDOC CRM can be completely implemented in a relational database • Tree view with Place as root enables GIS use • GIS can be used to do spatial visualisation or analysis • Discussion • Spezialisation within TYPE (lossofinteroperabilityifnostandardized Thesaurus isused) • Guidelines for data modeling • what classes correspond to what reality • when use a type, when an instance • User interfaces for not CRM literate people

More Related