DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-10-02T16:51:19ZDataONE Tasks
Redmine Member Nodes - Task #8723 (New): tDAR: Implemented IP Whitelisting on tDAR systems / Impacts to r...https://redmine.dataone.org/issues/87232018-10-02T16:51:19ZMonica Ihliemail@monicaihli.com
<p>tdar has implemented IP whitelisting on their member node. Requests from IP addresses not whitelisted will be refused. Was provided CN IPs for production. The reports that ping Tdar MN for up status will fail unless it happens to be executed from an IP that can be provided. This may or may not be considered a big enough issue to do something about. No harm is actually being done as long as the CNs can get in and do their business. </p>
Search UI - Task #8576 (New): Remove Code Changes Specific to Appearance of Data Citation for PAN...https://redmine.dataone.org/issues/85762018-04-30T13:29:25ZMonica Ihliemail@monicaihli.com
<p>Should be completed after a broader strategy for customizing appearance of data citation, particularly with regard to which identifiers display, has been implemented.</p>
Search UI - Task #8575 (Closed): Make Code Adjustments to Display SID only in PANGAEA data citation.https://redmine.dataone.org/issues/85752018-04-30T13:27:40ZMonica Ihliemail@monicaihli.comSearch UI - Story #8574 (New): PANGAEA Temporary Fix: SID only in Data Citationhttps://redmine.dataone.org/issues/85742018-04-30T13:26:15ZMonica Ihliemail@monicaihli.com
<p>Adjust appearance of data citation in the case of formatid <a href="http://www.isotc211.org/2005/gmd-pangaea">http://www.isotc211.org/2005/gmd-pangaea</a> such that the SID alone appears in the data citation and not the PID. This is intended as a temporary fix to be in place only while a longer term strategy for customizing appearances of data citations is designed and implemented. Once that longer term strategy is in place, whatever temporary code level changes were implemented to accommodate PANGAEA should be removed.</p>
Testing 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>
Python GMN - Story #8371 (Closed): Develop Ability to Host Multiple Nodes from a Single Installat...https://redmine.dataone.org/issues/83712018-02-19T16:15:19ZMonica Ihliemail@monicaihli.com
<p><strong>Problem Statement:</strong></p>
<p>For some business models, a single organization may host and otherwise manage content for multiple source repositories or producers of science data. Examples might include a consortial or aggregator arrangement. In such cases it may be most appropriate for each of the source data providers to maintain their respective identities, while still having their participation in DataONE managed by the central entity. This means that a single entity should be able to host and manage multiple DataONE member nodes. The problem is that GMN presently only supports hosting a single Member Node per installation of the web app. The only way to meet the above stated needs is for the one entity to setup multiple web servers, creating a situation of additional costs and barriers. </p>
<p><strong>Proposed Solution:</strong></p>
<p>The solution is to modify GMN so that multiple member nodes can be hosted from a single installation of the web application.</p>
<p>Notes on the basic strategy is as follows:<br>
* The CN recognize and interact with MN through the node's baseURL. <br>
* A BaseURL and all of the content on the node is tied to the Node doc. GMN needs to be able to serve up different content for different baseURLs.<br>
* This would be facilitated through Apache's ability to serve content for multiple hosts from a single web server.<br>
* WRT application itself, would be implemented with vendor specific extension that allows the create() call to add a field specifying which Node doc goes with the particular object.<br>
* Also adds a layer of abstraction to the database.</p>
Testing MN Management - Task #8356 (New): Formal Announcementhttps://redmine.dataone.org/issues/83562018-02-08T15:28:14ZMonica Ihliemail@monicaihli.com
<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) <a href="https://www.dataone.org/public_relations#logos">https://www.dataone.org/public_relations#logos</a></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}<br>
* 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>)<br>
* MN social media handles</p>
Testing MN Management - Task #8344 (New): MN Communicationshttps://redmine.dataone.org/issues/83442018-02-08T15:28:10ZMonica Ihliemail@monicaihli.com
<ul>
<li>Complete MNDeployment ticket properties fields</li>
<li>Upload MN logo to GitHub (<a href="https://github.com/DataONEorg/member-node-info/tree/master/production/graphics">https://github.com/DataONEorg/member-node-info/tree/master/production/graphics</a>) & add link to “Logo URL”</li>
<li>Add POCs to mnforum Google Group</li>
<li>Send MN communication channels to MN (<a href="https://redmine.dataone.org/projects/mns/wiki/MN_communication_channels">https://redmine.dataone.org/projects/mns/wiki/MN_communication_channels</a>)</li>
<li>Business requirements confirmed:
<ul>
<li>legal?</li>
<li>licensing?</li>
<li>data sharing restrictions / privacy concerns?</li>
</ul></li>
</ul>
Member Nodes - Task #8306 (Closed): Upgrade NKN GMNhttps://redmine.dataone.org/issues/83062018-02-06T18:35:13ZMonica Ihliemail@monicaihli.com
<p>Currently on a version 1.2.10 of GMN. </p>
<ul>
<li>Establish contact and make arrangements to upgrade to current GMN (2.4.1). </li>
<li>Node's baseURL is <a href="https://dataone.northwestknowledge.net/mn/v1">https://dataone.northwestknowledge.net/mn/v1</a></li>
<li>Can update contact in node document while upgrading. </li>
</ul>
Member Nodes - Story #8225 (In Progress): Customize Indexing & View for gmd-pangaeahttps://redmine.dataone.org/issues/82252017-12-06T19:41:28ZMonica Ihliemail@monicaihli.com
<p>An example metadata record: <a href="http://cn-sandbox.test.dataone.org/cn/v2/object/doi:10.1594/PANGAEA.877809_.201711172109">http://cn-sandbox.test.dataone.org/cn/v2/object/doi:10.1594/PANGAEA.877809_.201711172109</a></p>
<p>This record in the search interface on sandbox: <a href="https://search-sandbox.test.dataone.org/#view/doi:10.1594/PANGAEA.877809_.201711172109">https://search-sandbox.test.dataone.org/#view/doi:10.1594/PANGAEA.877809_.201711172109</a></p>
<p>Currently, alternate access point is pulling the link from:<br>
/ns0:MD_Metadata/ns0:distributionInfo[ 1 ]/ns0:MD_Distribution[ 1 ]/ns0:transferOptions[ 1 ]/ns0:MD_DigitalTransferOptions[ 1 ]/ns0:onLine[ 1 ]/ns0:CI_OnlineResource[ 1 ]/ns0:linkage[ 1 ]/ns0:URL[ 1 ]</p>
<p>However, Pangaea wishes users to be directed towards a landing page where they are able to obtain METADATA in multiple formats, found in:<br>
/ns0:MD_Metadata/ns0:dataSetURI[ 1 ]/ns2:CharacterString[ 1 ]</p>
<p>The landing page for this example: <a href="https://doi.pangaea.de/10.1594/PANGAEA.877809">https://doi.pangaea.de/10.1594/PANGAEA.877809</a></p>
Member Nodes - Support #8021 (Closed): GRIIDC - Setting up a Test Server and Interested in using ...https://redmine.dataone.org/issues/80212017-02-15T18:11:14ZMonica Ihliemail@monicaihli.com
<p>Joe at GRIIDC is interested in creating a test environment. Their local system is undergoing changes, and a test server would be helpful for ensuring continued harmony between GRIIDC and DataONE systems. Joe also recognizes setting up a test server as an opportunity to test upgrading to GMN v2.</p>
<p><em>General strategy for proceeding:</em></p>
<ul>
<li>Reactivate the DataONE configuration for a previously setup test server.</li>
<li>This means that Joe can recycle existing certificates, settings.py file, etc as these are already setup to work on the DataONE end.</li>
<li>Once the machine is setup, Joe will run a practice upgrade from GMN v1 the test server to GMN v2.</li>
<li>Thoroughly test the GMN v2 instance.</li>
<li>Upgrade the production server to GMN v2 when satisfied with testing.</li>
<li>The test server will continue to exist even after production is upgraded, in order to fulfill the need for a continually available test environment to ensure that GRIIDC system changes outside of DataONE do not cause unexpected consequences.</li>
</ul>
<p><em>Some notes on testing:</em><br>
Any new adjustments to scripts or the adapter do not require immediately being actively connected to the CN for testing. The preferred approach would be to begin with testing the integration of the repository and GMNv2 via adapter in the member node's local environment before extending testing to include synchronization with the Stage CN. As a standalone test instance which has not been connected to CN yet, it is without consequence to wipe and start over as needed.</p>
<p><em>Next Steps:</em><br>
The GRIIDC test setup in DataONE's stage environment is currently set to down, which means the CN are not attempting to communicate with the test server. When Joe has his machine setup, he will attempt the upgrade. DataONE will continue to provide support throughout this process as needed.</p>
Member Nodes - Support #8017 (New): NCEI - Implement GMN for replicating Arctic Data Center Datahttps://redmine.dataone.org/issues/80172017-02-13T20:35:12ZMonica Ihliemail@monicaihli.com
<p><em>New Additional Technical Contact:</em> <br>
Xiaoyan - Working at NOAA NCEI facility with Sheekela, Ken.</p>
<p><em>Objectives:</em><br>
* Upgrade NCEI from Tier 1 to Tier 4, in order to fulfill replication partnshership with Arctic Data Center.<br>
* Moving GMN hosted by DataONE to hosting by NCEI.<br>
* Interested in further exploring implementation of DataONE API in current NCEI system.</p>