Morpho: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362001-07-21T00:34:43ZEcoinformatics Redmine
Redmine Bug #257 (Resolved): package wizard error when data file selectedhttps://projects.ecoinformatics.org/ecoinfo/issues/2572001-07-21T00:34:43ZMatt Jonesjones@nceas.ucsb.edu
<p>When stepping through the package wizard it prompts for a filename. If one<br />actually provides a filename, an exception is generated and neither the "Next" <br />nor "Previous" buttons work. Seems to be trying to treat the file as XML and<br />running into problems parsing it. Should really handle data files separately<br />from metadata files.</p>
<p>Towards that end, I suggest that FileSystemDataStore makes a separate subdir for<br />data and metadata (which has the added benefit of avoiding a bunch of sax parse<br />errors when searching). Maybe profiles/username/data and<br />profiles/username/metadata?</p> Bug #246 (Resolved): morpho hangs when metacat is not runninghttps://projects.ecoinformatics.org/ecoinfo/issues/2462001-07-09T23:55:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>Morpho will hang if metacat is not found on startup. It hangs after the<br />connection dialog.</p> Bug #245 (Resolved): need right click menu for query resultshttps://projects.ecoinformatics.org/ecoinfo/issues/2452001-07-06T17:47:18ZChad Berkleyberkley@nceas.ucsb.edu
<p>We need a menu that comes up when you right click on a result package. the<br />items in the menu should be:<br />1)copy this package to local from metacat<br />2)copy this package from metacat to local<br />3)sync this local and metacat copies<br />4)delete this package<br />5)change permissions on this package</p> Bug #241 (Resolved): Package Wizard does not upload data fileshttps://projects.ecoinformatics.org/ecoinfo/issues/2412001-06-20T18:34:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>The package wizard does not upload data files. metacat, at this time will not<br />allow the client to specify the id of the file so this functionality must wait<br />until metacat is updated.</p> Bug #237 (Resolved): exclude old revisions of packages from results displayhttps://projects.ecoinformatics.org/ecoinfo/issues/2372001-06-14T20:10:02ZMatt Jonesjones@nceas.ucsb.edu
<p>Need mechanism for not showing old revisions of data packages in the morpho<br />result set pane.</p>
<p>The second and third options are not mutually exclusive. It would actually be<br />pretty easy to maintain a running data structure that determines if two docs<br />have the same id except for revision, and only show the most recent. I think we<br />should pursue this approach, and not separate the archive unless needed.</p>
<p>Higgins' original message<br />-------------------------<br /> Chad and I were discussing the problem of what to do with previous<br />versions of revised local documents in Morpho (i.e. 3.1 when you revise<br />it and create 3.2)</p>
<p>Possibilities:</p>
<p>1) do nothing (current) - then old versions show up in result set tables<br />--- confusing<br />2) leave docs in data folder but filter in result set - requires looking<br />at all rows in resultset and finding most current<br />3) move older version out of data folder to a 'archive' folder<br />automatically when revision is created.</p>
<p>What are your thoughts?</p>
<p>Dan</p> Bug #231 (Resolved): Consistent searching problemshttps://projects.ecoinformatics.org/ecoinfo/issues/2312001-04-26T22:54:28ZDavid Blankmandblankman@lternet.edu
<p>Using the web interface for searching produced consistent and expected results. <br />Searching from Morpho, however, produced strange results. For example, using <br />simple catalog search with "title" selected, I entered the term "test" in the <br />SUBJECT field with author left empty. Morpho returned 1 document. When I <br />put "Blankman" in the AUTHOR field and selected the AND button, it returned 5 <br />documents (the expected result). I emailed Dan with screen shots showing Morpho <br />and Web results for the same search term.</p> Bug #230 (Resolved): Problems saving XML from Morpho to metacathttps://projects.ecoinformatics.org/ecoinfo/issues/2302001-04-26T18:18:54ZDavid Blankmandblankman@lternet.edu
<p>When Morpho generates an eml file such as resource, it appends a SYSTEM <br />reference as part of the doctype. This system refernce is of type file:// . <br />This reference will almost certainly be different from the SYSTEM attribute <br />stored in XNL_CATALOG. Somehow Morpho needs to strip out the SYSTEM attribute <br />before it attempts to submit the document to Matacat.</p> Bug #224 (Resolved): default ACL for data packageshttps://projects.ecoinformatics.org/ecoinfo/issues/2242001-04-10T00:48:49ZMatt Jonesjones@nceas.ucsb.edu
<p>When data packages are saved, they should automatically have a default ACL that<br />specifies who can have read and write access to the files. By default, Morpho<br />should send an ACL for all of the components with RW access for the submitter<br />and for all of the originators, but nobody else. Morpho should search the ldap<br />server for the originators to determine the appropriate username and authSystem<br />for the originator (this might be part of the data entry process for entering<br />users as originators).</p> Bug #220 (Resolved): Test Morpho and morpho installer on Windowshttps://projects.ecoinformatics.org/ecoinfo/issues/2202001-04-10T00:38:46ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to test Morpho and the Morpho Installer on Windows.</p> Bug #219 (Resolved): need ResultSet handling UIhttps://projects.ecoinformatics.org/ecoinfo/issues/2192001-04-10T00:36:12ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to redesign the resultset handling UI. Should take an XML document<br />representing the resultset, and create the data stroage mechanism for it. It<br />should then be able to display the resultset in either a tabbed pane, or a<br />window. Initially, the "My Data Packages" tab will be populated by a query for<br />all packages owned by the current user. Being able to rip tabs off as Windows<br />seems useful. There should be a UI widget for calling up (and refining) query<br />using the query composition dialog box. Various actions on resultset records<br />should call the Data Package module to handle opening, viewing, and changing. <br />Consider whether the resultset columns should be configurable or not (probably).</p> Bug #218 (Resolved): need query execution modulehttps://projects.ecoinformatics.org/ecoinfo/issues/2182001-04-10T00:31:49ZMatt Jonesjones@nceas.ucsb.edu
<p>Need a query execution module that takes a pathquery document as input and<br />returns a resultset (in XML format) as output. The same module should be used<br />for both network and local queries. Initially, this means it will execute an<br />XPath Query locally, and a metacat query on the net, and merge the results into<br />one resultset (presumably by accession#), indicating where each result record is<br />located). Eventually this might turn into a metacat search locally if John's<br />attempts to port metacat to a local client work out. This is related to the<br />resultset handling widget that Matt is working on.</p> Bug #216 (Resolved): combine subject and "all text" query screenshttps://projects.ecoinformatics.org/ecoinfo/issues/2162001-04-09T22:54:29ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to consolidate these two query screens. Allow some specific fields<br />(author, title, etc), and allow multiple booleans with arbitrary nesting. Also<br />allow completely free-text searches.</p> Bug #215 (Resolved): need query composition modulehttps://projects.ecoinformatics.org/ecoinfo/issues/2152001-04-09T22:52:43ZMatt Jonesjones@nceas.ucsb.edu
<p>need a module that can combine the results of multiple query screens into a<br />single pathquery document for submission to the query execution engine. We<br />agreed in March that this could be essentially a boolean AND (INTERSECT) among<br />the different query types (text, taxonomic, spatial, etc), but it needs to be<br />possible. The user interface for the query component might be a series of<br />tabbed panes ina dialog, so the entity that creates the dialog might also be the<br />one that combines the queries.</p> Bug #214 (Resolved): Redesign query pluginhttps://projects.ecoinformatics.org/ecoinfo/issues/2142001-04-09T22:45:47ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to redesign query plugin. Agreed that it should no longer be a "tab" in<br />the user interface, but rather should be called up as a dialog box. Each<br />resultset should be a window. Result sets list data sets (data packages) that<br />are returned from the query. Double clicking on a dataset record opens that<br />data set by calling the data package module that Chad is building. All types of<br />queries end up with a pathquery document, which is sent to a query execution<br />engine (regardless of whether it is local or remote). There is a distinct query<br />composition module that is used to combine different types of queries together<br />(like text and taxonomic).</p> Bug #210 (Resolved): redesign and implement XML editing/display componenthttps://projects.ecoinformatics.org/ecoinfo/issues/2102001-04-09T22:14:36ZMatt Jonesjones@nceas.ucsb.edu
<p>Focus of this redesign is on a highly intuitive user interface. If we have to<br />choose between usability and generality, choose usability. Explore the use of<br />HTML forms as reconfigurable forms, and other scripted layout approaches. Chris<br />and Dan agreed to look into this.</p>