© 2021-… Picturae, Heerhugowaard, the Netherlands
The Memorix Application Ontology describes Classes and Properties that are uses in Picturae's Collection Management System.
Parent Class for pagination properties.
Used to link a record to one or more external resources.
Component to link one or more Geonames resources to a Record
Used to link a record to one or more other Records.
The class of information about Accessibility & Rights.
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.
Class for UI components that can be used in Recordtype
UI Components
Depot location information, specific to memorix application.
An editor for marking the audience status of a record. Only accepts memorix:internal or memorix:external
Vastgelegde informatie die als eenheid moet worden behandeld.
Recorded information that must be handled as a unit.
@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 .
Indicates that something may not be used outside of the Memorix application (to be used as value for audience predicate on Context).
Indicates that something may be used outside of the Memorix application (to be used as value for audience predicate on Context).
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.
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.
Switch for indication that a Document should be used as a defauklt asset for a Record/Context
Filesize of document, Memorix always uses bytes as Int and not Text as Schema.org defines.
The document name in DAM (without extension)
An editor for floats. Implicit used if sh:datatype = xsd:float
An editor for xsd:date literals, offering a calendar-like date picker.
Memorix unit used as an entrypoint to all things related to an informationobject.
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.
The Class of accessMode… Datatype Properties that can be used to permit certain actions
An editor for boolean literals, rendering as a select box with values true and false. Implicit used if sh:datatype = xsd:boolean
An editor for nubers. Implicit used if sh:datatype = xsd:decimal
Links a Record to its Context
Allow display of attached assets.
Marks a Recordtype as usable in a Collection
Links a AccessibilityAndRightsComponent to its Context
Links zero or more History reources to a Class
Property that makes a something internal/external from the Application perspective. An external record may never be published outside the Memorix Application.
Specifies a list of skos:ConceptSchemes that can be used for picking Concepts.
Allow request/reservations.
If set to TRUE then a schema:DigitalDocument is the default Document for a Record.
Links an InformationComponent to a RecordType. Can be used as information for frontend rendering.
Allow scanning on demand.
Collection of links to digital documents stored in Asset Manegement System.
If set to TRUE then it is required to show Creditstatement.
Allow download of attached assets.
Link to a Context/Record from Memorix
Links from a Record to Media (e.g. Nuxeo links, IIIF Manifest files, etc)
Used for direct and limited (only creation and modification a.k.a. replacement) history on a Resource. There is also a full History log for Resources (memorix:History) link to a Resource by the Resources object property memorix:hasHistory
Links a Context object to a Record, AccessibilityAndRightsComponent or schema:DigitalDocument
UUID of a Depot object registred in Memorix. Depots are not expressed as RDF Resources!
UUID of a Depot object registered in Memorix. Depots are not expressed as RDF Resources!
Indicator for number of items (e.g. Records or Concepts) Sthat are contained by Sets, Collections and ConceptSchemes
Property that defines when a restriction to Conditions of Access expires.
UUID of a Depot Container that markes the start of a physical depot location of an object registered in Memorix. Containers are not expressed as RDF Resources!
Current page of result set (offset by 1).
UUID of a Depot Container that markes the end of a physical depot location of an object registered in Memorix. Containers are not expressed as RDF Resources!
Property that defines when the copyright expires.
Maximium number of items in page of a result set (a.k.a. as 'limit').
Relevance Tuning for Elastic: Weight. Each field has a possible weight of 0 to 10, 10 being the most substantial weight.
The class of Memorix individuals that do not have a specific name, or have a name that no one can come up with during a meeting.