Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362015-03-27T21:59:28ZEcoinformatics Redmine
Redmine Bug #6702 (New): Import metadata indexing optionhttps://projects.ecoinformatics.org/ecoinfo/issues/67022015-03-27T21:59:28ZJessica Couturecouture@nceas.ucsb.edu
<p>When metadata is added to a package from an external file, Morpho creates a new identifier for it rather than incrementing the existing identifier. It would be great to have the option to either add the metadata to the existing series or create a new identifier when the file is brought in.</p> Bug #6701 (New): Entity descriptions can't be added outside wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/67012015-03-27T21:56:52ZJessica Couturecouture@nceas.ucsb.edu
<p>I was trying to add entity descriptions after my tables had been imported and found that there is no way to go back and access this. Can this function be added so that this can be edited outside the initial data wizard has been closed?</p> Bug #6700 (New): Pub date fieldhttps://projects.ecoinformatics.org/ecoinfo/issues/67002015-03-27T21:54:54ZJessica Couturecouture@nceas.ucsb.edu
<p>The publication data defaults to the current date and there is no way to manually set this in Morpho. Can we have one added for datasets that had been published in the past?</p> Bug #6589 (New): common name in taxonomic coveragehttps://projects.ecoinformatics.org/ecoinfo/issues/65892014-08-28T20:02:32ZJessica Couturecouture@nceas.ucsb.edu
<p>When inputting taxonomic coverage manually there is an option to put common name but when assigning columns of names from a table, only the scientific classes are available. It would be helpful to be able to add common names from a table too.</p> Bug #6112 (New): Use .morpho when we release the morphohttps://projects.ecoinformatics.org/ecoinfo/issues/61122013-10-01T23:53:37ZJing Taotao@nceas.ucsb.edu
<p>Currently the default morpho home is .morpho2. It is great for users to test morpho without change the file structure. But the real release will use .morpho as the default directory.</p> Bug #6042 (New): Cannot save/synchronize Morpho data package to the networkhttps://projects.ecoinformatics.org/ecoinfo/issues/60422013-08-01T01:55:54Zunset unsetkmwolf@ucdavis.edu
<p>Hi everyone,</p>
<p>I have saved a data package and completed all fields. I have tried saving it to the network (while logged in), and synchronizing, and both give me multiple errors, starting with this one:</p>
<p>Some problem with saving data files has occurred! <?xml version = "1.0"?> <error> Permission denied for upload </error></p>
<p>I am sure this is some simple thing that I am not understanding as a new user, but I would certainly appreciate some guidance. Thanks!</p> Bug #6010 (New): Windows 8 installation errorhttps://projects.ecoinformatics.org/ecoinfo/issues/60102013-07-01T16:19:59ZSarah Clarksclark@nceas.ucsb.edu
<p>A user trying to install Morpho in Windows 8 received a configuration error, Matt described it as an issue with write access to the installation directory.</p> Bug #5887 (New): Handle the query result set which contains the revision chains of documentshttps://projects.ecoinformatics.org/ecoinfo/issues/58872013-03-07T23:48:28ZJing Taotao@nceas.ucsb.edu
<p>Morpho network query now experiences a performance issue because the merge of the network and local search results.</p>
<p>During the merge, morpho needs to make lots of calls the DataONE MN to get the revision chains.</p>
<p>The proposed solution is to add the revision chain for each eml document to the result set. This can avoid lots of network traffic.</p>
<p>So morpho needs to handle the new result set.</p> Bug #5872 (New): Irregularities with access controlhttps://projects.ecoinformatics.org/ecoinfo/issues/58722013-02-21T14:17:28Zunknown unknowneva-maria.gerstner@senckenberg.de
<p>Dear Metacat and Morpho developers,</p>
<p>I am using metacat 2.0.3 and morpho 1.10.0. There seems to be a problem with setting the access rights for other entity data or table data added to a metadata package. When I add such extra data, grant certain access rights and upload everything to the metacat server, sometimes (I haven't figured out exactly under what circumstances) there is no access to the extra data except for the owner of the data. By looking into the postgresql table xml_access I found out that the entries for the extra data were missing in these cases. The EML itself seems to be ok though.</p>
<p>For example, when I have data.1.1 as metadata package and data.2.1 and data.3.1 as extra data to this package, sometimes there is no access to data.2.1 and/or data.3.1 except for the owner of the data.</p>
<p>I would appreciate any advice how to fix or circumvent this problem.</p>
<p>Sincerely,<br />Eva-Maria Gerstner</p> Bug #5848 (New): Ensure Morpho can edit EML contributed by DataUphttps://projects.ecoinformatics.org/ecoinfo/issues/58482013-02-06T01:31:26Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Tried to open network EML 2.1.1 contributed by DataUp tool:<br /><a class="external" href="https://oneshare.unm.edu/knb/d1/mn/object/ark:/90135/q13j39xf/4/mrt-eml.xml">https://oneshare.unm.edu/knb/d1/mn/object/ark:/90135/q13j39xf/4/mrt-eml.xml</a><br />Got a few errors while it tried to parse the package (butterfly still flapping):<br />physicalList is null!<br />physicalList is null!<br />physicalList is null!<br />physicalList is null!<br />Invalid Id</p> Bug #5845 (New): illegible fonts when remoting via Xhttps://projects.ecoinformatics.org/ecoinfo/issues/58452013-02-02T22:17:18ZTom RocheTom_Roche@pobox.com
<p>I have a ~1.1-GB dataset on a cluster on which I work. I have morpho-1.10.0-linux on my debian laptop, which works fine, but I don't want to copy the data locally and then upload it to KNB. So I tried to install morpho on the cluster (in my home space) by running</p>
<p>$ URI=http://knb.ecoinformatics.org/software/dist/morpho-1.10.0-linux.jar<br />$ FN="$(basename ${URI%%\?*})" ; DIR="$HOME/bin" ; FN=$(echo ${FN} | sed <del>e 's/ /_/g') ; FN=$(echo ${FN} | sed -e 's/%20/_/g') ; mkdir -p ${DIR} ; FP="${DIR}/${FN}" ; curl -C - -o "${FP}" "${URI}" <br /> % Total % Received % Xferd Average Speed Time Time Time Current<br /> Dload Upload Total Spent Left Speed<br />100 83.3M 100 83.3M 0 0 2392k 0 0:00:35 0:00:35 -</del>:--:-- 2455k<br />$ java -jar ${FN}</p>
<p>in a (bash) shell on the cluster, accessed via ssh from, and X forwarded to, my linux laptop. Upon doing so I get an illegible dialog: see the attached screenshot.</p> Bug #5809 (New): Default save behavior to always include local storehttps://projects.ecoinformatics.org/ecoinfo/issues/58092013-01-24T19:22:17Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Currently you can opt to save your datapackage changes to either LOCAL, NETWORK, or BOTH. This means you can make changes to a package then opt to save them only to the NETWORK. This can leave your local store a version behind and I don't undersand the usecase for that.</p>
<p>I am proposing that we <em>always</em> save changes locally (if local does not already have the latest version).</p>
<p>I started thinking about this because of a related bug that displayed different local and network revisions simultaneously (<a class="issue tracker-1 status-2 priority-2 priority-default" title="Bug: Local and Network revisions show at same time in search results (In Progress)" href="https://projects.ecoinformatics.org/ecoinfo/issues/5805">#5805</a>). I think we should still try to address that bug, but I'm not exactly sure how to guarantee it will not continue to be a problem especially if we maintain distinct revision histories for local and network content. (This may qualify as yet another bug for discussion).</p> Bug #5780 (New): DataONE object listing doesn't show the updated data package by morphohttps://projects.ecoinformatics.org/ecoinfo/issues/57802013-01-15T00:55:19ZJing Taotao@nceas.ucsb.edu
<p>I created a data package by the morpho new data package wizard. Then i saved it to the DataONE and got the id tao.284.</p>
<p>I updated the title by morpho and saved it to the DataONE again. This time it gave me the id: tao.2013011416170149711. It is much longer than it was.</p>
<p>Thought I can access it by:<br /><a class="external" href="https://mn-demo-5.test.dataone.org/knb/d1/mn/v1/meta/tao.2013011416170149711">https://mn-demo-5.test.dataone.org/knb/d1/mn/v1/meta/tao.2013011416170149711</a></p>
<p>But the list of object doesn't include it:<br /><a class="external" href="https://mn-demo-5.test.dataone.org/knb/d1/mn/v1/object">https://mn-demo-5.test.dataone.org/knb/d1/mn/v1/object</a></p>
<p>It includes the previous version - tao.284.</p>
<p>I also search the metacat and the result doesn't include the newer version. The metacat search result did show up the previous version tao.284 before I updated it.</p> Bug #5774 (New): Only save the system metadata to local and network if users only modify the syst...https://projects.ecoinformatics.org/ecoinfo/issues/57742013-01-10T00:56:48ZJing Taotao@nceas.ucsb.edu
<p>This issue has come from modifying the access rules for the entities.</p>
<p>After the user modify the access rules for an entity, the system metadata of the entity was modified; but the data was not. Ideally we only serialize the system metadata to the local and the dataone network but keep the data untouched.</p>
<p>For "save locally", it is not hard. But for "Save network", there are some issues. First the MN doesn't have the setSystemMetadata API. Second, there is a delay to get the data in CNode.</p>
<p>Now we just had a temporary solution - label the entity dirty even though there is only change in the system metadata. We need a better solution.</p>
<p>This issue also apply the the Replication Policy as well.</p> Bug #5766 (New): Include data identifier in EML (rather than ecogrid:// URL)https://projects.ecoinformatics.org/ecoinfo/issues/57662012-12-12T00:07:13Zben leinfelderleinfelder@nceas.ucsb.edu
<p>We use ecogrid:// URLs in the EML distribution section for data files. But we should also be writing the plain identifier into a standard place in the EML so that we can match the data Identifier from the ORE to the EML</p>