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 #8355 (New): Mutual Acceptancehttps://redmine.dataone.org/issues/83552018-02-08T15:28:14ZMonica Ihliemail@monicaihli.com
<p>Verify that the content is synchronizing correctly and the search results appear as expected. Member node approves</p>
Testing MN Management - Task #8354 (New): Register in Productionhttps://redmine.dataone.org/issues/83542018-02-08T15:28:13ZMonica Ihliemail@monicaihli.com
<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>
Infrastructure - Feature #8107 (New): Improved Node Synchronization Feedback - Leveraging MNRead....https://redmine.dataone.org/issues/81072017-06-06T17:30:43ZMonica Ihliemail@monicaihli.com
<p>MN Operators would benefit from clearer feedback from the CN to be aware of when syncs fail for a PID.</p>
<ul>
<li>GMN - currently logs MNRead.synchronizationFailed() requests received as part of the regular GMN logs.</li>
<li>Metacat - also currently just logs MNRead.synchronizationFailed() requests as part of regular logs.</li>
<li>One solution might be to simply log these failures in a separate file to make it easier for node operators to identify when something fails to sync. </li>
</ul>
<p>Additionally, we should confirm what kind of information is getting sent back to MNs with MNRead.synchronizationFailed().</p>
Infrastructure - Bug #8106 (Testing): Difficulty Distinguishing Between Different Kinds of Failed...https://redmine.dataone.org/issues/81062017-06-06T17:25:55ZMonica Ihliemail@monicaihli.com
<p>Attached are two examples of parsed log files describing PIDs which failed to sync. The log files contain excerpts from different areas of logs including Metacat and d1-synchronization. Of particular interest is the Synchronization logs which in both cases report "Not Found", but in response to different conditions. In the one case, the sync failed because the CN was given a manual synchronization request but passed a PID that it could not locate on the MN (the node operator had attempted to escape PID characters and it was unneeded in this case). In the second case, the CN recognized a legitimate PID but the bytes of the object were missing. </p>
<p>Some differentiation in the error messages could be more helpful in identifying what went wrong during a sync. </p>
Infrastructure - Bug #8024 (Rejected): Submitter Being Checked During SeriesId Validation within ...https://redmine.dataone.org/issues/80242017-02-20T21:59:36ZMonica Ihliemail@monicaihli.com
<p>Submitter is incorrectly being checked for change rights within seriesId validation during synchronization. </p>
<p>An example of an error logged in relation to this issue:</p>
<p><em>cn-synchronization.log.1:[ERROR] 2017-02-16 21:54:43,986 (V2TransferObjectTask:processTask:416) Task-urn:node:TDAR-doi:10.6067:XCV8FN183H_format=d1rem1468436505149 - NotAuthorized to claim the seriesId - NotAuthorized - Submitter does not have CHANGE rights on the SeriesId as determined by the current head of the Sid collection, whose pid is: org.dataone.service.types.v1.Identifier@2cf9dd65</em></p>
<p>The system metadata for the member node version of the affected object referenced in this log entry has been attached as an example. </p>