Managing Display of Upcoming Nodes

Upcoming Member Nodes are optionally added to the upcoming Member Nodes list

Adding a MN to the Upcoming Node List

../_images/764d82264c50fc29597776f8924c685a66a6a50e8935c6dfa28de83a30f54a0d.svg

Figure 1. Procedure for listing a MN in the list of upcoming Member Nodes without registering the node in the production environment.

  1. There must be agreement within DataONE and by the MN that they can be listed as upcoming.
  2. For the MN to display properly a number of custom properties must be set, and the values for these should be recorded in the corresponding MN Deployment ticket in readmine.
  3. The logo for the MN must be ready for display and present in the web folder on in the member-node-info repository on GitHub.
  4. Adding an node entry in the upcoming.xml document and committing the change to GitHub will trigger the listing of the node as upcoming in the dashboard.
  5. The node should appear in the dashboard within 15 minutes.

Registering an Upcoming Member Node

The process of registering a node will add it to the production node list reported by the Coordinating Nodes.

../_images/d1aab8fc7186799ab3d753f4f384e61853cc7a345d4ecac394e16f96e07faef9.svg

Figure 2. Procedure for listing a Member Node as upcoming when it is registered with the production Coordinating Nodes.