Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362017-03-21T16:32:28ZEcoinformatics Redmine
Redmine Bug #7175 (New): The link for non-numeric attribute domains doesn't work on the exported eml filehttps://projects.ecoinformatics.org/ecoinfo/issues/71752017-03-21T16:32:28ZJing Taotao@nceas.ucsb.edu
<p>To Whom It May Concern:</p>
<p>I am trying to use Morpho to create metadata for a project (Morpho has been updated to the latest version). I have entered all the information (that I have at this time, at least) into Morpho and can view everything that I’ve entered within the software. When I export the metadata and view the html or pdf files, everything is great except with defining nominal codes. For these attributes, a link name “Domain Info” is provided and when clicked the link either returns to the top of the metadata file (clicked within the Morpho preview) or opens a browser window that says “No file exists at the address “/metacat” (clicked from html or pdf files). I have attached a file for example. I am not a coder and have not been able to figure out a way for the nominal/category codes to be listed directly in the metadata export files. I don’t like the thought of having to export all my work from Morpho into Metavist, so thought I’d check with KNB for a possible solution first.</p>
<p>Thanks for any guidance that you are able to provide.</p>
<p>Best,</p>
<p>Jayne</p>
<p>I looked at the html of page and it shows:<br /><td class="innercoleven" align="center" colspan="2"><a href="/metacat?action=read&qformat=export&sessionid=&docid=&displaymodule=attributedomain&entitytype=dataTable&entityindex=4&attributeindex=6"><b>Domain Info</b></a></td></p>
<p>The link looks like to use the metacat read action to read the attributedomain module. However, this link as imported html can't work since it can't have the complete metacat url. I also search the Metacat code and can't find it supporting to display the attribute domain.</p>
<p>I also looked at the eml xslt code. Here is the code to generate the link at the template attributenonnumericdomaincommon:<br /> <a><xsl:attribute name="href"><xsl:value-of select="$tripleURI"/><xsl:value-of select="$docid"/>&displaymodule=attributedomain&entitytype=<xsl:value-of select="$entitytype"/>&entityindex=<xsl:value-of select="$entityindex"/>&attributeindex=<xsl:value-of select="$attributeindex"/></xsl:attribute></p>
<p>It seems there are issues on the export feature of Morpho. So the link doesn't work. However, we have a way to work around the issues. First, you may save the package to a Metacat server from Morpho. Then you can open the package on the link from a browser. You may save the html file which shows up on your browser to replace the metadata.html on your exported package directory.</p>
<p>Here is the link of an eml on our KNB web site (which is our default Metacat server on Morpho):<br /><a class="external" href="https://knb.ecoinformatics.org/knb/metacat?action=read&amp;docid=autogen.2017031514432105092.2&amp;qformat=default&amp;displaymodule=printall">https://knb.ecoinformatics.org/knb/metacat?action=read&amp;docid=autogen.2017031514432105092.2&amp;qformat=default&amp;displaymodule=printall</a><br />When you click the link "Domain info", it will show up the information. After you save your eml into KNB, you can open your package by modifying the above link - replace "autogen.2017031514432105092.2" by your docid.</p>
<p>If you do want to use one html to show all the information, you may use this link:<br /><a class="external" href="https://knb.ecoinformatics.org/knb/metacat?action=read&amp;docid=autogen.2017031514432105092.2&amp;qformat=metacatui&amp;displaymodule=printall">https://knb.ecoinformatics.org/knb/metacat?action=read&amp;docid=autogen.2017031514432105092.2&amp;qformat=metacatui&amp;displaymodule=printall</a><br />As I said, when you try to open your eml, you need to replace the "autogen.2017031514432105092.2" by your docid.</p> Bug #6111 (Closed): No resource map (ORE) document was created if morpho create an eml metadata d...https://projects.ecoinformatics.org/ecoinfo/issues/61112013-10-01T23:31:22ZJing Taotao@nceas.ucsb.edu
<p>Currently morpho will not create a resource map document for a eml document without data files. In the future, we may switch morpho from eml-oriented to datapackage-oriented. So it is good every eml document will have a data package document.</p> Bug #5899 (Closed): Morpho can't save a existed UUID package by DOI format without changing anythinghttps://projects.ecoinformatics.org/ecoinfo/issues/58992013-04-04T23:04:18ZJing Taotao@nceas.ucsb.edu
<p>matt: so let's say I have a package saved locally and on the net with a UUID<br />[3:58pm] matt: I want to give it a DOI<br />[3:59pm] matt: how do I do that without changing it? the Save dialog has the options disabled....<br />[4:00pm] Jing: good question.<br />[4:01pm] Jing: before, you could select DOI from the combo box, then the save dialog would be enabled.<br />[4:02pm] Jing: but we changed to the check box, we didn't consider this. it is a bug.</p> Bug #5897 (Closed): Improve UI for saving using a DOIhttps://projects.ecoinformatics.org/ecoinfo/issues/58972013-03-26T21:03:05ZJing Taotao@nceas.ucsb.edu
<p>1. In the Save Dialog, replace the selection list by a check box with the following text:</p>
<p>Publish with a DOI and make all metadata and data publicly readable</p>
<p>2. Add the following tooltip for the DOI:</p>
<p>A DOI (Digital Object Identifier) is a unique, permanent identifier that can be assigned to journal articles and data sets and is widely recognized as a means of citing these published products. An example DOI is doi:10….</p>
<p>3. If there are any data objects or metadata object is not public readable in this data package, the access policy will be changed to be public readable.</p> Bug #5896 (Closed): Get an error when user save a data package to net and local by using DOIhttps://projects.ecoinformatics.org/ecoinfo/issues/58962013-03-26T20:58:25ZJing Taotao@nceas.ucsb.edu
<p>matt: However, I just changed the data package, and tried to save to net and local again with a DOI, and I got this error:<br />[10:56am] matt: "Morpho couldn't find the source data file doi:10.5072/FK22F7WKT in any location (the temp, incomplete, data directories and the network) for copying" <br />[10:57am] benMac: that's no good. Jing - have you had problems with this before?<br />[10:57am] matt: and then the data isn't showing up in the morpho window any longer<br />[10:58am] matt: also, the newly saved data package didn't replace the original, so now the same data package is listed twice in my open dialog.</p> Bug #5885 (Resolved): Upgrading EML version causes access policy to be losthttps://projects.ecoinformatics.org/ecoinfo/issues/58852013-02-27T06:21:44Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Matt saved a DataONE package to the MN using R, but the EML was 2.0.1 and had no access rules in it. The SystemMetadata specified public access. When he opened it in Morpho it had him upgrade it to 2.1.1, but the access rules were lost.</p> Bug #5876 (Resolved): Modify the Access Page for users easily inputting a DNhttps://projects.ecoinformatics.org/ecoinfo/issues/58762013-02-22T00:26:34ZJing Taotao@nceas.ucsb.edu
<p>In today's meeting, Chris mentioned how a user inputted a DN rather than chose one from the tree. I took a look and found it is very hard to do that. The only way the DN input field showing up is the tree is null.</p>
<p>Ben and I discussed the GUI a little bit. We decided to add a check box there:<br />[x]Enter a Distinguish Name Manually</p>
<p>If this box is checked, the DN input field will show up and the tree selection will be hidden and vice versa.</p> Bug #5871 (Resolved): The revision manager contains the data files from different profile after u...https://projects.ecoinformatics.org/ecoinfo/issues/58712013-02-19T21:26:23ZJing Taotao@nceas.ucsb.edu
<p>A Revision Manager in Morpho 2.0 manages the data objects in a single profile. So every profile has a Revision Manager.</p>
<p>However, after upgrading from Morpho 1.x to Morpho 2.0, a Revision Manager may contain the objects from the other profiles.</p>
<p>For example, Morpho 1.x has two profiles - A and B. After the upgrading, the RevisionManager of the profile A only has the data objects in the profile A. This is correct behavior. However, the Revision Manager of the profile B has not only the objects in the profile B but also the objects in the profile A. This is not correct.</p> Bug #5870 (Resolved): Make sure that a newly generated profile doesn't need upgradehttps://projects.ecoinformatics.org/ecoinfo/issues/58702013-02-19T06:48:41ZJing Taotao@nceas.ucsb.edu
<p>Today, i created a new profile in morpho 2.0.0. I closed morpho and restart again. I saw an upgrade sign during the start process. The profile generated in Morpho 2.0 doesn't need the upgrade.</p> Bug #5868 (Resolved): Some weird behavior when morpho deletes a network data package with data filehttps://projects.ecoinformatics.org/ecoinfo/issues/58682013-02-14T22:47:13ZJing Taotao@nceas.ucsb.edu
<p>Here are the steps to produce the issue:<br />1. Use the new data package wizard and entity wizard to generate a data package.<br />2. Save it to network.<br />3. Go to File|Delete to delete the data package.<br />4. Morpho shows up a warning panel without any information.<br />5. The morpho frame does show up (It should disappear).<br />6. Morpho search on the network can't find the data package. It means that the data package does be removed.</p>
<p>When morpho delete a data package without data object, it works.</p> Bug #5866 (Resolved): Needs correct behavior for saving both when the saving network failshttps://projects.ecoinformatics.org/ecoinfo/issues/58662013-02-14T01:12:09ZJing Taotao@nceas.ucsb.edu
<p>When we choose to save a data package to the both location, the result of saving is the unsaved morpho frame (the frame before the saving) even though the local saving succeeds but the network saving fails. Since the local saving succeeded, we should display the local new data package and tell user the network saving failed.</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 #5861 (Resolved): Local delete doesn't delete the file storing the system metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/58612013-02-13T02:15:49ZJing Taotao@nceas.ucsb.edu
<p>The delete of local data package does delete the package itself. But it doesn't delete the stored system metadata file.</p> Bug #5808 (Resolved): Evaluate "Synchronize" feature for potential removalhttps://projects.ecoinformatics.org/ecoinfo/issues/58082013-01-24T19:12:24Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Synchronize is very similar to the Save action. I think the only difference right now is that you can invoke synch from the search/open dialog whereas a save requires you to open the package and then invoke save.<br /><del>When you Save from Local</del>>Network, the current id will be used unless it is already present on the network in which case an updated id will be used. This is the same for synch.<br /><del>When you save from Network</del>>Local, the network Id will be used locally unless it is already in use, in which case a new id will be generated and used. This is the same for synch.</p> Bug #1773 (Resolved): Importing code table results in display of ID numbers, not code valueshttps://projects.ecoinformatics.org/ecoinfo/issues/17732004-11-19T00:37:02ZAndrea Andreachadden@nceas.ucsb.edu
<p>When coded values are defined by importing a seperate table of code values and <br />definitions (in the DPW), the attribute info (next to "measurement domain") <br />displays ID numbers referencing the information in that table of codes, but <br />does not display the code definitions themselves. Therefore the person looking <br />at the attribute info for a column sees a long string of numbers (which have no <br />meaning to the user) instead of the information they need, namely, what do the <br />codes mean?</p>
<p>This bug was discovered by Veronique.</p>