LDTO

Person, group, organization or functionary.

A government organization, a natural person, a company. https://data.razu.nl/id/actor/feae08aa6f9214231815e9ed7b3816d9.

• Archiefvormer ^op
• Betrokkene actor ^op

Instances of this class usually consist of a blank node with properties ldto:beperkingGebruikTermijn and ldto:beperkingGebruikType.

• Termijn ^op
• Beperking gebruik type ^op

A collection of data in an electronic form, which can be handled and addressed by an electronic device under a single name. LDTO keeps the MDTO distinction between an information object as a unit of information, regardless of its form, and the specific form in which this information is represented. Files are one form of representation (also called manifestation).

An audio file, a text file.

• URL Bestand ^op
• Bestandsformaat ^op
• Checksum ^op
• Omvang ^dp

Person or organization that is relevant within the context of the creation and use of this information object. Instances of this class usually consist of a blank node with properties ldto:betrokkeneActor and ldto:betrokkeneTypeRelatie.

• Betrokkene actor ^op
• Betrokkene type relatie ^op

Instances of this class usually consist of a blank node with properties ldto:checksumAlgoritme, ldto:checksumWaarde and ldto:checksumType.

• Algoritme ^op
• Datum checksum ^dp
• Waarde ^dp

Instances of this class usually consist of a blank node with properties ldto:dekkingInTijdBeginDatum, ldto:dekkingInTijdEindDatum and ldto:dekkingInTijdType.

• Dekking in tijd begindatum ^dp
• Dekking in tijd einddatum ^dp
• Dekking in tijd type ^op

Instances of this class usually consist of a blank node with properties ldto:eventResultaat, ldto:eventDatum and ldto:eventType.

• Resultaat ^dp
• Tijd ^dp
• Type ^op

• Beperking gebruik gegevens ^c
• Betrokkene-gegevens ^c
• Checksum-gegevens ^c
• Dekking in tijd-gegevens ^c
• Eventgegevens ^c
• Identificatiegegevens ^c
• Termijngegevens ^c

Instances of this class usually consist of a blank node with properties ldto:identificatieBron, ldto:identificatieKennmerk.

• Bron ^op
• Kenmerk ^dp

A self-contained set of data with its own identity. An information object (IO) can be composed of smaller information objects. This is called an aggregation. For example, the file of a permit application is an aggregation, containing the application, decision and all other relevant IOs. IOs can be represented by ldto:Bestand entities, ex: a .doc file or a .pdf representation of an IO.

Information objects in the context of LDTO are information objects that arise from government tasks.

A document, a database, a dossier, a website.

• Aggregatieniveau ^op
• Archiefvormer ^op
• Beperking gebruik ^op
• Betrokkene ^op
• Classificatie ^op
• Dekking in ruimte ^op
• Dekking in tijd ^op
• Event ^op
• Is onderdeel van ^op
• Omschrijving ^dp
• Trefwoord ^dp

• Is onderdeel van ^op
• Is representatie van ^op

Physical or online place in space.

MDTO doesn't impose any additional requirements on how a location is recorded. Ideally, reference should be made to a term in an existing registry, such as the BAG (Road Registration and Allocation of Buildings), or to a term in an existing glossary, such as that used by OWMS.

A BAG location, a province, a road.

A physical, digital or conceptual thing in the real world that is of interest to an organization.

A location, an application, a text document, a business activity, a bridge, a car.

• Identificatie ^op
• Naam ^dp

• Bestand ^c
• Informatieobject ^c

Data about the period for which a retention object should be retained. This class usually consists of a blank node with properties ldto:termijnEinddatum and ldto:termijnLooptijd.

• Einddatum ^dp
• Looptijd ^dp

The Access identifier of the file. RAZU plans this to be persistent.

The aggregation level of the information object. Provides information about the nature of the information object.

For RAZU, this should link to a term in the Aggregatieniveaus thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/aggregatieniveau/37b10081ed00e0e430c071ed04c99aee thesaurus

The hierarchical structure of Information Objects is intellegible via its aggregation level. IOs can have aggregation level 'Archiefstuk' > 'Serie' > 'Archief'

The organization responsible for for creating and/or receiving the information object.

For RAZU, this should refer to a term in the Actoren thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/actor/bd4867122112bf6248d97334ea20479e

A restriction placed on the use of the information object.

For RAZU, the ldto:BeperkingGebruikGegevens entity should link - via ldto:beperkingGebruikType - to a term in Typering mogelijke beperkingen gebruik thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/beperkinggebruiktype/eec50697074c187a5e279dbd44252ad1.

The period within which the restriction on use applies.

The type of restriction placed on the use of the information object.

For RAZU, this should refer to a term in the Typering mogelijke beperkingen gebruik thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/beperkinggebruiktype/eec50697074c187a5e279dbd44252ad1.

Geen openbaarheidsbeperkingen/No access restrictions, Auteursrechten verlopen/Author rights expired, Openbaarheidsbeperkingen/Access restrictions

The format of the information in a computer file.

For RAZU, this should refer to a term in the Bestandsformaten PRONOM-based thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/bestandsformaat/21b73c5c25b191625d98b2b9bd5826ba.

A person or organization that is relevant within the context of the creation and use of this information object, other than the archivist.

the applicant for a permit, or the employee to whom a personnel file pertains.

The person or organization involved in the information object.

For RAZU, this should refer to a term in the Actoren thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/actor/bd4867122112bf6248d97334ea20479e

Characterization of the actor's involvement in the information object.

For RAZU, this should refer to a term in the Aard betrokkenheid thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/betrokkenheid/8e5fc8818e2acb55185b9330d81a3b53

Data used to determine if the file is damaged or modified.

The algorithm used to create the checksum.

For RAZU, this should refer to a term in the Begrijppenlijst amgoritmes thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/algoritme/15eda032483eb222b6992b55bc0e50ea

Message Digest Algorithm 5 (MD5)

Classification of information objects in a logical context, as defined in a classification schema.

For RAZU, this should refer to a term in the Type of soort informatieobject thesaurus (a skos:ConceptScheme) https://data.razu.nl/id/soort/bbc3a6702c26cc0f1ca33eb5e80c9d4a

an Information object in our Newspaper collection could be classified as 'Aflevering', 'Pagina' or 'Krant'. Other possible classification examples: 'Bibliografische collectie', 'Foto', 'Vergadering'.

Place or location to which the content of the information object relates.

A point in time or period to which the content of the information object relates.

In LDTO, the property and its related metadata, refer to the relative time coverage of the records stored at RAZU, not to the absolute time covered by those works. For instance, a publication may have been issued from 1930 to 1980, but RAZU might store only records issued from 1950 to 1980. More details should be specified via ldto:dekkingInTijdType.

Event that occurred related to the creation, modification, destruction, and management of the information object and its associated metadata.

Events described using these metadata should be those happened to an IO before its ingestion at RAZU, hence,these information should be submitted, if known, by archive creators. Events happening to IO during transfer and ingestion at RAZU will be recorded in a separate event log.

Denotation of the type of event.

Data used to identify the object.

Origin of the attribute. The source system used to assign identification.

ISBN, BAG, Internal Actorenregister.

The parent aggregation of which this IO is directly a part of.

By means of aggregation, related information objects are grouped. This also makes it clear what the context of an information object is. RAZU uses this property, not the MDTO inverse mdto:bevatOnderdeel.

Reference to the IO of which the file is a (partial) physical representation.

RAZU uses this property, not the MDTO inverse mdto:heeftRepresentatie.

JPEG file that is a representation of a document, E-mail file that is a representation of a case or part of it.

Additional description of use limitation. As an addition to use limitation type.

The date on which the checksum was created.

The value of the checksum.

The start date of the period to which the content of the information object relates.

In LDTO, this property refers to the relative time coverage of the records stored at RAZU, not to the absolute time covered by those works. For instance, a publication may have been issued from 1930 to 1980, but RAZU might store only records issued from 1950 to 1980.

The end date of the period to which the content of the information object relates.

In LDTO, this property refers to the relative time coverage of the records stored at RAZU, not to the absolute time covered by those works. For instance, a publication may have been issued from 1930 to 1980, but RAZU might store only records issued from 1950 to 1980.

Description of the outcome of the event insofar as relevant to the sustainable accessibility of the information object.

The timestamp at which the event occurred.

An attribute used to identify an object.

For a given 'identificatieBron', 'identificatieKenmerk' should be unique.

123e4567-e89b-12d3-a456-426614174000 (UUID), 789047706205 (ISBN), 0518100000320637 (BAG ID)

A meaningful name under which the object is known.

Description of the content of the IO.

The size of the file in bytes.

The date on which the access attribute expires.

The amount of time in which the termEnd Date is reached after the trigger occurs.

Sometimes the end date of the period depends on an event. From that event (the trigger), a certain period (the term) starts before the end of the period is reached.

• We prefer to use thesauri, but this can be used for all terms that can't simply be structured into a thesarus. And to possibly implement keyword search in the future.

• A keyword assigned to the IO.