Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-08-03T14:51:46ZEcoinformatics Redmine
Redmine Bug #5117 (Resolved): Add an "Edit Profile..." dialoghttps://projects.ecoinformatics.org/ecoinfo/issues/51172010-08-03T14:51:46Zben leinfelderleinfelder@nceas.ucsb.edu
<p>If you enter an incorrect username or organization for your profile, there is no way to edit the mistake. You can delete the profile and start fresh, but often times a number of datapackages have already been created in that profile and migrating DPs to a new one is not the most straightforward process.</p> Bug #5079 (Resolved): Convert User Manual to LaTex formathttps://projects.ecoinformatics.org/ecoinfo/issues/50792010-07-06T23:50:44Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Jim suggested LaTex could streamline the user manual update process. Images/screenshots would not be embedded in the document and we could easily produce a PDF - all without MS Word. It is also spiffy, it seems.</p> Bug #5037 (Resolved): Internationalizehttps://projects.ecoinformatics.org/ecoinfo/issues/50372010-06-02T18:11:10Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Collaborators with Dr. Chau Chin Lin have externalized strings in Morpho and made a Chinese (Taiwan) version of the language bundle. (source here: <a class="external" href="ftp://fire.tfri.gov.tw/morpho-1.8.0-MultiLanguage-beta1-src.zip">ftp://fire.tfri.gov.tw/morpho-1.8.0-MultiLanguage-beta1-src.zip</a>)</p>
<p>Incorporate these changes to the current Morpho codebase so that future internationalization efforts are as easy as authoring a new properties file.</p> Bug #4975 (Resolved): Morpho can't handle docid prefix containing a periodhttps://projects.ecoinformatics.org/ecoinfo/issues/49752010-05-04T16:53:07ZJim Regetzregetz@nceas.ucsb.edu
<p>A user just reported mysterious problems attempting to save and reopen documents in Morpho. It appears the problem is that her prefix contains a period, impairing Morpho's ability to parse the document id.</p>
Steps to reproduce:
<ul>
<li>Create a new profile, choosing a prefix that contains a period (foo.bar)</li>
<li>Create a new data package, and save locally</li>
<li>Restart Morpho</li>
</ul>
<p>The saved package doesn't appear in the Open Data Package window.</p>
<p>Also, .morpho/profiles/foo.bar/data looks like this:<br />`-- foo<br /> `-- bar.3.1</p>
<p>Rather than this:<br />`-- foo.bar<br /> `-- 3.1</p>
<p>Either Morpho needs to be smarter about parsing IDs, or if such a prefix is illegal, it shouldn't allow users to create one containing periods in the first place (and this should be documented).</p> Bug #4635 (Resolved): morpho attempts to display binary otherEntity objects as texthttps://projects.ecoinformatics.org/ecoinfo/issues/46352009-12-15T19:27:43ZJim Regetzregetz@nceas.ucsb.edu
<p>Morpho attempts to display otherEntity objects as text in the data table panel, even when they are binary files. Not only does this result in gibberish being displayed, but it can take a few seconds or longer if the file is large.</p>
<p>Two example DPs on KNB (note revision numbers):<br />nceas.958.1 -- contains an Excel file<br />nceas.960.1 -- contains a PDF file</p> Bug #4625 (Resolved): authenticate against KNB, switch source to DEV, and still have accesshttps://projects.ecoinformatics.org/ecoinfo/issues/46252009-12-11T02:07:26ZOliver Soongsoong@nceas.ucsb.edu
<p>I have packages that exist on DEV but not KNB. I start Morpho r4682 with KNB set as the metacat source and authenticate. I can confirm my packages are not on KNB. I then switch the metacat source to dev and open the package list and can see my packages. I can export the packages and extract the data. There was no re-authentication.</p> Bug #4620 (Resolved): Add handler for externally saving/opening an attached data objecthttps://projects.ecoinformatics.org/ecoinfo/issues/46202009-12-10T18:45:02ZJim Regetzregetz@nceas.ucsb.edu
<p>Imagine someone wants to quickly inspect the contents of a binary data file attached to a data package. Currently, the only way to do so is to export the entire DP, then drill down through cryptically named directories in the exported directory tree to manually locate and open the file. There should be a more straightforward way within Morpho to externally save or open a specific attached data object.</p>
<p>For the user, this should behave much like handling an email attachment: e.g., provide some sort of GUI element (button or menu option) that triggers a pop-up dialog presenting the option of saving the data object to disk or opening it with some other application. Note that the Metacat web registry already provides this functionality by presenting a "Download File" link for each attached entity in the DP, and allowing the web browser to handle the rest.</p>
<p>Ideally this functionality would apply not just to data tables, but also to other entity types (especially otherEntity).</p>
<p>Note: The button or menu text should probably be more along the lines of "export data" rather than "open data", otherwise users may be misled into thinking that editing/saving the object in the external application will actually save it within the DP.</p> Bug #4364 (Resolved): Convert otherEntity from registry to dataTablehttps://projects.ecoinformatics.org/ecoinfo/issues/43642009-09-03T21:48:20ZJing Taotao@nceas.ucsb.edu
<p>Currently, the web page registry generates eml document with otherEntity entity. But morpho mainly handle dataTable entity. So we need a mechanism to convert otherEntity to datatTable.</p> Bug #3473 (Resolved): allow user to attach, replace, or delete data table on existing entity desc...https://projects.ecoinformatics.org/ecoinfo/issues/34732008-08-20T22:24:52ZMatt Jonesjones@nceas.ucsb.edu
<p>Currently users can describe a data table in Morpho without importing the data. This causes the attributeList to be filled out, but the data table is not associated with the package. This feature used to exist, but apparently has been removed, and we need to add it back. Its a relatively simple matter of:</p>
<p>1) Add the data table to the profiles/data directory with an appropriate id number<br />2) Add an online distribution URL to the physical element of the entity description</p>
<p>This would look like this:<br /><distribution><br /> <online><url>ecogrid://knb/jones.354.1</url></online><br /></distribution></p>
<p>If Morpho was used to describe the data, there may already be an empty offline distribution description, which should be deleted if it is empty:<br /><distribution><br /> <offline><mediumName> </mediumName></offline><br /></distribution></p>
<p>It's not clear to me why this is being created in the first place -- we should probably stop creating it, but that is a separate issue.</p>
<p>3) This procedure assumes that the newly attached entity matches the existing entity and attribute list, which may be a bad assumption. We should probably test if they are in agreement (e.g., right # and types of columns)</p>
<p>4) Add a GUI element that allows one to attach a data table for an entity that currently doesn't have an attached table</p>
<p>That should do it.</p> Bug #1716 (Resolved): Feature requests for access screen in DPWhttps://projects.ecoinformatics.org/ecoinfo/issues/17162004-10-13T20:36:59ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Features requested by people at the KNB workshop for access screen in DPW:</p>
<p>1. Provide data and time of the last access list update - below the table which <br />displays the access list.</p>
<p>2. Put a search box on top of the access table - so that someone could search <br />for a user without going through the whole list.</p> Bug #1531 (Resolved): Import local eml documents to create new data packageshttps://projects.ecoinformatics.org/ecoinfo/issues/15312004-04-22T18:16:22ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Add support for importing local eml documents to create new data packages, <br />along with tabular data they describe (ideally validating data via the metadata <br />and/or validating the attribute metadata based on the new data)</p>
<p>Relevant part from Wade Sheldon's email....</p>
<p>"The only "problems" I had with the program were really ones of scope related <br />to using it within the context of an existing IM program in LTER or elsewhere <br />(the same issues I discussed with Chris and Chad years ago in Phoenix). Unless <br />I missed something big, your approach to working with metadata using Morpho <br />only allows two avenues for loading metadata documents: a) manual creation of <br />data packages de novo using forms and wizards, b) retrieval of existing <br />packages from Metacat. Because Morpho doesn't appear to offer any mechanism for <br />importing local metadata documents (i.e. eml files) in whole or in part, or <br />copying existing packages for editing and re-use for repeat submissions (i.e. <br />boilerplating or templating), there is no mechanism for coupling Morpho with <br />existing information systems or recouping effort already spent entering <br />metadata for long-term monitoring data sets (for which only temporal coverage, <br />abstract and title may have changed since the last submission).</p>
<p>I view this as a large impediment that may preclude use of Morpho in many IM <br />shops, at least for initial metadata entry and editing. In order to create <br />metadata more efficiently, many IMs will be forced to generate eml metadata for <br />new data sets via some other path that supports content re-use (e.g. raw xml <br />editing or generation from an RDBMS using scripting) and then load them into <br />Metacat via Harvester or another channel. This will limit use of Morpho to <br />metadata viewing/polishing and Metacat querying, which is a shame considering <br />all it has to offer users."</p> Bug #1521 (Resolved): Column name labels in Morpho Data Table Display disappearhttps://projects.ecoinformatics.org/ecoinfo/issues/15212004-04-19T19:04:41ZRick Reevesreeves@nceas.ucsb.edu
<p>Displaying a data table for an existing Morpho data package using the 'tabbed <br />dialog' display. The column widths are adjustable; if I slide one column to <br />the left (making the column to the left narrower), the (Boldface) column name <br />disappears, even though the column units do not completely disappear.</p>
<p>I originally discovered this when importing an existing table in which one of <br />the column units was MolesKilogramMeterSquared or some such very long string. <br />The long string was truncated in the table display, but the boldface column <br />name did not get displayed.</p> Bug #1518 (Resolved): Data Table Import Wizardhttps://projects.ecoinformatics.org/ecoinfo/issues/15182004-04-19T17:00:00ZEric Fegrausfegraus@nceas.ucsb.edu
<p>More examples are needed here...what categories/units/precision are species <br />presence/abscene (e.g. 0 or 1), plot numbers starting from 1...N wher N equals <br />the number of plots in a study, richness (i.e. the number of species in a <br />plot). I try to define richness and then have to associate it with an existing <br />standard unit type which i don't know. This gets very complex...</p> Bug #1198 (Resolved): Increase visibility & Descriptiveness of "more..." link under morpho citati...https://projects.ecoinformatics.org/ecoinfo/issues/11982003-11-04T00:04:44ZMatthew Brookebrooke@nceas.ucsb.edu
<p>more... link under morpho citation title/header (that opens package html pane) should be <br />made more visible and possibly more descriptive (possibly a graphical link?)</p> Bug #606 (Resolved): MetaViewer Path Display/Navigation Needs to be Finishedhttps://projects.ecoinformatics.org/ecoinfo/issues/6062002-09-28T16:50:04ZMatthew Brookebrooke@nceas.ucsb.edu
<p>Support classes for Path display in header area currently in place, but actual<br />display and associated method of navigation (links or buttons??) not yet implemented</p>