The Registry Service is a container of knowledge. It provides useful information regarding a digital object (e.g. a satellite image, an in-situ instrument data, etc.), which can cover the following topics:
- The structure of the digital object (headers, footers, instrument measures, annotations, fixed parts, variable parts, etc.)
- The meaning of that digital object
- Basic information (The so-called “metadata”: acquisition time, lat/lon, etc.)
- Auxiliary Information, such as Sensor Description, physical parameters measured by the sensor, etc.
- Usage Information: how this digital object can be exploited by different user communities
- The rendering information, describing what additional software can be used to display/process/edit the digital object.
This information is retrieved, collected and organized with the main goal to help a user accessing the digital object, understand it and use it for his purposes. In few words it allows “what is unfamiliar to become familiar”. This is particularly important in the Earth Science community where different categories of users may need to access data they do not usually work with (e.g. an Oceanographer wants to access and use Earth Observation data).
There are two implementations of the registry concept. The Framework is used by applications to access any registry.
Web based registry
- Try it out at: [simple-links category=”6″]
- Web based Registry – overview
- The source – mostly PHP files – is available at https://svn.code.sf.net/p/digitalpreserve/code/SCIDIP-ES/software/common/webserver-registry/
- Jar file for Registry Browser
SOLR based registry
- SOLR based Registry – quick start guide
- SOLR based Registry – detailed documentation
- There are SOLR based registry installation files at http://releases.digitalpreserve.info/packages/ with source code at https://svn.code.sf.net/p/digitalpreserve/code/SCIDIP-ES/software/services/Registry-Repository/
The Framework code provides a common interface to a distributed set of registries :