Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362002-03-25T20:19:06ZEcoinformatics Redmine
Redmine Bug #448 (Resolved): FileSystemDataStore class not configured for binary fileshttps://projects.ecoinformatics.org/ecoinfo/issues/4482002-03-25T20:19:06ZDan Higginshiggins@nceas.ucsb.edu
<p>currently, the FileSystemDataStore class is set up to work with 'Reader' object;<br />i.e. character streams. This causes problems for binary data files like jpeg or<br />gif images (corrupts the data). Need to revise to handle arbitrary file. (i.e.<br />streams)</p> Bug #431 (Resolved): upload method bugshttps://projects.ecoinformatics.org/ecoinfo/issues/4312002-02-15T04:28:27ZDan Higginshiggins@nceas.ucsb.edu
<p>The upload method in DataPackage class calls the method incrementPackageIds.<br />This method puts the metadata files into strings which is problematic for very<br />large packages. <br />Also, data and metadata are treated identically which causes a problem when<br />attempts are made to put ids into data file. <br />Also, upload attempts to see if a file is data by checking whether or not it is<br />an xml file. This will cause problems if XML is ever used for data.<br />Should add method to check if file is a data file (using triples).</p> Bug #426 (Resolved): data package displays wrong infohttps://projects.ecoinformatics.org/ecoinfo/issues/4262002-02-14T18:22:29ZMatt Jonesjones@nceas.ucsb.edu
<p>When a data package is opened in the Data Package Editor, incorect information<br />is displayed for some of the originators. In particular, metadata documents<br />with originators that have only an "organizationName" field (ie, no<br />individualName) incorrectly display the individualName and address and other<br />fields from the previous originator. It appears that a data structure is not<br />being initialized when looping through the originators, so originator fields<br />from previous originators are retained when displaying an originator that did<br />not have that field.</p>
<p>An example of the problem can be seen by searching for and viewing the document<br />'nrs.3.2'.</p> Bug #424 (Resolved): Memory Problems with Big DataPackageshttps://projects.ecoinformatics.org/ecoinfo/issues/4242002-02-13T21:46:41ZDan Higginshiggins@nceas.ucsb.edu
<p>There have been several cases were the JVM has run out of memory when users<br />create datapackages with either very large datasets or many different datasets<br />in the same package.</p>
<p>Need to investigate why all available memory is being used. Solution may be to<br />simply increase the memory requested by Java at startup (default=64M) so that<br />the problem does not occur on machines that have more memory.</p> Bug #423 (Resolved): Change Default to Use TextImport Wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/4232002-02-13T21:42:40ZDan Higginshiggins@nceas.ucsb.edu
<p>requested by REOT group</p>
<p>Currently the DataPackage Wizard has the default "Manually enter data file<br />descriptions". Automatic option almost always used by REOT.</p> Bug #416 (Resolved): editor bug - empty branches not being trimmed properlyhttps://projects.ecoinformatics.org/ecoinfo/issues/4162002-02-08T16:43:39ZDan Higginshiggins@nceas.ucsb.edu
<p>in eml-attribute, if there is no data in the attributeDomain element (i.e. no<br />subnodes have any text, then only the <attributeDomain> tag is saved with no<br />children. This results in an invalid document.</p> Bug #415 (Resolved): Bug in editor creates invalide docs(rngdates)https://projects.ecoinformatics.org/ecoinfo/issues/4152002-02-08T16:40:15ZDan Higginshiggins@nceas.ucsb.edu
<p>In the temporalCov element of eml-dataset, the choices under the "rngdates" <br />choice are not displayed and saved properly. This results in an invalid document.</p>
<p>The problem is the lack of a SEQUENCE grouping which is incorrectly being dropped.</p> Bug #410 (Resolved): need to use more descriptive relationships in building triple statementshttps://projects.ecoinformatics.org/ecoinfo/issues/4102002-02-02T09:35:08ZChris Jonescjones@nceas.ucsb.edu
<p>Morpho and other clients that build triple statements in eml-dataset docs <br />should use more descriptive relationship strings. They should also come from <br />an standard list. Perhaps:</p>
<p>is data entity in<br />provides access control rules for<br />provides data entity information for<br />provides project information for<br />provides protocol information for<br />provides attribute information for<br />provides physical file information for</p>
<p>etc. Lastly, some relationships for data files such as: <br />isDataFileFor(C:\Documents and Settings\cjones\DESKTOP\allsp.txt) <br />are being generated by the package wizard. Seems like the path should be nixed <br />from the relationship...</p> Bug #409 (Resolved): package export interface not intuitivehttps://projects.ecoinformatics.org/ecoinfo/issues/4092002-02-02T01:18:07ZMatt Jonesjones@nceas.ucsb.edu
<p>When exporting data from Morpho, the directory selection interface is confusing.<br /> When the file chooser appears, it expects you to single-click on the name of a<br />directory. Howver, most users would generally navigate to inside the directory<br />in which they want the export placed. Also, the label asks for a "File name",<br />when in fact you are selecting a "Directory" or "Folder" name.</p>
<p>Proposed solution: 1) Change the label to "Folder name", 2) allow the user to<br />either select the folder directly (from the parent) or to enter the folder and<br />select nothing. If their is no folder name selected when the user hits the<br />button, then morpho should select the current directory that the use ris in in<br />the file chooser.</p>
<p>Here's an example, given the that folders /a/b exist:</p>
<p>If user wants to save in b, he can either enter folder a and click once on b<br />then hit Save, or enter folder b and hit save. They would both put the data<br />export in folder b.</p> Bug #405 (Resolved): Problems editing dataset eml files from nrs web pagehttps://projects.ecoinformatics.org/ecoinfo/issues/4052002-01-25T20:38:43ZDan Higginshiggins@nceas.ucsb.edu
<p>There is a problem when one tries to use Morpho to edit dataset files created<br />using the nrs web page input and then opened in Morpho. It looks like the Morpho<br />editor inserts some optional nodes in the wrong location, then does not remove<br />them even if empty, and thus tries to submit an invalid document when the doc is<br />edited. The error message also seems inappropriate. Details still need to be<br />determined.</p> Bug #402 (Resolved): can't update data files in current Morpho UIhttps://projects.ecoinformatics.org/ecoinfo/issues/4022002-01-23T16:50:05ZMatt Jonesjones@nceas.ucsb.edu
<p>Joel Gramling reports:<br />Additionally, I haven't figured out if you can add more data to a table once you<br />have already established the descriptions or if you have to reload updated<br />datasets as new ones.</p>
<p>This is indeed a problem. Right now you can add a new data table (with<br />metadata), and you can associate a data table with an existing set of metadata,<br />but there is no way to change an existing table. Need to be able to change the<br />data file associated with the data set (which creates a new revision, but<br />doesn't delete the old!). Sometimes this will require a change in the metadata<br />as well (ie, to update coverage info), while other times no change in metadata<br />will be needed other than to associate the new entity & file.</p> Bug #401 (Resolved): Morpho Problems with Very Large Data Fileshttps://projects.ecoinformatics.org/ecoinfo/issues/4012002-01-23T16:32:26ZDan Higginshiggins@nceas.ucsb.edu
<p>One of the REOT students tried submitting a very large (360,000 lines) data file<br />and discovered that Morpho 'hangs' in trying to work with the file (i.e. in<br />going from one screen to the next in the Package wizard.</p>
<p>It looks like the problem is due to code which copies the data file to a string<br />(i.e. an in-memory data structure)</p> Bug #399 (Resolved): Editor problem with repeated elementshttps://projects.ecoinformatics.org/ecoinfo/issues/3992002-01-15T04:55:21ZDan Higginshiggins@nceas.ucsb.edu
<p>When elements are repeated (eg the attribute element in eml-attribute) and<br />subelements are repeated, it turns out that entering a text value for one<br />element causes all the duplicate elements to have the same value!</p> Bug #397 (Resolved): editor resizes very slowlyhttps://projects.ecoinformatics.org/ecoinfo/issues/3972002-01-11T19:45:37ZChad Berkleyberkley@nceas.ucsb.edu
<p>If you resize the editor screen, it takes a very long time to redraw. It seems<br />like it is doing the entire dtd parse over again. I don't know if that is<br />really the case but the amount of time it takes to resize is roughly<br />proportional to the time it originally takes to open. it would be nice if you<br />could quickly resize the window to meet your needs.</p> Bug #392 (Resolved): when upload error occurs metacat and local copies can divergehttps://projects.ecoinformatics.org/ecoinfo/issues/3922002-01-11T19:14:23ZChad Berkleyberkley@nceas.ucsb.edu
<p>when changing a file that is both on metacat and local, if a metacat upload<br />error occurs because of a problem with the document (such as a missing required<br />tag) the local copy is still saved, even though it is invalid but the metacat<br />copy is not saved, causing the two copies to diverge. morpho then only shows<br />the newest revision which is the local (and now invalid) one.</p>