Task #4202: EDAC node name and description should be more informative - Member Nodes - DataONE Tasks

Task #4202

MNDeployment #3221: EDAC member node

EDAC node name and description should be more informative

Added by Rob Nahf about 11 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Rob Nahf

Target version:

Operational

Start date:

2013-12-12

Due date:

% Done:

100%

Story Points:

Sprint:

Description

The node's name and description will be visible through applications (ONEmercury for example), and should be informative for users unfamiliar with EDAC GSTORE.

I tried finding information on the scope of GSTORE on the EDAC site, but did not find any information - didn't even find mention to GSTORE. The GSTORE landing page (http://gstore.unm.edu) is similarly unlinked to EDAC, except for a logo and copyright at the very bottom of a long page.

see https://cn.dataone.org/cn/v1/node for examples of names and descriptions from other nodes.

Typically, the description provides some scoping information about the collection, and the name is a either the name of the organization (Earth Data Analysis Center), or if the organization has multiple collections, a combination of the organization and collection name. Given that both EDAC and GSTORE are in the node id, perhaps both should be in the name. (The EDAC site has "Image Archive" and "RGIS Clearinghouse" sections on it's page - are they other collections EDAC maintains?)

History

#1 Updated by Rob Nahf almost 11 years ago

A technical description of GSTORE:

All of the data available through the data portal is stored on the GSTORE platform.
The Geographic Storage, Transformation and Retrieval Engine (GSTORE) has been developed as a
flexible, scalable data management, discovery and delivery platform that supports a combination
of Open and Community standards for client access. It is built upon the principle of a services
oriented architecture that provides a layer of abstraction between data and metadata management
technologies and the client applications that consume the services published by the platform.

The GSTORE API is the basis for all of the data portal’s functionality - dataset search,
dataset access, documentation access, and OGC service access

perhaps something like this is more appropriate:

Earth Data Analysis Center's (EDAC) Geographical Storage, Transformation and Retrieval Engine (GSTORE) platform
archives data produced by various NM organizations, including NM EPSCoR and RGIS. GSTORE primarily houses
GIS and other digital documents relevant to state agencies, local government, and scientific researchers. See RGIS
and NM EPSCoR for more information on the scope of data. It currently uses the FGDC metadata standard to describe
all of it's holdings.

#2 Updated by Laura Moyers almost 11 years ago

Target version changed from Deploy by end of Y5Q2 to Deploy by end of Y5Q3

#3 Updated by Rob Nahf almost 11 years ago

% Done changed from 0 to 50
Status changed from New to In Progress

Decided by Karl:

Here goes on the remaining items:

nodeid: urn:node:EDACGSTORE (this covers the possibility of there being other potential GStore instances out there in the world that would also be hosting member nodes)

name: EDAC Gstore Repository (this allows us to consider deploying different/additional repositories some time in the future)

description: (use option B) below

the touched-up version:

Earth Data Analysis Center's (EDAC) Geographical Storage, Transformation and Retrieval Engine (Gstore) platform archives data
produced by various NM organizations, including NM EPSCoR and RGIS. Gstore primarily houses GIS and other digital
documents relevant to state agencies, local government, and scientific researchers. See RGIS and NM EPSCoR
for more information on the scope of those collections. Gstore currently uses the FGDC metadata standard
to describe it's holdings.