Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362000-09-28T18:31:45ZEcoinformatics Redmine
Redmine Bug #155 (Resolved): revised UI for insert/update/delete to metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1552000-09-28T18:31:45ZMatt Jonesjones@nceas.ucsb.edu
<p>I think we need a revised user interface for inserting, updating, and deleting <br />metacat documents from within dmanclient. Insert and update should have very <br />natural interfaces that are only minor extensions of the 'Save as...' and <br />'Save' menu items, respectively. The current 'ID' assignment (from the <br />SaveToDatabase dialog) should be another field that parallels the filename field <br />in the Save As dialog. The 'ID Label' field in the SaveToDatabase dialog should <br />become a user-configurable preference, rather than something that is set for <br />every document individually. The 'Save As...' dialog should have a radio button <br />to choose whether to save locally or to the database (which enables/disables the <br />appropriate text entry fields).</p>
<p>This would mean eliminating the current 'Save to Database...' menu item and <br />dialog box. The 'delete' function from that dialog should become a menu choice <br />that is accessible from the querybean popup menu (right click on document in <br />resultset display, choose 'Delete', get confirmation dialog). The 'File to <br />Submit' part of the dialog should be eliminated entirely (users should open a <br />document to make a change). The 'Access Control' part of that dialog should <br />become a separate dialog that the user can open from the 'Save as...' dialog box <br />and by selecting a menu item from the querybean resultset context popup menu.</p> Bug #136 (Resolved): need XSL transform for pathqueryhttps://projects.ecoinformatics.org/ecoinfo/issues/1362000-09-22T22:07:42ZMatt Jonesjones@nceas.ucsb.edu
<p>As per our discussion last week, we need a new XSLT stylesheet that can<br />attractively display a query that is marked up in the pathquery.dtd format. <br />This presentation in HTML format can be used to show the "query summary" in the<br />query client for all queries.</p> Bug #127 (Resolved): change resultset display to be dataset orientedhttps://projects.ecoinformatics.org/ecoinfo/issues/1272000-09-20T18:40:19ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to make both the local and metacat resultset displays be "dataset <br />oriented", in that they should display a list of datasets rather than actual <br />hits on metadata documents. Each dataset is represented by a proxy metadata <br />document, generally eml-resource, but this should be configurable. Related <br />documents should be a hierarchical tree (collabsible) below the entry in the <br />table.</p> Bug #120 (Resolved): customizable resultset displayhttps://projects.ecoinformatics.org/ecoinfo/issues/1202000-09-20T18:17:21ZMatt Jonesjones@nceas.ucsb.edu
<p>Need a new feature that allows the user to configure which metadata fields <br />(doctype and pathexpr specification) are displayed in the resultset table that <br />results from each query. There should be a default that includes ecologically <br />relevant information about each data set, such as title, originator, and <br />keywords.</p> Bug #87 (Resolved): need ability to upload data with metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/872000-08-21T03:53:28ZMatt Jonesjones@nceas.ucsb.edu
<p>dmanclient currently does not upload data with the metadata that is being<br />registered. Need to add this feature so that users can decide whether or not to<br />upload the data. Probably should mediate this through metacat so that we have<br />the option of replacing the srb with other backend data storage, but it might be<br />more efficient to have the client talk directly to the srb. Not sure which is<br />best.</p> Bug #84 (Resolved): create javadoc documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/842000-08-21T03:31:22ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to create javadoc documentation for all public and protected methods and<br />fields in dmanclient. See the format used in xmltodb for formatting. These are<br />particulary needed for the querybean can dtclient packages, and the mde<br />documentation needs to be brought up to date.</p> Bug #83 (Resolved): remove hardcoded parser nameshttps://projects.ecoinformatics.org/ecoinfo/issues/832000-08-21T03:29:44ZMatt Jonesjones@nceas.ucsb.edu
<p>Some references to the SAX parser driver are hardcoded into the source code. <br />These shoulld be replaced with references to property values so that we don't<br />generate dependencies on particular parsers. An example to be changed is line<br />51 of querybean.ExternalQuery. There may be others.</p> Bug #76 (Resolved): local and network queries should work the samehttps://projects.ecoinformatics.org/ecoinfo/issues/762000-08-21T03:02:22ZMatt Jonesjones@nceas.ucsb.edu
<p>Currently, local and network queries search using different algorithms<br />(therefore they return a different set of documents), and they have differing<br />resultset structures. This should be changed so that the same resultset is used<br />for both types of queries, and so that a given query will return the same<br />resultset regardless of whether the document collection is local or network<br />based. This will improve the consistency of the search algorithm and make the<br />UI experience more predictable.</p> Bug #68 (Resolved): Query performance inhibits UI refreshhttps://projects.ecoinformatics.org/ecoinfo/issues/682000-08-19T00:47:47ZMatt Jonesjones@nceas.ucsb.edu
<p>When a query is launched, especially when local queries are running, there is a<br />very long delay before all of the appropriate windows refresh. This needs to be<br />fixed so that, after launching a query, it is run asynchronously (probably in<br />its own thread). This way, the UI code can refresh the windows immediately and<br />the user won't getthe feeling that the applicaiton is "frozen".</p>