Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362000-09-22T22:39:25ZEcoinformatics Redmine
Redmine Bug #147 (Resolved): return partial resultsetshttps://projects.ecoinformatics.org/ecoinfo/issues/1472000-09-22T22:39:25ZMatt Jonesjones@nceas.ucsb.edu
<p>Need feature in metacat that allows the client to specify if only a partial<br />resultset should be returned for a query. For example, the client should be<br />able to say "return records 1-100" and get only those records, then in another<br />pass say "return records 101-200", etc. The client may be required to submit<br />the query each time, or maybe there is a "Get next batch" action where a query<br />is <strong>cached</strong> in the session object and successive resultsets are returned to the<br />client as each batch is requested.</p> Bug #128 (Resolved): change resource public ID in the cataloghttps://projects.ecoinformatics.org/ecoinfo/issues/1282000-09-20T20:00:29ZChad Berkleyberkley@nceas.ucsb.edu
<p>The public ID of eml-resource documents needs to be changed in the catalog to<br />fit with the standard syntax of public IDs. It should be changed from<br />"resource" to "-//NCEAS//DTD resource-1.0//EN".</p> Bug #114 (Resolved): need interface for package info and downloadinghttps://projects.ecoinformatics.org/ecoinfo/issues/1142000-09-20T17:57:55ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to modify the current HTML interface for marine to allow display of the <br />"package" relationships and allow for downloading the overall dataset and the <br />specific metadata and data elements.</p> Bug #113 (Resolved): need "dataset oriented" html interface for resultshttps://projects.ecoinformatics.org/ecoinfo/issues/1132000-09-20T17:55:28ZMatt Jonesjones@nceas.ucsb.edu
<p>The current HTML interface displays result sets as a table, with all metadata <br />documents displayed. We need to modify this so that only "dataset" proxies are <br />displayed and the "related" metadata documents and data entities are displayed <br />as a collapsable hierarchical tree below each data set entry. For example:</p>
<ul>
<li>Dataset title
* general metadata
* data entity 1
* metadata for data entity 1
* data entity 2
* metadata for data entity 2</li>
</ul> Bug #111 (Resolved): reading large documents from metacat is slowhttps://projects.ecoinformatics.org/ecoinfo/issues/1112000-08-31T20:04:37ZMatt Jonesjones@nceas.ucsb.edu
<p>Reading documents from metacat seems to scale with document size, and gets to be<br />extremely slow for even medium sized documents. This is probably because we<br />recursively create a whole tree of objects representing every element and<br />attribute and test node when reading from the database, and this is an expensive<br />operation. Need to change this so that the conversion from the resultset into<br />an XML form is all done within a single instance of a class (probably within<br />DocumentImpl.java).</p> Bug #109 (Resolved): query speed slows as database growshttps://projects.ecoinformatics.org/ecoinfo/issues/1092000-08-30T18:36:33ZChad Berkleyberkley@nceas.ucsb.edu
<p>As the database grows in size, the speed at which a query result is returned<br />becomes greater. The database size to query result time ratio seems to grow at<br />a large rate. These results were obtained by the experiment described below:</p>
<blockquote>
<p>First of all, I wrote a script that adds an xml file to the database<br />repetitively using the command line INSERT feature of<br />DocumentImpl.java. I used this script for the following tests. When I<br />started, the database (under the jones username) had about 15 documents<br />in it and queries were returned pretty quickly (within 5 seconds or<br />so). I started by adding several different small xml document (<20<br />lines, <500 bytes) to the database about 10-15 times each. Query speed<br />was not noticably effected by adding these documents. It took about 5<br />seconds or so to add each document. Then I added a larger document (973<br />lines, 34,000 bytes). I added it about 10 times and it averaged about<br />30 seconds for the INSERT. After inserting this document query time was<br />noticable slower. It took about 10 seconds to return any simple query.<br />Next, I added a bohemith document (~5000 lines, 186,000 bytes). I added<br />this document only once. It took it 5 min. 20 sec. to insert. After<br />inserting this document, queries are now slowed to about 15-20<br />seconds/query. The database now contains 105 documents and xml_nodes<br />contains 37,449 records. I think we expected these results, and after<br />loading the 5000 line file, I actually expected it to take much longer<br />to retrieve a query.</p>
</blockquote> Bug #97 (Resolved): combine printExtendedSQL and printSQL methods into onehttps://projects.ecoinformatics.org/ecoinfo/issues/972000-08-23T22:18:44ZChad Berkleyberkley@nceas.ucsb.edu
<p>The printExtendedSQL and printSQL methods of QuerySpecification can be combined<br />into one method that works like printExtendedSQL but takes all of its parameters<br />except for doctype from the returnfield tag in the pathquery document.</p> Bug #63 (Resolved): methods in MetaCatServlet should be private not protectedhttps://projects.ecoinformatics.org/ecoinfo/issues/632000-08-18T17:26:50ZMatt Jonesjones@nceas.ucsb.edu
<p>Many of the helper methods in MetaCatServlet have been changed to "protected" <br />from their original "private" state. Most of these should be changed back to<br />"private" because they are not intended to be overridden by subclasses (for<br />example, handleGetOrPost). A couple should remain "protected", but only when<br />the method id specifically intended to be overridden (e.g., decodeMouseAction).</p> Bug #48 (Resolved): need an option to do xml indexing asynchronouslyhttps://projects.ecoinformatics.org/ecoinfo/issues/482000-07-28T22:06:14ZJivka Bojilovabojilova@nceas.ucsb.edu
<p>We need an option to do indexing of a document asynchronously, so the user<br />to get response quickly</p> Bug #31 (Resolved): need dataset id reference from metadatahttps://projects.ecoinformatics.org/ecoinfo/issues/312000-06-21T18:40:21ZDan Higginshiggins@nceas.ucsb.edu
<p>Need update to relations tag in order to obtain data id from metadata</p>