Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362007-10-29T19:07:33ZEcoinformatics Redmine
Redmine Bug #2988 (Resolved): Custom unit does not allways create the needed <additionalMetadata> tagshttps://projects.ecoinformatics.org/ecoinfo/issues/29882007-10-29T19:07:33ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>An example of a data package that had to be edited in a text editor is the following:<br /><a class="external" href="http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=knb&docid=gss1.22&displaymodule=entity&entitytype=dataTable&entityindex=1">http://knb.ecoinformatics.org/knb/metacat?action=read&qformat=knb&docid=gss1.22&displaymodule=entity&entitytype=dataTable&entityindex=1</a></p>
<p>Here is part of the error reported in the stderr.log</p>
<p><error><br />Error processing keyrefs: //unit/customUnit : Error in xml document. This EML instance is invalid because referenced id partsPerBillion does not exist in the given keys.<br /></error></p>
<p>There is a partsPerBillion, and a partsPerMillion custom unit that the user created using Morpho but when the dp was saved the necessary <additionalMetadata> tags were not created. Then we had to add the following, using a text editor, so that the data package would save up to the network.</p>
<p><additionalMetadata><unitList><unit id="partsPerMillion" multiplerToSI=" " name="partsPerMillion" parentSI="molesPerCubicMeter" unitType="amountOfSubstanceConcentration"><description>partsPerMillion</description><br /> </unit><br /> </unitList><br /> </additionalMetadata><br /> <additionalMetadata><unitList><unit id="partsPerBillion" multiplerToSI=" " name="partsPerBillion" parentSI="molesPerCubicMeter" unitType="amountOfSubstanceConcentration"><description>partsPerMillion</description><br /> </unit><br /> </unitList><br /> </additionalMetadata></p> Bug #2957 (Resolved): Other entity does not display other entity Descriptionhttps://projects.ecoinformatics.org/ecoinfo/issues/29572007-09-10T19:46:22ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>Morpho does not have an interface for working with the otherEntity element. Morpho does not import other entities. I have been using Morpho in combination with a text editor to do this.</p>
<p>Morpho only works with the dataTable element when displaying Entity information. When Morpho works with a file that is not a dataTable type of entity, the Entity Description information is missing. Our new online form will include the ability to upload other entities. Morpho needs to allow for the other kinds of entities.</p>
<p>Currently the display and download of other entities works fine on the knb/nceas website.</p> Bug #2508 (Resolved): Incorrect example for relative attribute given in table wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/25082006-08-02T17:00:39ZWill Tyburczytyburczy@nceas.ucsb.edu
<p>In the new data table wizard, the example for the attribute category "relative" is currently "12.2 meters". However, meter measurements are generally absolute measurements, not relative measurements. The example of a relative attribute should instead be something like "12 degrees Celsius". This should be a quick fix, but it's important to have good examples here since the distinction between the categories is already confusing to many users.</p> Bug #2443 (Resolved): Dialog box needed to warn when deleting data tablehttps://projects.ecoinformatics.org/ecoinfo/issues/24432006-05-24T01:01:21ZCallie Bowdishbowdish@nceas.ucsb.edu
<p>There is no "Delete" dialog box for data tables. When the request to "Delete Current Data Table" is given no dialog box comes up. The table is deleted.</p>
<p>We need something similar to the Delete the Morpho Data Package dialog box.<br />When a request to Delete (through the File menu) is given a "Delete" dialog box comes up. It says, "Are you sure you want to delete the data package? If yes, please choose one option and click the Delete button." The options adjust depending on the state of the file being deleted. If it has never been saved, all of the options are gray for instance.</p>
<p>If the data table is deleted through a menu request, the only way to recover the data table is to close the data package without saving the changes. In some cases, the data packaged has never been saved. This recovery will not work in that case. If many changes have been made and not saved, all of them will be lost.</p>
<p>In order to protect the user from the wrong choice on the menu a dialog box should come up. This way the user can confirm that they want to delete the table. In some cases where there are more than one table. It would be good to have the name of the table that will be deleted named in the dialog box.</p>
<hr />
<p>Regarding "Delete Selected Row" and "Delete Selected Column" <br />In most cases I was able to use the "Revert Entity to Saved Version" and the "Revert All Entities to Saved Version" choices, in the Edit menu, after deleting columns and Rows.</p>
<p>When only the table attributes are listed, but no actual data table, is available, the columns cannot be recovered. A table that brings up the following dialog box when it is first opened in Morpho tests this case. The dialog box titled, “Warning!†says, "Unable to display this data. However, an empty table with the column header information will be shown...". There is no revert option for this kind of column and header information.</p>
<p>I am uncertain about the usefulness of the dialog box for deleting selected rows and columns. The edit menu is able to undo this. I do not think it is a standard practice to warn with a dialog box when editing a row or column.</p>
<hr />
<p>I think it is important to have the dialog box come up when deleting data tables in Morpho.</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 #2284 (Resolved): Data tables not uploaded to networkhttps://projects.ecoinformatics.org/ecoinfo/issues/22842005-11-22T23:35:13ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>I saved a dp named connolly.258.1 to the knb metacat. This dp contains two data<br />tables: ecogrid://knb/connolly.261.1 and ecogrid://knb/connolly.262.1.</p>
<p>When I searched for that dp in Morpho and opened it, I got an error message saying <br />"Exception opening file!". When I clicked OK for this message, I got another<br />dialog box saying the following:</p>
<p>"Unable to display this data. However, an empty table with the column header<br />information will be shown. Data is referenced by the URL<br />ecogrid://knb/connolly.261.1"</p>
<p>I got the same kinds of messages when trying to display<br />ecogrid://knb/connolly.262.1.</p> Bug #2280 (Resolved): methodStep creation errorhttps://projects.ecoinformatics.org/ecoinfo/issues/22802005-11-17T20:58:59ZJames Bruntjbrunt@lternet.edu
<p>When creating the method step in the ingestion wizard - you enter a title and<br />description - this creates a section, title, and paragraph. But there is a<br />paragraph required after methodStep that doesn't get filled in. Then if you try<br />to edit that empty field can't be deleted or trimmed.</p> Bug #2206 (Resolved): Tree editor does not properly process additionalMetadata items when "trimming"https://projects.ecoinformatics.org/ecoinfo/issues/22062005-09-22T17:27:22ZWill Tyburczytyburczy@nceas.ucsb.edu
<p>If a data package contains an additionalMetadata element (for example to define<br />a custom unit), the tree editor does not execute the "trim" function properly. <br />The editor insists that a value for the "any" element must be supplied, instead<br />of recognizing the element (in this example, unitList) that is intended to<br />replace it. If the user actually then fills in a value for the "any" element to<br />allow them to exit from the tree editor, invalid eml is generated. For example,<br />if you start with:</p>
<p>additionalMetadata
|
|<br />+--unitList
| |
| +(custom units defined in by the morpho wizard)
|<br />+--describes</p>
<p>After the trim function is done, you are left with:</p>
<p>additionalMetadata
|
|<br />+--unitList
| |
| +(custom units defined in by the morpho wizard)
|<br />+--ANY
| |
| +(whatever the user added to get the tree editor to exit)
|<br />+--describes</p>
<p>This forces the user to create invalid eml to exit the editor, which would then<br />prevent them from saving the data package onto the knb.</p> Bug #2193 (Resolved): Morpho incorrectly tries to insert rather than update when trying to save r...https://projects.ecoinformatics.org/ecoinfo/issues/21932005-09-09T18:34:08ZWill Tyburczytyburczy@nceas.ucsb.edu
<p>Morpho sometimes fails to save revisions to data packages to the network. It<br />tries to "insert" rather than "update" the package, which then produces the<br />error: "Problem Saving Data: Id already in use". the data package involved had<br />been modified and saved several times locally prior to attempting to save to the<br />network, and was name nceas.227.12 (the network version was nceas.227.1).</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 #1831 (Resolved): "other" organization field does not workhttps://projects.ecoinformatics.org/ecoinfo/issues/18312004-12-15T18:20:59ZChad Berkleyberkley@nceas.ucsb.edu
<p>if you put an organization name in the "other" field in the new user wizard,<br />morpho does not actually use the name you fill in, instead it uses whatever is<br />selected in the list box. the desired functionality is that when you click in<br />the other field, the list box selection should be cleared and morpho should use<br />the user entered org name.</p> Bug #1777 (Resolved): Selecting columns is very slowhttps://projects.ecoinformatics.org/ecoinfo/issues/17772004-11-19T01:01:06ZAndrea Andreachadden@nceas.ucsb.edu
<p>It takes an excruciatingly long time to select a column in a data table. On <br />Andrea's computer and on Veronique's computer, it takes up to 20 seconds for a <br />column to be selected after you click on the column header. On Dan's computer, <br />it takes about 4 seconds. All are PCs.</p>
<p>The search and open functions of morpho also take a long time to complete, <br />although not as long as the column selection takes.</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>