Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362013-07-10T18:19:02ZEcoinformatics Redmine
Redmine Bug #6035 (Rejected): The system metadata table in a Metacat was messed up with the value of arch...https://projects.ecoinformatics.org/ecoinfo/issues/60352013-07-10T18:19:02ZJing Taotao@nceas.ucsb.edu
<p>In the mn-demo-4.test.dataone.org, I queried the systemmetadata table and got:</p>
<p>metacat=> select count(*) from systemmetadata where obsoleted_by is not null and archived=false;<br /> count <br />-------<br /> 4644<br />(1 row)</p>
<p>You see, there are 4644 documents which are not archived but have the obsoleted_by value. This is a contradiction.</p>
<p>Also, the xml_documents and xml_revisions table are messed up:</p>
<p>metacat=> select count(*) from xml_documents;<br /> count <br />-------<br /> 4998<br />(1 row)</p>
<p>metacat=> select count(*) from xml_revisions;<br /> count <br />-------<br /> 0</p>
<p>We need figure out why the metacat has this funny result.</p> Bug #6030 (Closed): Deleting a document causes the method itemAdded(ItemEvent<SystemMetadata> ent...https://projects.ecoinformatics.org/ecoinfo/issues/60302013-07-09T00:23:58ZJing Taotao@nceas.ucsb.edu
<p>When we delete a document from the Metacat, the method itemAdded in the in the SysteMetadataEventListener class (Metacat-index module) will be called because the haszelcast service. However, i figure the method will be call twice even though i only delete one document. This only happens for the deleting, the inserting works fine.</p>
<p>Here is the log:</p>
<p>Jul 08, 2013 5:17:25 PM edu.ucsb.nceas.metacat.index.SystemMetadataEventListener itemAdded<br />INFO: ===================================calling SystemMetadataEventListener.itemAdded method <br />Jul 08, 2013 5:17:25 PM edu.ucsb.nceas.metacat.index.SystemMetadataEventListener itemAdded<br />INFO: ===================================adding the document urn:uuid:e54bd099-e616-4f0d-be9d-f80df0f42354</p>
<p>........</p>
<p>Jul 08, 2013 5:17:25 PM edu.ucsb.nceas.metacat.index.SystemMetadataEventListener itemAdded<br />INFO: ===================================calling SystemMetadataEventListener.itemAdded method <br />Jul 08, 2013 5:17:25 PM edu.ucsb.nceas.metacat.index.SystemMetadataEventListener itemAdded<br />INFO: ===================================adding the document urn:uuid:e54bd099-e616-4f0d-be9d-f80df0f42354</p> Bug #6009 (Closed): Metacat uses "metacat.output" temp files for all read() operationshttps://projects.ecoinformatics.org/ecoinfo/issues/60092013-06-22T00:35:17Zben leinfelderleinfelder@nceas.ucsb.edu
<p>The KNB has 1.3 GB of these that have accumulated since ?.</p>
<p>There should be two scenarios:<br />-stream the contents from the metadata file on disk<br />-recompose the metadata file from the DB records to disk (/var/metacat/documents) then stream from that location.</p> Bug #6007 (Resolved): Registry uses filename from upload form to save in temporary directoryhttps://projects.ecoinformatics.org/ecoinfo/issues/60072013-06-21T19:22:02Zben leinfelderleinfelder@nceas.ucsb.edu
<p>This can cause collisions when a room of 22 people all submit a datapackage with the same data file name....</p>
<p>The registry should ensure that filenames it uses to write in a shared directory are unique.</p> Bug #6006 (Closed): Metacat admin screen requires metacat-index directorieshttps://projects.ecoinformatics.org/ecoinfo/issues/60062013-06-18T19:35:40Zben leinfelderleinfelder@nceas.ucsb.edu
<p>When configuring Metacat there is a dependency on metacat-index. This should be gracefully skipped if that webapp is not deployed. I believe it comes up when the solr-home directory is initialized.<br />This happens for CNs deploying Metacat in DataONE.</p> Bug #5997 (Closed): Restrict KNB trusted CAshttps://projects.ecoinformatics.org/ecoinfo/issues/59972013-06-05T18:00:12Zben leinfelderleinfelder@nceas.ucsb.edu
<p>Instead of trusting all commercial CAs, the KNB Member Node should only trust the DataONE and CILogon certificate authorities.</p>
<p>To see a list of all them that are (currently) trusted:<br /><pre>openssl s_client -connect knb.ecoinformatics.org:443</pre></p> Bug #5938 (Closed): sitemap format is deprecatedhttps://projects.ecoinformatics.org/ecoinfo/issues/59382013-05-22T02:34:25ZMatt Jonesjones@nceas.ucsb.edu
<p>The sitemap format used by Metacat has been deprecated, and should be updated to the current release (0.9) as published by <a class="external" href="http://sitemaps.org">http://sitemaps.org</a>.</p> Bug #5925 (Resolved): Clean up the jar files in the Metacat deploy directoryhttps://projects.ecoinformatics.org/ecoinfo/issues/59252013-04-25T18:13:32ZJing Taotao@nceas.ucsb.edu
<p>In the knb/WEB-INF/lib, i saw some jar files like:<br />spring-aop-2.5.5.jar spring-context-2.5.5.jar spring-core-2.5.5.jar spring-tx-2.5.5.jar spring-webmvc-2.5.5.jar<br />spring-beans-2.5.5.jar spring-context-support-2.5.5.jar spring-jdbc-2.5.5.jar spring-web-2.5.5.jar</p>
<p>imageio-ext-arcgrid-1.0.5.jar imageio-ext-gdaldted-1.0.5.jar imageio-ext-gdalenvihdr-1.0.5.jar imageio-ext-gdalmrsid-1.0.5.jar imageio-ext-imagereadmt-1.0.5.jar<br />imageio-ext-customstreams-1.0.5.jar imageio-ext-gdalecw-1.0.5.jar imageio-ext-gdalerdasimg-1.0.5.jar imageio-ext-gdalmrsidjp2-1.0.5.jar imageio-ext-tiff-1.0.5.jar<br />imageio-ext-gdal-bindings-1.4.5b.jar imageio-ext-gdalecwjp2-1.0.5.jar imageio-ext-gdalframework-1.0.5.jar imageio-ext-gdalnitf-1.0.5.jar imageio-ext-utilities-1.0.5.jar<br />imageio-ext-gdalarcbinarygrid-1.0.5.jar imageio-ext-gdalehdr-1.0.5.jar imageio-ext-gdalkakadujp2-1.0.5.jar imageio-ext-geocore-1.0.5.jar</p>
<p>and others.</p>
<p>We may need to clean them up.</p> Bug #5875 (Rejected): d1_cn_index_processor packagehttps://projects.ecoinformatics.org/ecoinfo/issues/58752013-02-21T23:55:30ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Have maven jar up the classes from d1_cn_index_processor for use in metacat</p> Bug #5833 (Closed): Temporary files aren'thttps://projects.ecoinformatics.org/ecoinfo/issues/58332013-01-30T01:14:31ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Detritus accumulates in the 'temporary' directory. Output files generated by read requests may persist for the lifetime of the application server and will not be cleaned on abnormal termination. Copies of data files are left in the 'uploads' directory.</p>
<p>Temporaries should at least be cleaned on startup/config.<br />Better to remove them immediately after use or schedule a definite deletion<br />Why are these operations staged through temporaries at all?<br />Why does metacat implement its own temporary file management rather than use app-server provided facilities?</p> Bug #5818 (Resolved): SOLR deployment on Lucene indexhttps://projects.ecoinformatics.org/ecoinfo/issues/58182013-01-24T21:54:51ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Enable optional deployment of SOLR interface to Lucene index</p> Bug #5817 (Resolved): MN query for Lucene indexhttps://projects.ecoinformatics.org/ecoinfo/issues/58172013-01-24T21:54:38ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Make Lucene index available via DataONE MN query interface</p> Bug #5816 (Resolved): REST for Lucene indexhttps://projects.ecoinformatics.org/ecoinfo/issues/58162013-01-24T21:54:23ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Make Lucene index available via REST</p> Bug #5815 (Resolved): Integrate Lucene indexinghttps://projects.ecoinformatics.org/ecoinfo/issues/58152013-01-24T21:54:08ZBrendan Hahnhahn@nceas.ucsb.edu
<p>Add a Lucene index and query interface for metacat docs.</p> Bug #5813 (Resolved): Partition document storage on filesystemhttps://projects.ecoinformatics.org/ecoinfo/issues/58132013-01-24T20:35:22Zben leinfelderleinfelder@nceas.ucsb.edu
<p>There has been concern that ALL xml documents and revisions are saved into a single directory on the filesystem. There is a practical limit to the number of files any one directory can support (though I feel like we don't have definitive numbers on what those limits are exactly).</p>
<p>It would be wise if we could distribute our document/data storage across multiple directories. We could break the file name into subdirectory pieces, or do something more random. Suggestions appreciated.</p>