Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362001-12-17T03:21:44ZEcoinformatics Redmine
Redmine Bug #375 (Resolved): morpho fails to display access metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/3752001-12-17T03:21:44ZMatt Jonesjones@nceas.ucsb.edu
<p>The new version of Morpho fails to display the access metadata associated with<br />older versions of EML. This seems to be because Morpho is configured to only<br />view the most recent version of EML in the config.xml file. For example, if I<br />have an old package that had an eml-access 2.0.0beta4 document associated with<br />it, and I try to open it under the new morpho, the access doc does not show up<br />in the list of other metadata. But if you edit the config.xml file and change<br />all references from "beta6" to "beta4" and relaunch morpho the files then show up.</p>
<p>The solution to this is to have morpho support multiple doctypes for each role<br />like access control. So, instead of a single "access_doctype" parameter, morpho<br />should take a list of doctypes. This is also true of other roles for doctypes<br />like "package_doctype" and any others. The idea is to have morpho work<br />seamlessly across EML upgrades and changes.</p>
<p>We may also want Morpho to be able to automatically connect to a server and<br />download the most recent version of eml with all of the relevant config files so<br />that users can easily upgrade their version of eml without understanding the<br />cryptic way in which Morpho configuration works.</p> Bug #363 (Resolved): update morpho and metacat DTDs to include EML2.0.0Beta5https://projects.ecoinformatics.org/ecoinfo/issues/3632001-12-01T01:07:55ZMatt Jonesjones@nceas.ucsb.edu
<p>We will release a new version of EML with our accumulated changes and with<br />updated documentation. Need to add these files to morpho and metacat and test<br />the full system using the new DTDs.</p> Bug #355 (Resolved): show icon indicating presence of data in package listhttps://projects.ecoinformatics.org/ecoinfo/issues/3552001-12-01T00:47:23ZMatt Jonesjones@nceas.ucsb.edu
<p>Current icons in the resultpanel show whether or not a file is local, or is on<br />metacat. Need to also show whether or not the package actually contains data<br />(versus metadata only).</p> Bug #352 (Resolved): errors in XML editor with complex documentshttps://projects.ecoinformatics.org/ecoinfo/issues/3522001-11-30T17:16:32ZDan Higginshiggins@nceas.ucsb.edu
<p>Several errors in the displayed XML document have been observed, especially with<br />complex documents with (CHOICE) nodes deep in hierarchy. In some cases, nodes<br />that are in document do not appear in the editor.</p> Bug #346 (Resolved): make sure morpho displays ALL eml field documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/3462001-11-30T03:10:04ZMatt Jonesjones@nceas.ucsb.edu
<p>Morpho now selectively displays eml documentation. Need to make sure that it<br />displays all of the EML documentation comprehensively. Probably best if it<br />would read the docs directly out of the XML Schema files.</p> Bug #343 (Resolved): text import doesn't reliably save datatypehttps://projects.ecoinformatics.org/ecoinfo/issues/3432001-11-30T02:55:21ZMatt Jonesjones@nceas.ucsb.edu
<p>The datatype field for attributes is parsed and set by the text import wizard<br />but is not saved reliably in the final eml that is output fromthe wizard. Need<br />to test this.</p> Bug #341 (Resolved): text import issues with eml-attribute creationhttps://projects.ecoinformatics.org/ecoinfo/issues/3412001-11-30T02:47:53ZMatt Jonesjones@nceas.ucsb.edu
<p>While parsing and importing text files we currently default fill in the<br />attribute definition to be identical to the attribute name. This is wrong. <br />Instead, we should have separate boxes for the attribute name, label,<br />definition, and units as part of the text import dialog. As the definitin is a<br />required field, the import wizard should not let the user move on until all<br />fields are defined (or post a warning like it does for other content violations).</p> Bug #333 (Resolved): add fields to package wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/3332001-11-30T01:48:05ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to add the core fields to the package wizard to allow for a reasonably<br />complete metadata set using only the package wizard. For the first screen<br />(eml-dataset), this means adding a "rights" field and an "abstract" field at a<br />minimum. We shoudl also seriously consider coverages, including the FGDC<br />bounding box (spatial) and taxonomic and temporal coverage.</p>
<p>Need to systematically review the rest of the screens and make informed<br />decisions about which fields should be included.</p> Bug #318 (Resolved): identifier not passed to new metadatat objectshttps://projects.ecoinformatics.org/ecoinfo/issues/3182001-11-06T01:40:05ZJames Bruntjbrunt@lternet.edu
<p>When trying to create new metadata objects I noticed that the identifier was <br />not passed to the new objects - I don't know if this is a bug or a feature?</p>
<p>James</p> Bug #315 (Resolved): Need to add eml-physical creation to package wizard and text input wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/3152001-11-02T22:48:41ZDan Higginshiggins@nceas.ucsb.edu
<p>Need to add eml-physical creation to package wizard and text input wizard to<br />capture info about seperators, record layout etc.</p> Bug #304 (Resolved): ampersand handling errorshttps://projects.ecoinformatics.org/ecoinfo/issues/3042001-10-23T19:12:43ZMatt Jonesjones@nceas.ucsb.edu
<p>Reported by Christy Bowles:<br />"Error in adding new packages (after complete package wizard and close package<br />editor):Org.xml.sax.SAXParseException. The entity name must immediately follow<br />the ?&? in the entity of reference."</p>
<p>"Can?t download files from Metacat (I could earlier today). I tried this several<br />times and nothing happened. Several later attempts generated the error<br />message:Org.xml.sax.SAXParseException. The entity name must immediately follow<br />the "&" in the entity of reference. Another attempt froze the program."</p> Bug #301 (Resolved): use UID as scope, chek for conflictshttps://projects.ecoinformatics.org/ecoinfo/issues/3012001-10-17T03:19:48ZMatt Jonesjones@nceas.ucsb.edu
<p>check that morpho generates scope + accession #'s correctly and that it recovers<br />gracefully when an accession # is already in use.</p> Bug #300 (Resolved): need to change Morpho DN behavior to send full DN on loginhttps://projects.ecoinformatics.org/ecoinfo/issues/3002001-10-17T03:16:26ZMatt Jonesjones@nceas.ucsb.edu
<p>Morpho currently only sends to metacat a truncated username for login. Need to<br />change this to be the full DN. Also need to change the user profile interface<br />to make it easy for the profile to be mapped to a DN, probably by having the<br />user pick from a preset list of organizations.</p> Bug #297 (Resolved): Problem with data Export from Metacathttps://projects.ecoinformatics.org/ecoinfo/issues/2972001-10-16T18:28:49ZDan Higginshiggins@nceas.ucsb.edu
<p>If a dataset which includes a data document is inserted into production Metacat<br />context and then 'Exported' the export of the data document appears to work<br />(because there is also a local copy?) However, if local dataset is deleted and<br />then one 'Exports' from Metacat, the data document contains an error message<br />rather than the data!</p>
<p>It is currently not clear whether this is a Morpho or a Metacat problem. Thus,<br />this error has been entered to both.</p> Bug #263 (Resolved): editor fails to create some CHOICE content modelshttps://projects.ecoinformatics.org/ecoinfo/issues/2632001-07-31T00:49:10ZMatt Jonesjones@nceas.ucsb.edu
<p>The Morpho editor has trouble representing some CHOICE content models for<br />editing properly, likely those that have multiple levels of nesting. For<br />example, in eml-physical.dtd, the following content model is not handled<br />properly in the editor:</p>
<p>(fieldStartColumn?, (fieldDelimiter | fieldWidth))*</p>