Skip to content
Alina-Packed edited this page Sep 13, 2022 · 6 revisions

logo-culturize-klei-web

What is cultURIze-Web

CultURIze is an automated workflow to create and activate persistent URI’s for entities, managed by cultural heritage institutions. The workflow consists of three systems communicating with each other:

  • collectionmanagementsystem (CBS), where users record metadata about cultural heritage objects
  • integration plug-in, which enables communication between the CBS and the cultURIze webservice
  • you're own webserver with installed cultURIze webservice, which activates persistent URI’s and resolves them to a corresponding webresource

Who needs cultURIze-Web

Registrars, curators and managers of small or medium cultural heritage collections. These heritage institutions need to have a more advanced digital infrastructure to set up this workflow (collectionmanagementsystem, integration plug-in, webserver) Others can set up the manual cultURIze workflow for persistent URI's.

How does it work

The workflow consists of two steps:

Step 1. Create a persistent identifier and a persistent URI for an entity

This step should be executed by:

  • the collectionmanagementsystem or;
  • the integration plug-in, using an external identifier generator such as NOID, that is activated by the collectionmanagementsystem

The requirements for collection management system and integration plugin

Step 2. Activate a persistent URI

This step should be executed by the cultURIze webservice. In this step the information about the persistent URI and a webresource to which it should resolve has been sent to the cultURIze webservice. The webservice activates the resolving function and reports the status of the resolving back to the integration components.

Where do I start?

Persistency of identifiers is depended on the persistency of it's management. A cultural heritage organisation is therefore advised to begin with thinking about it's Persistent identification strategy where the infrastructure, the management and the syntax of persistent URI's should be captured. These publications can help you with that:

The following step would be to check if your infrastructure meets the requirements for the automated workflow of cultURIze-web.

For the installation of the cultURIze-web go to culturize-web-installation