Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-02-21T23:38:01ZEcoinformatics Redmine
Redmine Bug #5873 (Resolved): Change [invisible] Login button to hyperlink buttonhttps://projects.ecoinformatics.org/ecoinfo/issues/58732013-02-21T23:38:01Zben leinfelderleinfelder@nceas.ucsb.edu
<p>In Windows (7) the "Login" button only shows the text and no border or button-looking outline. Since we use a hyperlink button for the "Logout of network" text, we should just change to the hyperlink version so that it is consistent and we know it renders properly.</p> Bug #5864 (Resolved): ECP login causes new DN so user's can't see their datahttps://projects.ecoinformatics.org/ecoinfo/issues/58642013-02-13T02:25:06ZMatt Jonesjones@nceas.ucsb.edu
<p>Logging into the new version of Morpho using ECP has two negative side effects that need to be resolved.</p>
<p>1) The ECP login uses the ou=Account subtree, so my password changed and most users will not realize this, and thus will not be able to find their previously saved data packages</p>
<p>2) the DN for logged in users changes to the CILogon DN, which also causes their previously created data to not show up. Even once the user's old knb id is mapped to their new CILogon DN, its not clear if their data will be accessible in Morpho.</p> Bug #5863 (Resolved): After deleting the newest version of a package locally, the search and open...https://projects.ecoinformatics.org/ecoinfo/issues/58632013-02-13T02:20:00ZJing Taotao@nceas.ucsb.edu
<p>Here are steps:</p>
<p>1. create a data package and save it.<br />2. update the title and save it again.<br />3. delete the package.<br />4. search and open couldn't find the previous version.</p>
<p>I know for the dataone network, there is no way to go back the previous version by search.</p>
<p>But for the local copy, maybe we can offer the user a way in the search.</p> Bug #5857 (Resolved): A package just created by the new package wizard has an obsoletes element i...https://projects.ecoinformatics.org/ecoinfo/issues/58572013-02-12T05:20:13ZJing Taotao@nceas.ucsb.edu
<p>I just created a data package by using the new data package wizard. When I checked the system metadata, it has a obsoletes element. However, it should not have one.</p> Bug #5852 (Resolved): Allow a mix of MN URL and MN Node Name values in the preferences screenhttps://projects.ecoinformatics.org/ecoinfo/issues/58522013-02-06T05:31:40Zben leinfelderleinfelder@nceas.ucsb.edu
<p>I think we can be more clever with mixing and matching the selection combobox with MNodeSelectionObjects (listed from the CN) and String URLs (manually entered). We only save the MN URL in the configuration file, so we'd rely on matching that up with the list from the CN. We can't store nodeId since an unregistered MN will not have one and we really do need the URL, not just a random [unregistered] nodeId in the Morpho config.</p> Bug #5831 (Resolved): Address "inherited" access policy on data entitieshttps://projects.ecoinformatics.org/ecoinfo/issues/58312013-01-30T00:08:44Zben leinfelderleinfelder@nceas.ucsb.edu
<p>There is an "inherit from metadata" choice when editing data access policy. This worked when we knew Metacat was handling the package and would enforce the EML rules for everything in the datapackage. But DataONE doesn't have the same notion -- all the obejcts fend for themselves using whatever SM.AccessPolicy they have.</p>
<p>My inclination is to remove this option but that raises some concerns:<br />-what should the default policy be for data files? (I say private)<br />-would it be more convenient to let people duplicate their sciMeta access rules to the sciData objects?</p> Bug #5827 (Resolved): Changes to dataTable data are not saved to networkhttps://projects.ecoinformatics.org/ecoinfo/issues/58272013-01-29T22:52:59Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Follow these steps to reproduce:<br />1. New DP wizard<br />2. Import new tabular data file<br />3. Save to network (only)<br />4. Edit data (add a row)<br />5. Save to network again.<br />Note that the data file changes are gone, even though a new id is being used for it.</p>
<p>If you also save locally, the changes are persisted as expected.</p> Bug #5825 (Resolved): Call CN.setReplicationPolicy() when editing replication policyhttps://projects.ecoinformatics.org/ecoinfo/issues/58252013-01-25T22:12:13Zben leinfelderleinfelder@nceas.ucsb.edu
<p>This should act the same as the access policy edits. For network packages, we call the CN.setReplicationPolicy() and only save the SM locally if that was successful. Otherwise we tell the user to wait for the CN to synch with the MN.<br />If the package is local-only, then we can just save the SM locally.</p> Bug #5824 (Resolved): Call CN.setAccessPolicy() when editing accesshttps://projects.ecoinformatics.org/ecoinfo/issues/58242013-01-25T22:08:19Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Currently Morpho edits the SystemMetadata.AccessPolicy for an EML and/or data file and uploads a new version of those during a save. Instead we should be calling the CN to set the accessPolicy for a package that has been saved to the network.</p>
<p>Here are some ideas:<br />-For local-only packages, just save the SM accessPolicy change to disk when user hits "ok" after editing the access rules.<br />-For network/both packages, attempt to save to the Network, if that fails, alert user to try again later. Do not save the change locally either. User will have to wait until the CN synchs with the MN to get the SM.accessPolicy updated.</p> Bug #5799 (New): publish using DOI featurehttps://projects.ecoinformatics.org/ecoinfo/issues/57992013-01-23T06:48:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Morpho currently uses local identifiers that are not necessarily globally unique for data objects and metadata documents. Users should be able to publish their data packages and associated objects with a digital object identifier that is universally recognized as a citable object. Towards this end, add a feature to morpho that allows a user to choose a particular version of a data set to be 'published' with a DOI. This effectively means that a new version of all associated objects will be created, each with a minted, unique DOI that can be used to cite the object. Morpho will undertake the following steps when a user selects 'Publish using Digital Object Identifiers (DOIs)' as an action:</p>
<p>1) Ensure that all objects in the current package are saved and valid<br />2) For each data object, metadata object, and package ORE in the package<br /> a) Call the MN to reserve a DOI for that object, if it hasn't already been assigned a DOI<br /> -- if DOI minting errors occur, fail with explanation to user<br /> b) Update all metadata and package pointers to use these new DOIs to reference data, etc.<br /> c) save a new version of the object using update() to replace the old version with the DOI-named version</p>
<p>Note that when the receiving MN receives a create() or update() call that uses a DOI as its identifier, it will ensure that the user has the right to mint that DOI (either it is unreserved or reserved by that user), and then it will register that identifier with the EZID DOI registry service with appropriate metadata based on the DataCite standards.</p>
<p>The GUI for publishing with a DOI could either be part of the current Save dialog when users are saving to the network, or might be a separate menu action that is independent of the Save dialog.</p> Bug #5795 (Resolved): Centralize identifier conflict resolution during save LOCAL+NETWORKhttps://projects.ecoinformatics.org/ecoinfo/issues/57952013-01-19T00:17:37Zben leinfelderleinfelder@nceas.ucsb.edu
<p>After splitting the identifier conflict resolution code into separate Local and Network classes, it turns out this can be problematic for keeping the two copies in sync (see related bug <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: In some situation, morpho uses the same frame to display two data package with different ids (one... (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/5792">#5792</a>).</p>
<p>We should use a single class to check for existing identifiers in both target locations and choose an identifier that is valid in both locations before proceeding with the save in either location.</p> Bug #5794 (Resolved): Cannot add only Genus with Common Namehttps://projects.ecoinformatics.org/ecoinfo/issues/57942013-01-18T21:45:15Zben leinfelderleinfelder@nceas.ucsb.edu
<p>In the taxonomic import screen, Sarah Clark tried to add a Genus+Common Name without including a corresponding Species+name entry and Morpho did not honor that. Instead it moved Common Name into the Genus name field.</p> Bug #5740 (Resolved): Add MN selection to Morpho preferences screenhttps://projects.ecoinformatics.org/ecoinfo/issues/57402012-11-20T20:04:40Zben leinfelderleinfelder@nceas.ucsb.edu
<p>For now we have a configured MN URL in the config.xml. This works, but does not tell use which environment the client or mN is part of. <br />We should also design the preferences to use:<br />-CN URL + MN reference (to determine the MN URL)<br />or<br />-MN URL alone</p> Bug #5128 (Resolved): access list does not show all dns in the LTER LDAP treehttps://projects.ecoinformatics.org/ecoinfo/issues/51282010-08-04T20:32:06ZMargaret O'Brienmob@msi.ucsb.edu
<p>When adding access rules for individuals, not all the people in the LTER tree are available. It appears that missing folks are the relatively recent additions, eg, since about 2008, but I cannot be sure of that.<br />this might be related to bug 3596.</p> Bug #4418 (Resolved): "about" box displays incorrect version numberhttps://projects.ecoinformatics.org/ecoinfo/issues/44182009-09-25T18:51:57ZWill Tyburczywilltyb@uchicago.edu
<p>When you go to "morpho > About morpho" from the computer menu bar, the version displayed is 1.0</p>