Memorix Application Ontology

The Class of accessMode… Datatype Properties that can be used to permit certain actions

The class of information about Accessibility & Rights.

An editor for marking the audience status of a record. Only accepts memorix:internal or memorix:external

What is this??

An editor for boolean literals, rendering as a select box with values true and false. Implicit used if sh:datatype = xsd:boolean

Base Class for main Memorix Classes

Collections are permanent groupings of Records that are conceptually linked. Possible uses could be for works that were donated as a group, objects that all belonged to the same person, or that were shown together in a historical exhibition etc. Normally you wouldn’t use this to describe a category of works such as “books,” though that is your choice. Object can only be in a single collection.

@prefix dct: <http://purl.org/dc/terms/> .
@prefix memorix: <http://memorix.io/ontology#> .
@prefix recordtypes: </resources/recordtypes/> .
<> a memorix:Collection ;
  dct:description "Collection of Persons and Organisations" ;
  dct:title "Persons & Organisations" ;
  memorix:hasRecordtype recordtypes:All .

Memorix unit used as an entrypoint to all things related to an informationobject.

What is this??

An editor for xsd:date literals, offering a calendar-like date picker.

Depot location information, specific to memorix application.

Used to link a record to one or more external resources.

An editor for nubers. Implicit used if sh:datatype = xsd:decimal

An editor for floats. Implicit used if sh:datatype = xsd:float

Component to link one or more Geonames resources to a Record

The class of Actions performed on a resources by an Agent at a certain Time. Note there is also a ObjectProperty 'history' on Resources which is used for last modification and creation history.

Used to link a record to one or more other Records.

Recorded information that must be handled as a unit.

Record Types are the most commonly used way to categorize Records in your collection. The main guideline is to choose Record types that are broad enough so that an Record can never be more than one type (ie a painting can never also be an moving image). If you would like to describe your Records more specifically, you can supplement this categorization with an additional "subtype" dropdown menu on the record editor itself. For example, an object of type "ephemera" could have a subtype list of "postcard," "poster," "letter," etc.
A subtype list could potentially be repeatable, so you would have the opportunity to assign multiple subtypes if that's appropriate. Record types are described using SHACL Nodeshapes.

Parent Class for pagination properties.

Sets are designed for temporary and arbitrary groupings of your Record, often for a practical task such as creating an online exhibition, or creating a working list of images for publication etc. Sets can contain Records from one or more Collections.

Class for UI components that can be used in Recordtype