Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-12-03T22:14:44ZEcoinformatics Redmine
Redmine Bug #5757 (New): Add identifier scheme drop down to id conflict windowhttps://projects.ecoinformatics.org/ecoinfo/issues/57572012-12-03T22:14:44Zben leinfelderleinfelder@nceas.ucsb.edu
<p>In cases where we want to generate an identifier at the MN, we need to be able to tell the MN what type of identifier should be created. Usually we will target DOI, but only a handful of MNs will support this so we should have multiple options as well as a sensible default. Note that the scheme parameter for MN.generateIdentifier() is not optional.</p> Bug #4640 (New): add prev/next buttons to 'Edit Column Documentation' dialoghttps://projects.ecoinformatics.org/ecoinfo/issues/46402009-12-19T00:59:59ZJim Regetzregetz@nceas.ucsb.edu
<p>When a user needs to edit the documentation of several columns in one sitting, it is tedious to have to open and close the Edit Column Documentation dialog separately for each column. This often takes more time than the actual edit itself. This could be solved by adding "prev" and "next" buttons for moving back and forth across columns (and making multiple edits) within a single instance of the Edit Column Documentation dialog.</p>
<p>Note that the Import Data table wizard already has buttons to go back and forth across columns, albeit with extra things at the beginning and end of the wizard.</p> Bug #4621 (New): Allow sets of codes/definitions to be reused across data packageshttps://projects.ecoinformatics.org/ecoinfo/issues/46212009-12-10T23:21:24ZJim Regetzregetz@nceas.ucsb.edu
<p>Morpho allows enumerated value codes/definitions to be "imported from another table", although "imported" is somewhat of a misnomer because they are simply documented by reference (i.e., via entityCodeList in EML), and this only works within a single DP. This feature does <strong>not</strong> directly address the common use case of wanting to reuse identical (or similar) enumerated domains for different attributes, especially across DPs.</p>
<p>One approach might be to allow code/definition sets to be imported (copied) from <strong>any</strong> documented enumeratedDomain field that contains codeDefinitions, in any locally saved DP. This would require a GUI element to allow the user to select the desired DP, data table, and attribute to import from.</p>
<p>A second approach might be to provide a mechanism for users to save any existing code/definition sets to a local "registry" (in their morpho cache), and then import only from that code/definition registry. This would require a GUI element for saving (and probably naming) the codes/definitions from within the column documentation editor for enumerated domain attributes, and some modification of what the existing import button does.</p>
<p>After import, the codes/definitions should be editable for tweaking.</p>
<p>The general motivations for this bug are similar to those expressed for other forms of templating, namely in bug 1532 (for data packages) and bug 2851 (for attributes).</p> Bug #4416 (New): 1.7.0 - Geographic Coverage Sites List Should Record Tool Typehttps://projects.ecoinformatics.org/ecoinfo/issues/44162009-09-25T18:35:40ZWill Tyburczywilltyb@uchicago.edu
<p>When you select an item the shortcut list of sites in the geographic coverage window, it does not remember what tool type you used to create the item. Thus, if an item was created using the point tool but you select it while the currently selected tool is the box tool, it doesn't properly load the coordinates of the item.</p> Bug #2166 (New): 1.6.0RC1: Saving to network when a previous version was deleted from networkhttps://projects.ecoinformatics.org/ecoinfo/issues/21662005-08-03T00:03:44ZVeronique Connollyconnolly@nceas.ucsb.edu
<p>If a local data package is saved to the network, and the network copied<br />subsequently deleted from the network, saving a later version of the local copy<br />to the network will result in an error.</p> Bug #2095 (New): AbstractDataPackage - entity array not initialized automaticallyhttps://projects.ecoinformatics.org/ecoinfo/issues/20952005-05-30T21:38:56ZMatthew Brookebrooke@nceas.ucsb.edu
<p>This was discovered while writing a plugin for morpho - it doesn't affect how<br />morpho runs at the moment - but may cause complications in future if not addressed</p>
<p>Under some circumstances, for a datapackage with 1 or more entities, a call to<br />the AbstractDataPackage getEntityCount() method returns zero (0), and a call to<br />dataPackage.getEntityName(0) returns "No such entity!"</p>
<p>The reason is that the "entityArray" variable is not initialized until a call is<br />made to the getEntityArray() method. Therefore, as a temporary workaround for my<br />plugin, I called getEntityArray() before calling getEntityName(0)</p>
<p>SUGGESTED FIX - <br />1) ensure that all methods within AbstractDataPackage call getEntityArray()<br />instead of just using the global "entityArray" variable</p>
<p>2) ensure that subclasses do the same, by making "entityArray" private instead<br />of protected</p>
<p>(The plugin code can be seen in the jalama cvs module, under<br />jalama/src/edu/ucsb/nceas/jalama/entrypoint/morpho/OpenUIGenCommand.java, within<br />the method: private String getUniqueID_EML(int i) )</p> Bug #1985 (New): add morpho support for LSID identifiershttps://projects.ecoinformatics.org/ecoinfo/issues/19852005-02-18T01:54:06ZMatt Jonesjones@nceas.ucsb.edu
<p>Morpho currently uses traditional metacat identifiers when creating EML<br />documents. It needs to support LSIDs as described in Bug# 1984 both for<br />metadata and data references.</p> Bug #1983 (New): allow morpho to detect online data and import ithttps://projects.ecoinformatics.org/ecoinfo/issues/19832005-02-18T01:42:19ZMatt Jonesjones@nceas.ucsb.edu
<p>In several situations (such as Bug# 1982) an EML description might have a URL<br />pointing at an actual data file that is referenced in the top level EML<br />distribution section. When this occurs, Morpho should be able to import the<br />data from the URL, asking for the entity and attribute metadata, and move the<br />distribution reference to the entity distribution section.</p>
<p>If the data are stored in Metacat, then they need not be uploaded again, but<br />rather a simple reference to the Metacat id needs to be made to associate the<br />new metadata with the existing data.</p>
<p>If the data are at some other online URL, the data may need to be stored in<br />metacat (but only after the user has confirmed the operation).</p> Bug #1669 (New): Adding Project Information causes invalid eml 2 warninghttps://projects.ecoinformatics.org/ecoinfo/issues/16692004-09-02T17:12:24ZAndrea Andreachadden@nceas.ucsb.edu
<p>After adding Project information to a dp using the Morpho Editor and <br />clicking "OK", an error message pops up saying that "Validation Problem! The <br />saved document is not valid EML2 for some reason. You can save it locally and <br />fix the problem later but you will be unable to submit it to the network <br />storage system. Do you want to continue exiting the editor?" All of the <br />required fields in the project section are filled out, so this shouldn't be <br />invalid eml 2.</p>
<p>Sid discovered a hack to get around this problem. If you click "Yes" and exit <br />the editor, and then open the Editor again, and click OK, there is no invalid <br />eml2 message, and you can then save the dp to the network.</p> Bug #1481 (New): access list should support multiple selections in treehttps://projects.ecoinformatics.org/ecoinfo/issues/14812004-04-13T17:54:17ZMatt Jonesjones@nceas.ucsb.edu
<p>Current access list dialog allows users to select only one person in the user<br />tree at a time, and set permissions for that user. This enhancement request is<br />to allow for multiple user's ACL entires to be changed and selected at once. To<br />accomplish this, one possible approach would be to: 1) allow multiple select<br />from the table of acess rules, and 2) select each of these in the tree when<br />moving to the access tree. Adding more users by shift clicking would add new<br />records to the table. Need to be careful that it is clear to users that if they<br />deselect a person from the tree, their entry will be removed from the table. As<br />users can be spread apart very far in the tree (so multiple selections aren;t<br />simultaneously visible), this might be hard, especially because a single click<br />on the tree clears all of the current selections. We might want to change the<br />selection mechanism for the tree to be a 'double click' on a user to toggle<br />selection/deselection. This would make it harder to accidentally clear a bunch<br />of records, even though it is somewhat non-standard (shift and ctrl click are<br />more typical).</p> Bug #1460 (In Progress): Ablity to use TemporalPage.java from attribute or entity levelhttps://projects.ecoinformatics.org/ecoinfo/issues/14602004-04-08T21:30:28ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Temporal Page and hence other screens should be able to be retrieved from lower <br />down in eml hierarchy. e.g. assigning temporal coverage for an attribute. Right <br />now it can only be assigned on the DataPackage level through DPW.</p> Bug #1261 (In Progress): Advanced Geographic Display Systemhttps://projects.ecoinformatics.org/ecoinfo/issues/12612004-01-16T17:54:57ZDan Higginshiggins@nceas.ucsb.edu
<p>Currently, there is a geographic display in the Query system and it is being<br />adapted for the Geographic Coverage wizard. There are a number of extra features<br />that are desirable (see copy of email from MJones attached) especially the need<br />to provide higher resolution displays (higher zoom levels).</p>
<p>This appears to be a considerable effort (need for large images, multiple<br />images, or handling of vector data). We should thus consider a more advanced<br />geographic display system, perhaps 'GeoTools'.</p> Bug #664 (In Progress): add keyboard shortcuts for menushttps://projects.ecoinformatics.org/ecoinfo/issues/6642002-10-31T17:02:30ZMatt Jonesjones@nceas.ucsb.edu
<p>Most menu items lack keyboard shortcuts. Need to add them for all of the<br />standard ones (e.g., ctrl-w for close window, ctrl-o for open, etc.) and for the<br />non-standard ones where it would be useful (e.g., to hide/show metadata panes).</p> Bug #530 (In Progress): add spell checking supporthttps://projects.ecoinformatics.org/ecoinfo/issues/5302002-06-13T15:33:57ZMatt Jonesjones@nceas.ucsb.edu
<p>Need a spell checker that checks common words in science as well as standard<br />english. Use while editing metadata.</p> Bug #326 (In Progress): Ability to repeat more than one fieldhttps://projects.ecoinformatics.org/ecoinfo/issues/3262001-11-09T18:52:34ZChristy Christyubowlc00@umail.ucsb.edu
<p>The repeat button to add more fields is good, but it would be useful to be able<br />to have the ability to add more than one set of fields at a time. This would be<br />especially applicable to describing attributes for a large table. Maybe a second<br />button next to the repeat button (?multiple repeat?) could pull up a screen that<br />asks how many fields to add?</p>