3/12/18: email Steve to move ahead with setting up a distinct node for each of their repositories (discussed in January). We suggest they first just get one node setup-- best to choose either ECL or USAP to tackle first (GMD metadata). Once they let us know, Monica will schedule a time to install the code and run through the configurations.
* they still need a subdomain configured in order to register for a SSL certificate.

3/19/18 - sent follow-up email

{reply} reviewing completed draft of the MN information form. Ready to schedule call with Monica— have the Amazon VM set up with MN software, and will look into attaching it to a domain name.

IEDA decision making: Deploy 1 or 3 GMN instances
3/20: steve asking timeline for multiple deploy capability

{Monica response} manage multiple nodes from a single installation from the web app will probably not be worked on till a little later this year
* setting up your 3 contributors as distinct Member Node repositories could be a great choice for IEDA
* can certainly setup IEDA as a single Member Node on a single VM. In that case, IEDA will be listed as the source in the main Member Nodes list in search.dataone.org, and there will be only one logo.
* if anticipate that you would want to switch to operating as multiple Member Nodes at a later point in time, I would discourage you from this choice. It would be a difficult amount of work to go back and try to alter information about the metadata later once its already in Production

3/26/18: Dave to reach out to Kerstin & Stephen to get some answers about branding their data sources

• IMPORTANT: need long term solution to how they exposing their data

4/6/2018: meeting https://epad.dataone.org/pad/p/IEDA_Planning
Dave, Monica, Amy, Steve Richard (IEDA)

• need long term solution to how they expose their data + update on where they are re: branding decisions

sent work plan version 8/20/2018 to IEDA

8/27/18: follow-up email
* Kerstin on vacation...I'll try to get to it ASAP when back.