Model import

CIDOC CRM is used as basis for the underlying data model of OpenAtlas. Currently we are using CIDOC CRM v6.2.1 from
A script is used to parse the specification and import it into a PostgreSQL database (
OpenAtlas "knows" the specification and checks every link that it is made with the application. There is also a function to check all existing links which can be useful e.g. after an import of external data.


We don't import or use inverse properties (ending with i) since our links are directed anyway. Nevertheless their labels are imported for more convenient viewing of relations.
Properties with URLs as domain/range are ignored because our system has a foreign key on domain which must match an existing class.
Also some properties are linked as sub_properties_of properties with the i suffix. Since we don't use inverse properties in the database (direction is determined through domain/range selection)they are linked to their counterpart without i.


We try as long as possible to only use the official CIDOC CRM and to not introduce own classes or use extensions, which we managed so far.
But we are using some shortcuts in the software/database for performance and to keep the code base maintainable.
More details: CIDOC CRM shortcuts.

OpenAtlas class mapping

OpenAtlas uses the CIDOC CRM in the application but because of contextual differences we needed a more fine grained model for the user interface.
E.g. E33 Linguistic Object can be a source or a source translation which have different forms in different context.
An overview of internal mapping and CIDOC CRM classes can be found here

Here you can see a simplified version of the model used in OpenAtlas which is based on classes and properties of the CIDOC CRM.

Updated by Alexander Watzinger 1 day ago · 13 revisions

Also available in: PDF HTML TXT