Member Nodes

1/24/18 Call {Monica, Amy, Steve Richard}: PPT presentation
* Provided Partnership guidelines pdf & MN Description document to be completed and submitted

CHAT NOTES: Data files - http://get.iedadata.org/metadata/iso/mgdl/

http://get.iedadata.org/metadata/iso/mgdl/2_iso.xml
gmd:identifier>
gmd:MD_Identifier>
gmd:code>
gco:CharacterString>doi:10.1594/IEDA/300002

1/24/18: email to Steve Richard

apparently the US Antarctic Program Data Center (USAP-DC) is already a DataOne member node. If that’s true it presents a problem with granularity of MN participation. It might force us to register EarthChem and the Marine Geoscience Data System as member nodes separately, unless it is technically possible to conflate the existing USAP member node into a new IEDA member node and deprecate the USAP MN. There are various aspects—what’s easiest (or possible) technically, what policies are on D1 side, and what IEDA management decides to do.

{reply} USAP-DC is currently NOT a MN... if you want to further discuss setting up each of your source repositories as individual nodes, DataONE can facilitate but that cannot be done from a single installation. In other words, you would need to support multiple software installations—one for each.

2/15: inform Steve that DataONE is going to start working on adding the ability to deploy multiple Member Nodes from a single installation of the web app.

{Steve reply}: Maybe the IEDA node can be a guinea pig?
* not sure whether I’ll stay engaged with the DataOne implementation, still working out my project scheduling details. Kerstin should be your contact point going forward.