About PDS Registry
PDS Registry provides functionality for tracking, searching, auditing, locating, and maintaining artifacts within the system. These artifacts can range from data files and label files, schemas, dictionary definitions for objects and elements, services, etc. The core functionality for this component is satisfied by Elasticsearch.
For Build 9b (June 2019), the Registry and Search components of the PDS4 system received a major upgrade and significant re-design to greater leverage the power of Elasticsearch. We are continuing to improve our documentation, but please do not hesitate to send questions, comments, change requests and bug reports to the PDS Operator at pds_operator@jpl.nasa.gov and we would be happy to help work through any issues you are having.
PDS Registry and Related Software
- Java is required to run Elasticsearch, Harvest, Registry Manager and other tools.
- Registry data is stored in Elasticsearch.
- Registry Manager command-line tool is designed to load, delete and export registry data. It can also create and delete registry index in Elasticsearch.
- Harvest is a tool to crawl and extract metadata from PDS4 files. Extracted metadata is stored in an "intermediate" JSON or XML file which can be loaded into Elasticsearch or Solr by Registry Manager or other tools.
The high level architecture of PDS Registry and its main components is shown below.

Support
Found a bug? Or want a new feature? We would love your feedback and contributions. Here are some links to our public Github repository for source code and submitting issues:
- Issue Tracker: https://github.com/NASA-PDS/pds-registry-app/issues
- Source Code: https://github.com/NASA-PDS/pds-registry-app
Need help with installation or operation of the software, or any other additional feedback, please contact us at pds_operator@jpl.nasa.gov.