EarthCube Resource Registry
The EarthCube Resource Registry (ECRR) is intended to provide immediate access to a list of EC capabilities to understand what EC is, and what it isn’t. To support this goal, the ECRR project has developed several persistent resources available for wider EarthCube use:
- EarthCube resource registry ontology, registered in ESIP Community Ontology Repository
- 15 Controlled Vocabularies for resource description, registered in ESIP Community Ontology Repository
- Establishment of a URI naming authority for ark: identifiers, using the EZID system.
- EZID proxy wrapper to assist with URI registration; This will be useful for EarthCube and other EZID users
- A version 1 deployment registry system that can support documentation of resources using specified vocabularies, registration of new resources, and API access to resource descriptions.
- 216 resource description records loaded into the registry
As a convenience, here are some links to access the registry and related documents:
- SuAVE viewer for EarthCube resources
- Resource Registration Form for submitting resources:
- Resource Registry SPARQL endpoint (username and password sent by email)
- Documentation on mapping resource descriptions to the registry ontology and JSON-LD serialization. Project document with guidance on JSON-LD encoding.
- Controlled vocabularies Google Sheet (one tab for each vocabulary) This sheet is live-linked to the submission form, so column headings shouldn’t be edited or modified - but individual entries can be changed.
EarthCube Resource Registry Presentation - https://drive.google.com/file/d/1dwIUliAurfFstWRSiY74UBoUSaJYlVvc/view
Main GitHub Organization - https://github.com/earthcubearchitecture-ecresourcereg
EarthCube Resource Registry (ECRR) Version 1 Implementation
The EarthCube Resource Registry (ECRR) Version 1 is an integrated system for populating and exploring registry content. This section provides an overview of the system workflow; see the full project report for a more detailed description of operation and components. Figure 1 is an overview of the components in the workflow for registering new descriptions, and for accessing the registry.
- A user submits information describing a new resource for use by EarthCube using a web form interface. Pick lists in the form are generated from controlled vocabularies.
- When the user submits the form, a back end script generates a JSON-LD document containing the new resource registration information
- The JSON-LD document is copied to a Google Drive directory for direct access via URL.
- The p418 Miller process loads the JSON-LD into a MIMEO object store and generates a set of triples for loading into a triple store for rdf/SPARQL based access
- The resource description is formatted for presentation using the SuAVE interface for user search and browsing of the registry content.
- Users can access the system using the SuAVE interface, with SPARQL queries on the triple store, or via links to the JSON-LD documents in the Google Drive.
EarthCube Resource Registry Development Team
- Ruth Duerr - Ronin Institute for Independent Scholarship - Research Scholar
- Stephen Richard - US Geoscience Information Network (USGIN) Foundation - President
- Ilya Zaslavsky - San Diego Supercomputer Center Spatial Information Systems Laboratory - Director
- Eric Lingerfelt - EarthCube Science Support Office - Technical Officer
EarthCube Resource Registry Advisory Team
- Felimon Gayanilo - Harte Research Institute for Gulf or Mexico Studies
- Nick Jarboe - Scripps Institution of Oceanography
- Anna Kelbert - USGS
- Rebecca Koskela - DataONE
- Karen Stocks - Scripps Institution of Oceanography