DataONE Tasks: Issueshttps://redmine.dataone.org/https://redmine.dataone.org/favicon.ico2019-05-01T14:00:51ZDataONE Tasks
Redmine Infrastructure - Story #8791 (New): Complete deprecation of ONEMercury interfacehttps://redmine.dataone.org/issues/87912019-05-01T14:00:51ZDave Vieglaisdave.vieglais@gmail.com
<p>ONEMercury is still deployed on CNs and there are a number of links on the DataONE web site that link to the ONEMercury UI.</p>
<p>On production systems, the page: </p>
<p><a href="https://cn.dataone.org/onemercury/">https://cn.dataone.org/onemercury/</a> </p>
<p>should redirect to:</p>
<p><a href="https://search.dataone.org/">https://search.dataone.org/</a></p>
<p>It may be useful to have an informational page that continues the redirect after a few seconds to help inform users of the change.</p>
Search 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>
Infrastructure - Story #8470 (New): Make the spring context of the d1_index_processor daemon more...https://redmine.dataone.org/issues/84702018-03-02T20:56:14ZJing Taotao@nceas.ucsb.edu
<p>In the IndexTaskProcessorDaemon class, which is the start point of d1-indexx-processor, the context is initialized from a file in the class path:</p>
<p><code>context = new ClassPathXmlApplicationContext("processor-daemon-context.xml");</code></p>
<p>The file, processor-daemon-context.xml, imports all the index sub-processor application files. This make very hard for us to add a new sub-processor since we have to rebuild a new jar file in order to include a new file. Instead, if we use the <code>FileSystemXmlApplicationContext</code> class and read the file path from a properties file, we can get more flexibility.</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 - Story #8352 (New): Move to Productionhttps://redmine.dataone.org/issues/83522018-02-08T15:28:13ZMonica Ihliemail@monicaihli.comTesting MN Management - Story #8347 (New): Testing & Developmenthttps://redmine.dataone.org/issues/83472018-02-08T15:28:11ZMonica Ihliemail@monicaihli.com
<p>Install or develop a functional member node to be registered to a non-production environment. </p>
Testing MN Management - Story #8343 (New): Planninghttps://redmine.dataone.org/issues/83432018-02-08T15:28:10ZMonica Ihliemail@monicaihli.com
<p>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>
Testing MN Management - Story #8340 (New): Discoveryhttps://redmine.dataone.org/issues/83402018-02-08T15:28:09ZMonica 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>
Infrastructure - Story #7807 (New): cn.synchronize should support synchronization failure correct...https://redmine.dataone.org/issues/78072016-05-13T16:56:25ZRob Nahfrnahf@epscor.unm.edu
<p>cn.synchronize(session, identifier) works well for its original purpose (supporting MN-driven system metadata updates, and MN-driven push synchronization), but doesn't seem to work for manual synchronization failure workflows. The main problem is that the request can only be made by the MN itself (using the MN client certificate). </p>
<p>As we envision a centralized dashboard for monitoring failed synchronization items, how do we address this situation? </p>
<p>The synchronization processing queue needs both the pid and a nodeId from where to retrieve the object. the NodeId is not specified directly in the method call, but gleaned from the session by a reverse lookup from the certificate. (It uses the first node found in the NodeList where the Node.subject field matches the certificate subject).</p>
<p>Should we allow node.contactSubjects into the algorithm?<br>
Should we add nodeId as a parameter?</p>
Python GMN - Story #7095 (New): Support HTTP redirect capability for GMN within the Vendor Specif...https://redmine.dataone.org/issues/70952015-05-12T16:20:39ZMark Servillamark.servilla@gmail.com
<p>GMN provides proxy capabilities to integrate existing content residing in a back-end data repository through its Vendor Specific Extension model. Only minimal support exists within the GMN-VSE model for HTTP redirects. Although the use of HTTP redirects is more of an exception within the the GMN-VSE model, it can provide a flexible mechanism for MNs who dynamically manage data and metadata objects.</p>
Infrastructure - Story #6543 (New): Support RIF-CS metadata standardhttps://redmine.dataone.org/issues/65432014-11-03T00:23:31ZBruce Wilsonbwilso27@utk.edu
<p>Broadly used in the australian ecoinformatics community. URL is <a href="http://www.ands.org.au/resource/rif-cs.html">http://www.ands.org.au/resource/rif-cs.html</a>. AEKOS is planning to work with EML initially, but RIF-CS is their native format. </p>
Infrastructure - Story #6069 (New): open ask.dataone.org sign-in to communityhttps://redmine.dataone.org/issues/60692014-08-22T16:45:27ZRob Nahfrnahf@epscor.unm.edu
<p>We are starting to get community involvement in questions asked on DataONE, but community members are not able to sign-in and post responses, I believe.</p>
<p>the solution is to open up the Askbot server to accept new members from the general community.</p>
Python Libraries - Story #5468 (New): Remove dead code from D1 Python stackhttps://redmine.dataone.org/issues/54682014-06-06T18:57:00ZRoger Dahldahl@unm.edu
<p><a href="https://pypi.python.org/pypi/vulture">https://pypi.python.org/pypi/vulture</a></p>
Infrastructure - Story #4091 (New): ESRI GeoPortal MN stackhttps://redmine.dataone.org/issues/40912013-10-15T13:36:56ZBruce Wilsonbwilso27@utk.edu
<p>The objective is to design, develop, and implement a MN Stack to integrate with the ESRI GeoPortal server (<a href="http://www.esri.com/software/arcgis/geoportal">http://www.esri.com/software/arcgis/geoportal</a>).</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>