DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2018-02-13T20:17:25ZDataONE Tasks
Redmine CN REST - Story #8364 (In Progress): Ensure portal uses correct X509 certificateshttps://redmine.dataone.org/issues/83642018-02-13T20:17:25ZChris Jonescjones@nceas.ucsb.edu
<p>We've run into issues where after an upgrade of the <code>dataone-cn-portal</code> package on the CNs, the properties pointing to the public certificate and private key are incorrectly pointing to the old GeoTrust wildcard files rather than the new Lets Encrypt files:<br>
<br>
cn.server.publiccert.filename=/etc/ssl/certs/<em>.test.dataone.org.crt<br>
cn.server.privatekey.filename=/etc/ssl/private/</em>.test.dataone.org.key</p>
<p>These should be (in STAGE):</p>
<p>/etc/letsencrypt/live/cn-stage.test.dataone.org/cert.pem<br>
/etc/letsencrypt/live/cn-stage.test.dataone.org/privkey.pem</p>
<p>The issue might be that these are not being set correctly during the <code>postinst</code> script run. Jing pointed out that these values are taken from the debconf database settings that get set when <code>dataon-cn-os-core</code> is installed. So although the <code>postinst</code> script might be setting the correct values, the old cached values might still be in memory in the debconf database. If so, we'll need to clear those values during installations and upgrades.</p>
<p>Also, knowing where to look for these configuration settings can be challenging. These are referenced from <code>/var/lib/tomcat7/webapps/portal/WEB-INF/portal.properties</code>. These settings should be consolidated into <code>/etc/dataone/portal/portal.properties</code> so they also don't get blown away on war file upgrades in Tomcat.</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 #8227 (In Progress): ExceptionHandler regurgitates long html pages into th...https://redmine.dataone.org/issues/82272017-12-13T21:19:23ZRob Nahfrnahf@epscor.unm.edu
<p>While useful to know what was returned in the error response when it was not the correct response, HTML pages can be verbose and include excessive markup that's not useful. Especially when a GMN MN is in debugging mode and there is a systematic error being returned (like during an authentication issue), these logged html pages can end up being 75% of the log files, and cause meaningful log lines from scrolling off the end of the log rotation.</p>
<p>An option should be provided to limit the amount of characters being returned in the ServiceFailure.</p>
<p>Options are to:<br>
1. eliminate the message body altogether<br>
2. truncate the message body<br>
3. only print the visible parts of the HTML (remove and elements)<br>
4. combination of 2 & 3</p>
<p>since a new feature, develop in trunk.</p>
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>
Infrastructure - Story #8155 (In Progress): Ensure GMN fully supports the Package APIhttps://redmine.dataone.org/issues/81552017-08-01T16:25:32ZDave Vieglaisdave.vieglais@gmail.com
<p>The package API </p>
<p><a href="https://releases.dataone.org/online/api-documentation-v2.0/apis/MN_APIs.html#MNPackage.getPackage">https://releases.dataone.org/online/api-documentation-v2.0/apis/MN_APIs.html#MNPackage.getPackage</a></p>
<p>is a convenience method for clients to download a complete data package in single call. The result is a ZIP file in the BagIt format</p>
<p>The goal of this story is to fully implement the Package API on GMN.</p>
Infrastructure - Story #8081 (In Progress): develop federated broker configuration for indexinghttps://redmine.dataone.org/issues/80812017-04-24T22:52:34ZRob Nahfrnahf@epscor.unm.eduInfrastructure - 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 #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>
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>
Java Client - Story #3666 (In Progress): D1Client.listUpdateHistory() needs to handle changing ac...https://redmine.dataone.org/issues/36662013-03-15T22:51:23ZRob Nahfrnahf@epscor.unm.edu
<p>the current D1Client.listUpdateHistory() method needs to gracefully handle the situation where a NotAuthorized request is returned. the ObsoletesChain client class may need to be refactored to allow for this exception to be held so it can notify the user where appropriate.</p>
<p>Ostensibly, with a NotAuthorized, the user will not have access to either the tail or head of the chain, so can't return the head or tail, depending on how access changes.</p>
Infrastructure - Story #3591 (In Progress): Content consistency checks for new member nodeshttps://redmine.dataone.org/issues/35912013-02-18T23:24:34ZRob Nahfrnahf@epscor.unm.edu
<p>Want to be able to detect systematic content errors for new Member nodes:<br>
1) systemMetadata is parseable - existing getSystemMetadata() test should fail when it can't deserialize the systemMetadata, yes?<br>
2) resourceMaps are parseable - pull a resourceMap listObjects(formatId=, use ResourceMapFactory to deserialize <br>
3) checksum stability - content should have the same checksum every time it is pulled.</p>
Infrastructure - Story #725 (In Progress): Create Authentication and Access control design specif...https://redmine.dataone.org/issues/7252010-08-02T21:42:24ZChad Berkleyberkley@nceas.ucsb.edu
<p>The metacat <a class="wiki-page new" href="https://redmine.dataone.org/projects/d1/wiki/CrudService">CrudService</a> class contains methods for authentication and access control changes that are not part of the original D1 Crud specification. These services need to be decided on at a higher level and described in the specification so that they can be made to work with any D1 node, not just metacat.</p>