DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-03-22T20:45:07ZDataONE Tasks
Redmine Testing MN Management - Task #8519 (New): meow: Formal Announcementhttps://redmine.dataone.org/issues/85192018-03-22T20:45:07ZAmy Forresteraforres4@utk.edu
<ul>
<li>Verify MN appears as current in MN Dashboard and Search UI (<a href="https://www.dataone.org/current-member-nodes">https://www.dataone.org/current-member-nodes</a>)</li>
<li>Verify DataONE logo / link appears on MN page. (Repeat every year.)</li>
<li>Prepare and make news announcement - Coordinate with MN for any announcements they wish to do from their perspective.</li>
<li>Change the node's main MNDeployment ticket to Operational status.</li>
</ul>
<p>{checklist}</p>
<ul>
<li>Draft news item for public release + MN approval of PR. (<a href="https://drive.google.com/drive/folders/0B18azCDdsZfyYlFqTlhSTWFLYUU?usp=sharing">https://drive.google.com/drive/folders/0B18azCDdsZfyYlFqTlhSTWFLYUU?usp=sharing</a>)</li>
<li>MN social media handles</li>
</ul>
Testing MN Management - Task #8518 (New): meow: Mutual Acceptancehttps://redmine.dataone.org/issues/85182018-03-22T20:45:07ZAmy Forresteraforres4@utk.edu
<p>Verify that the content is synchronizing correctly and the search results appear as expected. Member node approves</p>
Testing MN Management - Task #8517 (New): meow: Register in Productionhttps://redmine.dataone.org/issues/85172018-03-22T20:45:07ZAmy Forresteraforres4@utk.edu
<ul>
<li>Switch node configuration to enable synchronization.</li>
<li>Submit node registration to production CN.</li>
<li>D1 admin approves node registration on CN production server.</li>
<li>Confirm node is synchronizing as expected.</li>
<li>D1 edits custom CN_ properties, as described at <a href="https://github.com/DataONEorg/member-node-info/blob/master/custom_properties.md">https://github.com/DataONEorg/member-node-info/blob/master/custom_properties.md</a></li>
</ul>
Testing MN Management - Task #8516 (New): meow: Implement in Productionhttps://redmine.dataone.org/issues/85162018-03-22T20:45:06ZAmy Forresteraforres4@utk.edu
<p>Ensure that the production version of the MN is ready. This is either a new instance with production content, or the test instance that has been completely cleaned (content and logs).</p>
<ul>
<li>! Disable Sync if re-using test software !</li>
<li>Software Configurations / Node Document / System Metadata checks:
<ul>
<li>URI in node software config shows production version</li>
<li>If applicable, adapter metadata reflects production URI too.</li>
<li>System metadata reflects production URI</li>
<li>Target CN is production hostname.</li>
</ul></li>
<li>Register Contact Subject identity in production version of DataONE LDAP w/ Sign in Link at <a href="https://search.dataone.org">https://search.dataone.org</a></li>
<li>D1 admin approves contact subject in production LDAP.</li>
<li>Request production certificates with prod version of URI and download w/ NCEAS uid. Install.</li>
</ul>
Testing MN Management - Story #8515 (New): meow: Move to Productionhttps://redmine.dataone.org/issues/85152018-03-22T20:45:06ZAmy Forresteraforres4@utk.eduTesting MN Management - Task #8467 (New): test: Display as Upcominghttps://redmine.dataone.org/issues/84672018-03-01T21:04:43ZAmy Forresteraforres4@utk.edu
<ul>
<li>Ensure MN logo in github (<a href="https://github.com/DataONEorg/member-node-info">https://github.com/DataONEorg/member-node-info</a>)</li>
<li>Create new entry for the MN in the Upcoming Nodes Document. (<a href="https://github.com/DataONEorg/member-node-info/tree/master/production/upcoming">https://github.com/DataONEorg/member-node-info/tree/master/production/upcoming</a>)</li>
<li>Confirm MN Dashboard detected change in github and displays the new entry as "upcoming". (<a href="https://www.dataone.org/current-member-nodes">https://www.dataone.org/current-member-nodes</a>)</li>
</ul>
Testing MN Management - Task #8466 (New): test: Test Registrationhttps://redmine.dataone.org/issues/84662018-03-01T21:04:42ZAmy Forresteraforres4@utk.edu
<p>Custom nodes will start off by first registering in Sandbox. Nodes using an existing MN software will register in Stage.</p>
<ul>
<li>Node contact subject approved by D1 admin in DataONE LDAP.</li>
<li>Node software configuration - synchronization enabled if applicable.</li>
<li>Node registration document generated and submitted to Sandbox or Stage CN.</li>
<li>D1 Admin approves node registration on the Sandbox or Stage CN server.</li>
<li>Monitor and verify synchronization, indexing, search behavior.</li>
<li>MN approves display of information in test search interface (<a href="https://search-sandbox.test.dataone.org/#data">https://search-sandbox.test.dataone.org/#data</a> or <a href="https://search-stage.test.dataone.org/#data">https://search-stage.test.dataone.org/#data</a>)</li>
</ul>
<p>A note for custom implemented DataONE services: It's expected that development and testing will be more iterative. When satisfied with results in sandbox, repeat the process by changing target to cn-stage.</p>
Testing MN Management - Task #8465 (New): test: Develop or Implement MN Softwarehttps://redmine.dataone.org/issues/84652018-03-01T21:04:42ZAmy Forresteraforres4@utk.edu
<ul>
<li><p>Change node's primary MNDeployment ticket status to Testing.</p></li>
<li><p>Identity Management:</p>
<ul>
<li>Confirm what nodeID will be used.</li>
<li>Register NCEAS LDAP (<a href="https://identity.nceas.ucsb.edu/">https://identity.nceas.ucsb.edu/</a>) because cert download auth is maintained by separate system.</li>
<li>Use Use cilogon to generate a DataONE LDAP account by logging into DataONE test env. (Sign-in link at <a href="https://search-stage.test.dataone.org">https://search-stage.test.dataone.org</a>)</li>
</ul></li>
<li><p>DataONE Certificate:</p>
<ul>
<li>Request in #CI for a sandbox or stage D1 certificate generated available to NCEAS uid.</li>
<li>Cert/key downloaded by node operator.</li>
</ul></li>
</ul>
<p><strong><em>For a custom implementation of DataONE APIs as new service:</em></strong></p>
<ul>
<li>MN implements full scope of Member Node APIs.</li>
<li>API methods systematically verified by D1 tech lead.</li>
<li>Passes web tester checks (<a href="http://mncheck.test.dataone.org:8080">http://mncheck.test.dataone.org:8080</a>)</li>
</ul>
<p><strong><em>For a DataONE Software Stack</em></strong></p>
<ul>
<li>Install software, SSL cert, and DataONE cert per installation instructions.</li>
<li>If using LE cert, schedule cron for renewal.</li>
<li>Configure software as appropriate (baseURL, Node Contact Subject, replication, etc).</li>
</ul>
<p><strong><em>For a SlenderNode:</em></strong></p>
<ul>
<li>Develop adapter.</li>
<li>Fully test movement of data from source system to target MN software.</li>
<li>Install on MN web server and schedule cron job. Verify cron is running as expected.</li>
</ul>
<p><strong><em>For both:</em></strong><br>
* Verify system metadata of test records. Ensure correct node URI value in auth/orig MN.<br>
* Verify node description document. Ensure that Contact Subject is set to the DataONE LDAP identity string.</p>
Testing MN Management - Task #8464 (New): test: Metadata Validationhttps://redmine.dataone.org/issues/84642018-03-01T21:04:42ZAmy Forresteraforres4@utk.edu
<p>Receive and validate sample metadata records from member node.</p>
Testing MN Management - Story #8463 (New): test: Testing & Developmenthttps://redmine.dataone.org/issues/84632018-03-01T21:04:41ZAmy Forresteraforres4@utk.edu
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Testing MN Management - MNDeployment #8462 (New): Test MN tickethttps://redmine.dataone.org/issues/84622018-03-01T20:57:23ZAmy Forresteraforres4@utk.eduTesting MN Management - MNDeployment #8461 (New): MEOW - Monitoring Ecosystems & Oceans in Waleshttps://redmine.dataone.org/issues/84612018-03-01T20:47:27ZMonica Ihliemail@monicaihli.comTesting MN Management - Task #8383 (New): Feasibility Assessmenthttps://redmine.dataone.org/issues/83832018-02-27T17:32:04ZMonica Ihliemail@monicaihli.com
<p>Initial determination of operational and technical feasibility. Addresses:</p>
<p><strong><em>Operational Feasibility:</em></strong></p>
<ul>
<li>Repository meets sustainability expectations.</li>
</ul>
<p><strong><em>Technical Feasibility:</em></strong></p>
<ul>
<li>What data will be exposed?</li>
<li>Content mutability.</li>
<li>Software needs:
<ul>
<li>DataONE software stack or implement new web service in existing applications (custom stack)?</li>
<li>Full repository or Slender Node?</li>
<li>metadata only or science data + replication?</li>
<li>Repository's in-house preferences? (Java? Python?)</li>
</ul></li>
<li>Consistency of metadata quality.</li>
<li>Level of functionality (tier).</li>
</ul>
<a name="Approval-Change-Status-gt-Planning"></a>
<h3 >Approval = Change Status > Planning<a href="#Approval-Change-Status-gt-Planning" class="wiki-anchor">¶</a></h3>
Testing MN Management - Task #8382 (New): Initial Communicationshttps://redmine.dataone.org/issues/83822018-02-27T17:32:04ZMonica Ihliemail@monicaihli.com
<ul>
<li>Schedule introductory meeting.</li>
<li>Provide potential MN with documentation:
<ul>
<li>What is DataONE? (<a href="https://www.dataone.org/what-dataone">https://www.dataone.org/what-dataone</a>)</li>
<li>Benefits of collaborating with DataONE as a Member Node (<a href="https://www.dataone.org/benefits-becoming-member-node">https://www.dataone.org/benefits-becoming-member-node</a>)</li>
<li>General process of becoming a Member Node (<a href="https://www.dataone.org/member-node-">https://www.dataone.org/member-node-</a> deployment-process)</li>
<li>Responsibilities of a Member Node--Partnership Guidelines (<a href="http://www.dataone.org/sites/all/documents/DataONE_MN_Partner_Guidelines_20131024.pdf">http://www.dataone.org/sites/all/documents/DataONE_MN_Partner_Guidelines_20131024.pdf</a>)</li>
<li>MN Description Worksheet: (<a href="https://drive.google.com/file/d/1pTstSQ2ziDEI-7B1LacU0ZyrsZzL4G3x/view?usp=sharing">https://drive.google.com/file/d/1pTstSQ2ziDEI-7B1LacU0ZyrsZzL4G3x/view?usp=sharing</a>)</li>
<li>MN Deployment Routes (<a href="https://www.dataone.org/member-node-deployment-routes">https://www.dataone.org/member-node-deployment-routes</a>)</li>
<li>Member Node APIs (<a href="https://releases.dataone.org/online/api-documentation-v2.0/apis/MN_APIs.html">https://releases.dataone.org/online/api-documentation-v2.0/apis/MN_APIs.html</a>)</li>
</ul></li>
</ul>
<p>{checklist}</p>
<ul>
<li>Upload completed MN Description Worksheet</li>
</ul>
Testing MN Management - Story #8381 (New): Discoveryhttps://redmine.dataone.org/issues/83812018-02-27T17:32:03ZMonica Ihliemail@monicaihli.com
<p>Discovery is about establishing contact and building a relationship with a potential new member node. In this phase, it is determined if DataONE and the repository are a good fit for one another and if the repository generally meets the requirements of DataONE member nodes. Broad discussions of deployment options may be reviewed as well.<br>
This story is complete when a determination is made to either proceed with planning a new deployment, or that joining DataONE is not an option for the repository at this time.</p>