Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-01-25T21:45:28ZEcoinformatics Redmine
Redmine Bug #4695 (Resolved): CSS doesn't work on mac installer versionhttps://projects.ecoinformatics.org/ecoinfo/issues/46952010-01-25T21:45:28ZJing Taotao@nceas.ucsb.edu
<p>The morpho metadata display loses color on mac installer version. Howerver, it works on windows and linux installer. The morpho built from svn on mac works too.</p> Bug #4678 (Resolved): Modify the documentation for 1.8 releasehttps://projects.ecoinformatics.org/ecoinfo/issues/46782010-01-15T20:18:16ZJing Taotao@nceas.ucsb.edu
<p>I will draft a new version of user manual.</p> Bug #4677 (Resolved): Windows 7 installer/testinghttps://projects.ecoinformatics.org/ecoinfo/issues/46772010-01-15T20:13:17Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Make sure Morpho installs and runs on Windows 7</p> Bug #4646 (Resolved): when upgrading from 2.0.1, morpho did not catch empty <offline> elementhttps://projects.ecoinformatics.org/ecoinfo/issues/46462010-01-04T23:00:54ZMargaret O'Brienmob@msi.ucsb.edu
<p>a user updated her morpho to 1.7.1, and loaded a 2.0.1 package. The first thing she must do is upgrade to EML2.1.0<br />The data package did not included a data table, but included the table attribute descriptions, so morpho 1.7.1 had inserted 2 elements which are not allowed in EML2.1:<br />1. an empty <objectName> </objectName><br />2. <offline> with no children<br />Morpho presented the user with a dialog box for adding the objectName, but ignored the offline element. The error message (from the parser) was not useful to the scientist.<br />The file is attached.<br />[Note: this file actually had 2 errors, but the other problem is addressed in another bug: 3978]</p> Bug #4543 (Resolved): export to FGDC BDP formathttps://projects.ecoinformatics.org/ecoinfo/issues/45432009-11-12T20:09:19ZMatt Jonesjones@nceas.ucsb.edu
<p>Include a 'format' dropdown in the Export dialog that allows people to choose the 'FGDC BDP' format as an export choice. The set of export formats should be configurable at runtime, and should allow for a mapping between the format name and an XSLT script used to generate that format from the EML document.</p> Bug #4422 (Resolved): morpho installer freezes when it creates short cut on windows 64-bit machinehttps://projects.ecoinformatics.org/ecoinfo/issues/44222009-09-28T19:22:00ZJing Taotao@nceas.ucsb.edu
<p>I think this is the right group of people for this problem, but I'm<br />not entirely sure. I'm trying to install Morpho 1.7.0, but it's<br />getting stuck when trying to create shortcut icons. The same thing<br />happened with the Kepler 2.0.0-alpha installer, and we figured out<br />that izpack requires some special 64-bit dlls for 64-bit Windows. I<br />don't really know any more specific details, but I recall Chad being<br />able to fix it for Kepler.</p> Bug #4253 (Resolved): ids for role confict when the person was imported from another packagehttps://projects.ecoinformatics.org/ecoinfo/issues/42532009-07-16T14:06:50ZJing Taotao@nceas.ucsb.edu
<p>Nikki in Phalaborwa showed me package which couldn't be saved to metacat. It turned out that there is one id for two different person. She said one person was imported from another package. So the importing causes the id conflict.</p> Bug #4106 (Resolved): Add Cancel button to dialog for closing unsaved packagehttps://projects.ecoinformatics.org/ecoinfo/issues/41062009-05-22T22:21:44ZJim Regetzregetz@nceas.ucsb.edu
<p>Closing an unsaved data package (or exiting Morpho when unsaved DPs are open) produces a dialog that only offers two options: save the DP, or close it without saving. A Cancel button should be added to allow users to go back to editing the DP if they change their mind or had accidentally closed the DP before they were ready.</p>
<p>I'm calling this an enhancement, but think it's pretty important. Currently, users can find themselves forced to choose between saving unwanted/incomplete changes or discarding desired changes (this has happened to me).</p> Bug #3946 (Resolved): feature request: a wizard to add content to distribution/online/urlhttps://projects.ecoinformatics.org/ecoinfo/issues/39462009-04-06T17:13:42ZMargaret O'Brienmob@msi.ucsb.edu
<p>EML documents can contain urls to resources like dataTables and protocol docs via its physical/distribution/online node. Morpho has no way to enter URLs.</p> Bug #3314 (Resolved): Morpho abstract search comes up with 0https://projects.ecoinformatics.org/ecoinfo/issues/33142008-05-22T21:43:09ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>The Morpho search only for abstract comes up with zero even if that word is part of abstracts on the server. This bug is similar to 3177</p> Bug #2379 (Resolved): Table metadata lost when trying to import codes from second filehttps://projects.ecoinformatics.org/ecoinfo/issues/23792006-03-09T21:53:11ZWill Tyburczytyburczy@nceas.ucsb.edu
<p>Morpho seems to be exiting out of not only the table import for the secondary<br />table containing the codes for an enumerated domain, but also the main table<br />being imported, if the second file imported is not a text file. This can<br />result in the loss of a lot of effort (in a recent case, 3 hours worth). To<br />reproduce this bug:</p>
<p>- Create a column that's "nominal" or "ordinal" with an enumerated domain (or<br />edit an existing column of taht type)<br />- Select "codes are imported from another table" and click "locate" <br />- Select "Import the table definitions into morpho later" and click "ok" <br />- When done documenting all the columns for the table, you will be asked to<br />import the code definitions for that column<br />- Select "the table containing the definitions needs to be imported into Morpho" <br />- Select "Automatic" for the type of import and click "Locate" <br />- Select a file that is not a text file (like an excel file) and click "Next"</p>
<p>At this point you will get a messge saying "The selected file is NOT a text<br />file!". When you click ok, you will be thrown out of the import of not only the<br />code definition table, but the main table as well, losing all you work. If you<br />select an inappropriate file for the code definition table, it should only exit<br />out of the import for that table, possibly prompting you to select another file.<br /> You should not lose all the information you put in for the main table.</p> Bug #2308 (Resolved): No metadata shown if schemaLocation attribute set improperlyhttps://projects.ecoinformatics.org/ecoinfo/issues/23082005-12-05T19:05:12ZWill Tyburczytyburczy@nceas.ucsb.edu
<p>If the xsi:schemaLocation attribute of the eml element of a document is set<br />improperly, no metadata (creator, coverage, table descriptions, etc) for the dp<br />are shown. Removing the attribute altogether allows the dp to display properly.<br /> Morpho should be using the namespace rather than the schemaLocation to<br />determine the type of the eml document.</p> Bug #1847 (Resolved): import EML documents into Morphohttps://projects.ecoinformatics.org/ecoinfo/issues/18472004-12-21T18:03:48ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>We need to implement a feature that allows the import of EML documents and<br />tabular data associated with these documents. The import step would include<br />validation to ensure that the document is a valid EML document. The docid of the<br />imported document would be compared to the docids of local data packages. If a<br />similar docid is found, Morpho would ask whether the user wants to create a<br />revision of the existing dp or create a new dp. If no similar docid is found,<br />Morpho would automatically create a new dp (with a new docid).</p>
<p>This import feature would allow importing documents that have been created by<br />the current Export feature of Morpho. Currently, there is not a straightforward<br />way of opening in Morpho a data package created by the Export command (see bug<br />1793). When using the Export command, the document created should be saved in a<br />place where it will easily be retrieved when using the import feature.</p>
<p>On top of allowing the import of existing EML documents, the import feature<br />would allow users to have a "template" dp from which they would create new dps<br />that usually differ only slighty in their format. This would lessen the burden<br />of creating new dps from scratch.</p> Bug #1771 (Resolved): Deleting row of taxonomic info in DPW prevents selection of other rows,https://projects.ecoinformatics.org/ecoinfo/issues/17712004-11-19T00:26:00ZAndrea Andreachadden@nceas.ucsb.edu
<p>In the top portion of the taxonomic coverage screen in the DPW, if you add a <br />few rows of information, and then delete the bottom row, the other rows become <br />unselectable, and the DELETE and EDIT buttons disappear.</p>
<p>This bug was discovered by Veronique.</p> Bug #1211 (Resolved): add serialization to steps in DataPackage Wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/12112003-11-17T20:50:18ZDan Higginshiggins@nceas.ucsb.edu
<p>There are potentially many steps in the DataPackage wizard, expecially when one<br />is entering matadata for a table with many columns. There should be some<br />automatic mechanism for serializing the data already entered in case of some<br />failure before a new package is saved. Serializing the<br />DataPackage/TextImportWizard as each screen (or column) is changed seems like a<br />usful approach that should be implemented.</p>