DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-04-09T21:14:39ZDataONE Tasks
Redmine Member Nodes - Story #8535 (In Progress): Neotoma: Story: Discovery & Planninghttps://redmine.dataone.org/issues/85352018-04-09T21:14:39ZAmy Forresteraforres4@utk.edu
<p>Discovery: establish contact and build relationship with a potential new member node. Determine if DataONE and the repository are a good fit for one another and if the repository generally meets the requirements of DataONE member nodes. </p>
<p>Planning: If the repository and DataONE have agreed to proceed with deployment as a member node. Decisions will be made as to how to proceed with development. Node operators will receive training. </p>
<p>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>
<p><strong>Record initial communication here</strong></p>
Member Nodes - Story #8358 (In Progress): Discovery & Planning (CAFF)https://redmine.dataone.org/issues/83582018-02-12T16:25:06ZAmy Forresteraforres4@utk.edu
<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>
Infrastructure - Story #8038 (In Progress): connect logging output to a log analysis toolhttps://redmine.dataone.org/issues/80382017-03-07T20:42:15ZRob Nahfrnahf@epscor.unm.edu
<p>this would be part of a larger monitoring framework effort</p>
Infrastructure - Story #7920 (In Progress): migrate apache2 authorization rules from 2.2 conformi...https://redmine.dataone.org/issues/79202016-10-26T18:15:04ZRob Nahfrnahf@epscor.unm.edu
<p>Currently, our apache configs are using the 2.2 style, but we will have to upgrade at some point. </p>
<p>The access_compat module (under mods-enabled) is in place to allow us to use the old 2.2 conventions.</p>
Infrastructure - Story #7882 (In Progress): Tune CN logfile managementhttps://redmine.dataone.org/issues/78822016-09-09T20:13:07ZDave Vieglaisdave.vieglais@gmail.com
<p>There are many log files generated on the Coordinating Nodes which can make diagnostics challenging. Some logs also appear to be misconfigured or set to log at DEBUG level even on production systems, resulting in extremely verbose logs.</p>
<p>The goal of this activity is to streamline logging to make it easier to find useful information in the logs by reducing verbosity, consolidating where possible, and perhaps refining some log messages.</p>
Search UI - Story #7754 (In Progress): Support for XSL transform of various metadata formatshttps://redmine.dataone.org/issues/77542016-04-27T14:43:23ZDave Vieglaisdave.vieglais@gmail.com
<p>Currently the DCX and ISO metadata formats are being rendered in the view service using solr output rather than a transform of the XML metadata. This results in a less than satisfactory rendering.</p>
<p>Goal of this story is to implement XSLT for metadata formats that currently are relying on the solr only rendering.</p>
Infrastructure - Story #7716 (In Progress): How to facilitate resubmission of sync Failures?https://redmine.dataone.org/issues/77162016-04-12T18:51:35ZJing Taotao@nceas.ucsb.edu
<p>Currently, when CNs harvest objects from MNs, they only compare the last modified time stamp on the system metadata with the last harvest date. If the last modified stamp is earlier than the last harvest date, the object wouldn't be put on the synchronization queue.</p>
<p>This causes an issue: if the synchronization for this object failed in the previous synchornizations and the issue of the failure was corrected (e.g. a misconfiguration on the MN and the last modified time stamp should NOT be changed), the harvest will not pick up the object. We have to manually to either reset the harvest date, or submit a v2.CN.synchronize(PID,NodeID) in order to pick up the object.</p>
<p>MemberNode operators are not well versed in how to submit these requests, so some sort of monitoring and management tool for MemberNode operators (and DataONE administrators) is proposed to simplify this type of action.</p>
<p>We are thinking to persist the information for the failed objects on a database table -e.g. failedSynchronization and it contains:<br>
identifier, mn_id, last_failed_time, message. </p>
<p>Message can be separated to another table to use the foreign key.</p>
<p>Once we have the failure information, we can work on the monitoring and management tool.</p>
Infrastructure - Story #7407 (In Progress): object formats in the d1_common_java bootstrap list a...https://redmine.dataone.org/issues/74072015-10-05T22:43:57ZRob Nahfrnahf@epscor.unm.edu
<p>Mark reports that:</p>
<p>dcx is not in d1_common_java but in production</p>
<p>And the objectFormat also appears to list formats that are not supported science metadata formats? For example:</p>
<p><a href="http://dublincore.org/schemas/xmls/qdc/2008/02/11/simpledc.xsd">http://dublincore.org/schemas/xmls/qdc/2008/02/11/simpledc.xsd</a><br>
<a href="http://dublincore.org/schemas/xmls/qdc/2008/02/11/qualifieddc.xsd">http://dublincore.org/schemas/xmls/qdc/2008/02/11/qualifieddc.xsd</a></p>
<p>The list should be consistent with what is in production.</p>
Infrastructure - Story #7358 (In Progress): ContactSubject on NodeList must be valid D1 ldap entryhttps://redmine.dataone.org/issues/73582015-09-16T19:58:13ZRobert Waltz
<p>Before a CN can be started, LDAP must have an approved entry for Contact Subject.</p>
<p>Contact Subject has been defaulted to CN=Robert P Waltz A904,O=Google,C=US,DC=cilogon,DC=org on all of the CN entries in the node list.</p>
<p>Since Robert P Waltz is a developer and not an organizer or director, then the publicized contact on the CNs should be changed to reflect the organizational hierarchy.</p>
<p>The Contact Subject for the CNs should be the PI of the project, or at least, a Co-PI.</p>
<p>Also, The DN of this subject should be derived from the DataONE CA instead of cilogon.</p>
<p>Updating the existing systems should be trivial. The Ldap Entry for each CN node will be modified, and a new LDAP entry for the new Subject will need to be added.</p>
Python GMN - Story #7219 (In Progress): Upgrade Django version used by GMN, add better support fo...https://redmine.dataone.org/issues/72192015-06-16T14:56:59ZDave Vieglaisdave.vieglais@gmail.comOGC-Slender Node - Story #7151 (In Progress): Generate system metadata for contenthttps://redmine.dataone.org/issues/71512015-06-04T20:24:16ZDave Vieglaisdave.vieglais@gmail.com
<p>For the three types of content (resource, science meta, data), develop a mechanism to provide system metadata.</p>
OGC-Slender Node - Story #7149 (Testing): Implement mechanism to retrieve a list of objects avail...https://redmine.dataone.org/issues/71492015-06-04T20:20:47ZDave Vieglaisdave.vieglais@gmail.com
<p>Using Python, implement a tool that is able to retrieve a list of packages, and the objects that make up each package.</p>
OGC-Slender Node - Story #7146 (In Progress): Determine formatId for content retrievable from NOD...https://redmine.dataone.org/issues/71462015-06-04T20:15:08ZDave Vieglaisdave.vieglais@gmail.com
<p>In order to create system metadata for objects held by NODC, it is necessary to infer the appropriate formatId for each object.</p>
Infrastructure - Story #5141 (In Progress): Describe the mn.updateSystemMetadata behavior in use ...https://redmine.dataone.org/issues/51412014-04-28T21:10:49ZRob Nahfrnahf@epscor.unm.edu
<p>The behavior for the mn.updateSystemMetadata call is a bit cryptic in how it's supposed to be implemented.</p>
<p>The implication is that it should be asynchronous with interaction with the CN, but even metacat seems to be passing back exceptions from CN interaction. (There currently isn't another way for MNs to report errors from the CN) </p>
Infrastructure - Story #4188 (In Progress): dataone Exception definition and implementation requi...https://redmine.dataone.org/issues/41882013-11-27T21:34:20ZDave Vieglaisdave.vieglais@gmail.com
<p>The documentation describes the properties and serialization of DataONE exceptions:</p>
<p><a href="http://mule1.dataone.org/ArchitectureDocs-current/apis/Exceptions.html">http://mule1.dataone.org/ArchitectureDocs-current/apis/Exceptions.html</a></p>
<p>However, the definition in the schema:</p>
<p><a href="https://repository.dataone.org/software/cicore/tags/D1_SCHEMA_1_1_1/dataoneErrors.xsd">https://repository.dataone.org/software/cicore/tags/D1_SCHEMA_1_1_1/dataoneErrors.xsd</a></p>
<p>differs, and so presents an inconsistent reference for implementations.</p>
<p>The Java code appears to follow the documentation, however the python implementation uses the schema to generate exception messages, and so follows the schema definition.</p>
<p>The schema and python code need to be updated to reflect the description in the documentation. Also, all implementations of MN and client software need to be informed of the issue and how they may be impacted.</p>