Ga naar hoofdinhoud

Glossary

Collection Manager​

A person who uses a Collection Management System to create, edit, and publish metadata records for heritage objects, without requiring technical knowledge.

Collection Management System​

Also known as: Collection Registration System (CRS) or Collection Information System (CIS).

A software application used by heritage institutions to create, edit, and publish metadata records about heritage objects. In the context of NDE, a Collection Management System implements the Dataset Register API and the Network of Terms API.

The system may include a separate publication component or layer that wraps the core application; for the purpose of NDE requirements, the system is treated as a whole.

Consumer​

A person or application that uses heritage data published by Data Platforms, typically through a Service Platform or directly via a dataset’s distributions.

Data model​

A formal description of the classes, properties, and relationships used to represent information about a domain, enabling data from different sources to be combined and queried consistently.

Data models can be:

NDE requires the Schema.org Application Profile for NDE (SCHEMA-AP-NDE) to be used when publishing linked data in the heritage network.

Data Platform​

Data Platforms provide access to heritage data, which can then be consumed by Service Platforms.

It can be integrated in a Collection Management System or be a separate system, such as a triple store or a IIIF image server.

Data owners are responsible for Data Platforms.

Defined in DERA (Dutch).

Data Provider​

(corresponds to Dutch ‘bronhouder’ as defined in the DERA).

Dataset Description​

An RDF document that documents a dataset. Formally defined in the Requirements for Datasets. These Descriptions should be registered with the Dataset Register so Consumers can find them and use the datasets.

Dataset Register​

See the Dataset Register service chapter.

Distribution​

A channel through which a dataset is made available, either for downloading (such as a CSV file download or RDF dump), or for querying (such as a SPARQL endpoint). Formally defined in the Requirements for Datasets.

Linked Data​

RDF data that is published according to the Linked Data principles.

Machine-readable​

A way to publish data that can be automatically processed by computer programs.

NDE-compatible​

Conforming to the requirements published by Netwerk Digitaal Erfgoed, so that heritage data and systems can interoperate within the network. The applicable requirements depend on what is being evaluated:

Additionally, the Requirements for Network of Terms Implementations and Requirements for Dataset Register Implementations provide more detailed guidance for Vendors of Collection Management Systems on implementing the Network of Terms and Dataset Register APIs.

Network of Terms​

See the Network of Terms service chapter.

Persistent HTTP URI​

A URI that is resolvable over HTTP(S) and once made available must remain accessible, always pointing to the same resource. A persistent HTTP URI acts both as a URI, providing the resource’s identity, and as a URL, providing its location.

May contain a Persistent Identifier. For more information, see the Publish datasets chapter.

Example: https://n2t.net/ark:/60537/b3KCns.

Persistent Identifier​

The part of a Persistent HTTP URI that uniquely identifies a resource.

Example: ark:/60537/b3KCns.

RDF​

The Resource Description Framework (RDF) is a framework for expressing information about resources, which allows that information to be processed by applications, rather than being only displayed to people. See also the RDF Primer.

Registration URL​

A URL submitted to the Dataset Register API that points to one or more Dataset Descriptions. The Dataset Register fetches and validates the descriptions found at this URL, and periodically re-crawls it to pick up changes.

Defined in the Requirements for Dataset Register Implementations.

Service Platform​

A software application with the purpose of making data from one or several Data Platforms available for a specific purpose, for example through a website or app.

Examples are:

  • making heritage objects from the Dutch colonial past available for heritage research;
  • keeping the memory of World War II alive by presenting stories about it.

Service Platforms are the responsibility of the Service Providers.

Term​

A word, name, acronym, phrase or other symbol with a formal definition, published in the Network of Terms.

Terms describe what heritage is about. Terms are, for example, subjects, persons or places. For example the Night Watch: it is a ‘painting’, made by ‘Rembrandt’ in ‘Amsterdam’.

Yet a term is more than a word. Each term has an identifier, a so-called URI. A URI is a unique address which makes it unambiguously clear which term is meant. For example, the (Dutch) term ‘noodweer’ could be a legal concept or really bad weather? The meaning becomes clear when you read the URI of the term, such as http://www.wikidata.org/entity/Q741507.

In addition, a term can contain additional information, such as a definition or an alternative name. For example the term ‘painting’ with the URI http://vocab.getty.edu/aat/300177435. The extra information about this term makes it clear that it has a synonym (in Dutch), 'schilderstuk'.

Terminology source​

A dataset, such as a thesaurus, reference list or classification system, that contains authoritative terms used to describe heritage objects.

URI​

A Uniform Resource Identifier (URI) uniquely identifies an abstract or physical resource. See also RFC3986.

Vendor​

An organization that supplies a Collection Management System.

Defined in the Requirements for Dataset Register Implementations and the Requirements for Network of Terms Implementations.