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 #371 (Resolved): problems with wizard-generated eml-physical documentshttps://projects.ecoinformatics.org/ecoinfo/issues/3712001-12-08T09:18:21ZMatt Jonesjones@nceas.ucsb.edu
<p>The text import wizard generates eml-physical documents. They have some issues:</p>
<p>1) fieldDelimiter and recordDelimiter are written out in English instead of<br />using actual ASCII symbol (e.g., "comma" instead of ","). Need to decide on a<br />convention. I would suggest using the ascii character, or its octal (\054) or<br />hex (0x2C) equivalents for non-printing characters. thus, a newline would be<br />"0x0A" and a carraige return would be "0x0D", but a comma would be ",".<br />2) Wrong number of header lines entered into metadata. The file says there was<br />1 header line, when in fact there was 0.<br />3) The "size" element contains the string "bytes" which is not supposed to be<br />there because it is defined in the "unit" attribute of the size element. So, it<br />should be:<br /> <size unit="bytes">26</size><br />4) the SYSTEMID in the DOCTYPE line is wrongly set to "eml-entity" when it<br />should be set to "eml-physical"</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 #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 #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 #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 #244 (Resolved): need refresh mechanism for query screenhttps://projects.ecoinformatics.org/ecoinfo/issues/2442001-07-06T17:43:45ZChad Berkleyberkley@nceas.ucsb.edu
<p>The query result screen needs to be able to handle a refresh command from other<br />plugins. This will allow the package editor/wizard (or other future plugins) to<br />call a refresh when it makes changes to the document base.</p> Bug #239 (Resolved): search dialog allows user to uncheck both catalog and local searchhttps://projects.ecoinformatics.org/ecoinfo/issues/2392001-06-19T23:37:10ZChad Berkleyberkley@nceas.ucsb.edu
<p>search dialog allows user to uncheck both catalog and local search. It then<br />throws a NullPointerException and crashes. Error checking should be added so<br />that only one of them can be unselected at a time, or the check boxes should be<br />turned into radio buttons (which are more suited for this purpose).</p> Bug #236 (Resolved): improve handling of query optionshttps://projects.ecoinformatics.org/ecoinfo/issues/2362001-06-13T08:56:43ZMatt Jonesjones@nceas.ucsb.edu
<p>QueryDialog currently hard codes the "casesensitive" query option and does not<br />allow the user to set and control many important options. Possibly add a new<br />tab for these query options, which would read and write the results to the users<br />profile. This includes: casesensitivity, local search toggle, metacat search<br />toggle, and other relevant search options.</p> Bug #232 (Resolved): [RFE] saved querieshttps://projects.ecoinformatics.org/ecoinfo/issues/2322001-05-08T18:40:53ZMatt Jonesjones@nceas.ucsb.edu
<p>It would be pretty easy to implemet a "saved queries" feature where a user could<br />save a pathquery document to disk so that it could be rerun at a later date. We<br />should probably save all of the queries in "lib/saved-queries" and then update<br />the lib/config.xml file with a <savedquery file="q001.xml>Title of the<br />query</savedquery> entry for each of the saved queries. The title would be<br />cached in the config file so that the Search menu could display menu items for<br />all of the saved queries without having to read each of the query files. When<br />the menu item is fired, we would retrieve the pathquery from disk and execute<br />it, bypassing the QueryDialog. Note that because pathqueries are XML documents,<br />it would also be possible to save these on the network using Metacat, possibly<br />as part of a user profile scheme.</p> Bug #165 (Resolved): taxonomic search facilityhttps://projects.ecoinformatics.org/ecoinfo/issues/1652000-10-31T16:44:01ZDan Higginshiggins@nceas.ucsb.edu
<p>Add at least simple taxonomic and spatial search capability</p> Bug #115 (Resolved): need short-term dataset parser implementationhttps://projects.ecoinformatics.org/ecoinfo/issues/1152000-09-20T18:03:32ZMatt Jonesjones@nceas.ucsb.edu
<p>Need a data set parser to extract relevant file- and variable- information for <br />MARINE datasets. The parser should generate XML output that is suitable for <br />inclusion in eml-file and eml-variable metadata modules, and that will help <br />speed data entry for the MARINE datasets. This may be implemented in SAS.</p>