Infrastructure

Emailed all node owners the following on May 8, 2012:

@
I'm emailing you because you are listed as the main contact for one of the repositories that is about to become a DataONE Member Node when we transition to production status. In order for this to happen, we need to decide on permanent node identifiers for each of the member nodes. These are short strings that act as the key for identifying the node in all DataONE systems (for example, for the Knowledge Network for Biocomplexity MN, the nodeid will be 'urn:node:KNB'). The nodeid should be memorable, but is not meant to be particularly human readable; rather, it is accompanied by other node metadata when the node is registered, including the node name, and the node description, both of which are meant to be human readable, natural language descriptions of the node (and can change).

To proceed, I have proposed a set of nodeids to be used for the initial DataONE nodes:
http://mule1.dataone.org/OperationDocs/membernodes.html

Please review the list of nodes and their proposed nodeid, and let me know if you would like changes for the node you manage (e.g., 'urn:node:USGSCSAS' for Viv, 'urn:node:DRYAD' for Ryan, etc). I need to know this ID in order to generate an x509 certificate for each node. So, I'd like to work this out this week. Keep in mind that, although the IDs are supposed to be memorable, you should try to limit the amount of descriptive information in the nodeid because it is immutable once it is set. There is a 25 character limit for the whole nodeid Please send me any proposed changes by the end of the week if possible, and let me know if you have any questions.
@

Will close ticket after gather ing responses this week.

All node ids have been edited and approved, and are listed here: http://mule1.dataone.org/OperationDocs/membernodes.html

Still need to establish correct contact after the Production LDAP/Portal are available to register the node contacts.

All nodes contacted and nodeids finalized. See Operation Docs for listing,