Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-02-24T21:48:54ZEcoinformatics Redmine
Redmine Bug #4835 (Resolved): ESA review comments don't appear to users when viewing their documentshttps://projects.ecoinformatics.org/ecoinfo/issues/48352010-02-24T21:48:54ZJim Regetzregetz@nceas.ucsb.edu
<p>After the moderator enters review comments and sends a document back for revision, those comments are visible to the moderator in the left panel when viewing the document. However, when the original document submitter logs in and views that same document, the panel on the left reports "No reviews found".</p>
<p>I would imagine the submitter <strong>should</strong> be able to see the reviews, but in any case it certainly shouldn't say "No reviews found".</p> Bug #4818 (Resolved): ESA does not send an email to moderators when new document is added via reg...https://projects.ecoinformatics.org/ecoinfo/issues/48182010-02-22T17:50:42ZMichael Daigledaigle@nceas.ucsb.edu
<p>The register-dataset.cgi does not send an email when a new document is created via the ESA skin. It used to, and still should.</p> Bug #4698 (Resolved): ESA skin links are hard coded to data.esa.orghttps://projects.ecoinformatics.org/ecoinfo/issues/46982010-01-27T17:45:56ZMichael Daigledaigle@nceas.ucsb.edu
<p>The "ESA Registry" and "Search for Data" links in the ESA header are hard coded to go to data.esa.org. This causes issues on non-production systems when testing because you can inadvertently wind up on production.</p>
<p>The skin property values should be used for the home url.</p> Bug #4644 (Resolved): Convert build to pull eml from svn instead of cvshttps://projects.ecoinformatics.org/ecoinfo/issues/46442010-01-04T18:11:06ZMichael Daigledaigle@nceas.ucsb.edu
<p>updated build.xml to get eml from svn</p> Bug #4594 (Resolved): Cannot insert replication server via guihttps://projects.ecoinformatics.org/ecoinfo/issues/45942009-12-02T22:27:45ZMichael Daigledaigle@nceas.ucsb.edu
<p>When attempting to add a replication record via the gui at</p>
<pre><code>&lt;metacat_context_url&gt;/style/skins/dev/replControl.html</code></pre>
<p>metacat throws an error:</p>
<pre><code>duplicate key value violates unique constraint "xml_replication_pk"</code></pre> Bug #4558 (Resolved): Create validate and isAuthorized unit testshttps://projects.ecoinformatics.org/ecoinfo/issues/45582009-11-18T21:17:54ZMichael Daigledaigle@nceas.ucsb.edu
<p>A new isValid method was created on the metacat authentication service to make validate that a session is active. A new authority service was created to make sure the user for a session has permission on a resource. Unit tests need to be created for these.</p> Bug #4420 (Resolved): Enforce permissions for tpc workflow viewing and schedulinghttps://projects.ecoinformatics.org/ecoinfo/issues/44202009-09-28T16:20:38ZMichael Daigledaigle@nceas.ucsb.edu
<p>The existing squery functionality handles the visibility of workflows for the appropriate users.</p>
<p>The schedule link for each workflow should be active only for users that have read permissions on the associated kar file.</p> Bug #4167 (Resolved): Create Workflow Schedulerhttps://projects.ecoinformatics.org/ecoinfo/issues/41672009-06-16T15:01:41ZMichael Daigledaigle@nceas.ucsb.edu
<p>Create a scheduling web service that can schedule jobs for the kepler workflow engine.</p> Bug #4166 (Resolved): Create archive extraction functionalityhttps://projects.ecoinformatics.org/ecoinfo/issues/41662009-06-16T14:54:21ZMichael Daigledaigle@nceas.ucsb.edu
<p>Create the ability for metacat to read data from an archive. This will extract the archive an get the desired file.</p> Bug #4165 (Resolved): Create TPC Report web browse/search pageshttps://projects.ecoinformatics.org/ecoinfo/issues/41652009-06-16T14:48:57ZMichael Daigledaigle@nceas.ucsb.edu
<p>Create TPC search and browse skins in the sanparks skin.</p> Bug #4130 (Resolved): data tables in KNB display dataTable->physical->objectNamehttps://projects.ecoinformatics.org/ecoinfo/issues/41302009-06-08T18:56:18ZOliver Soongsoong@nceas.ucsb.edu
<p>KNB names data tables according to the objectName element within the physical element. By contrast, Kepler's EML 2 Dataset actor displays the entityName. This is mostly confusing for a few dataTables for which the entityName is not the same as the objectName. For example look at judithk.609.27, entityName=Dailyrainl2005.txt and objectName=rainfall2005.txt. I'm not sure which what the best way to handle this is, but it seems more intuitive to refer to the dataTable by the entityName rather than the objectName of the physical container.</p> Bug #3729 (Resolved): Add admin names as dropdown in configuration loginhttps://projects.ecoinformatics.org/ecoinfo/issues/37292009-01-07T16:32:33ZMichael Daigledaigle@nceas.ucsb.edu
<p>Currently the user has to type in the full distinguished admin name to log in using ldap.</p>
<p>Instead, it would be nice if a dropdown of existing configured admins was available.</p> Bug #2994 (Resolved): Create a properties file for use by JUnit Testshttps://projects.ecoinformatics.org/ecoinfo/issues/29942007-11-02T21:39:20ZChris Barteaubarteau@nceas.ucsb.edu
<p>Currently the build.xml file defines a few properties that are used for <br />ant token substitution in JUnit tests. An objective is to replace<br />compile-time token substitution with property lookups at runtime.<br />Since test properties (i.e. usernames and passwords) probably wouldn't be appropriate in the build.properties or metacate.properties file, a separate test.properties file would be a possible solution.</p> Bug #1674 (Resolved): Access control for eml-2.1.0 documentshttps://projects.ecoinformatics.org/ecoinfo/issues/16742004-09-10T22:12:47ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>This bug is continuing from bug# 968 and is dependent on bug # 1132</p>
<p>Access control to handle eml version 2.0.1 has been implemented. But when new <br />version of eml (v2.1.0) is released, access control for handling that version <br />will be required.</p> Bug #1530 (Resolved): cfg is readable by everyonehttps://projects.ecoinformatics.org/ecoinfo/issues/15302004-04-22T18:08:46ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>The *.cfg files in skins is reabable by everyone. This is not good as they <br />might contain information that should not be revealed to public.</p>
<p>Solution: Assign 600 permission to the file with 'apache' as the owner.</p>
<p>Trouble: what is the best way to implement this? This will be specific for KNB <br />only. So if code is added to build file, it will only be KNB specific. might <br />not be true for others.</p>
<p>Also another related issue is that this is a skin specific thing. And I was <br />wondering if we will be packaging all the skins that we have when we <br />package/ship Metacat. Shouldn't there be just a default skin which can be <br />copied by everybody else? And all the rest of the skins should be seperate <br />modules. But that was the case initially. So this issue might already have been <br />debated upon.</p>