Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362008-01-10T19:01:41ZEcoinformatics Redmine
Redmine Bug #3058 (Resolved): Generalize the reading of skin.configs in DBTransformhttps://projects.ecoinformatics.org/ecoinfo/issues/30582008-01-10T19:01:41ZChris Barteaubarteau@nceas.ucsb.edu
<p>Generalize the reading of skin.configs to read any property within a skin config property file and pass them all as parameters in a transformation (using DBTransfrom.java). Currently it is hardcoded to read/pass only 3: registryurl, registryname, and lsidauthority.</p> Bug #3057 (Resolved): The field "skinconfigs" in the MetacatUtil class is publichttps://projects.ecoinformatics.org/ecoinfo/issues/30572008-01-10T17:52:20ZChris Barteaubarteau@nceas.ucsb.edu
<p>The field "skinconfigs" in the MetacatUtil class is public, exposing it to uncontrolled access. The fix would be:<br />1) Make it private<br />2) Create setter and getter methods<br />3) Create a 'hasSkinConfig' method</p>
<p>and then modify the current usages in MetacatServlet (1 chg) and DBTransform (2 chgs).</p> Bug #3000 (Closed): Multiple Permissions Orders exist for Single Documenthttps://projects.ecoinformatics.org/ecoinfo/issues/30002007-11-08T17:41:40ZChris Barteaubarteau@nceas.ucsb.edu
<p>Everytime "setaccess" is called for a document on MetacatServlet, a new row is<br />created in the xml_access table. Each row has a perm_order field; thus, multiple<br />orders will exist for that document. This will be problematic in determining which order to apply, and in creating an accurate eml-access control list xml doc.</p>
<p>The problem stems from xml_access not being normalized. perm_order is 1-to-many<br />to perm_type. Solutions are (in order of preferance):<br />1) Normalize the table (create a parent table)<br />or 2) Update perm_order in all existing rows everytime there is an access mod.<br />or 3) Add a timestamp field and apply the order in the last entry.</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 #2993 (Resolved): Permission Order is always set to 'allowFirst'https://projects.ecoinformatics.org/ecoinfo/issues/29932007-11-02T20:11:30ZChris Barteaubarteau@nceas.ucsb.edu
<p>Permission Order is always set to 'allowFirst'. Even if you send 'denyFirst, it will save 'allowFirst' to the access table.</p> Bug #2985 (Resolved): Expand public access flag to the whole ACLhttps://projects.ecoinformatics.org/ecoinfo/issues/29852007-10-16T00:52:08ZChris Barteaubarteau@nceas.ucsb.edu
<p>Expand public access flag (from bug <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: Change permission to the update form (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2929">#2929</a>) in MetaCatServlet.readFromMetacat, to do more than just signal public read; provide the whole ACL.</p>
<p>This will help when we want to indicate that a user's allowed actions on the client side, such as providing 'Edit' buttons for records they might have write access for. We could use this now in other skins like the ESA skin, and the new web client we outlined in the kruger project for metadata entry would be able to make good use of it too.</p>
<p>Deliver the ACL table list for all documents.<br />Provide the ACL details in the param list (that's passed to the skin's view) rather than just publicAccess=[true|false].<br />Possibly an xtra method for this in DocumentImpl.<br />Set the format using EML access syntax described in eml-access.xsd</p>
<p>Modify:<br />MetaCatServlet.java<br />DocumentImpl.java (or other?)<br />fgdc_1.xsl</p> Bug #2984 (Closed): "AccessControlList.getACL" returns outdated XML structurehttps://projects.ecoinformatics.org/ecoinfo/issues/29842007-10-16T00:27:57ZChris Barteaubarteau@nceas.ucsb.edu
<p>The "MetCatServlet.handleGetAccessControlAction" calls another method "AccessControlList.getACL". The resulting XML does not seem to follow the structure defined the the XmlSchema of eml-access.xsd.</p>
<p>eMail from Matt regarding this:</p>
<p>It appears that Metacat is still generating the old beta6 version of EML <br />using that method, rather than following the EML 2.0.1 specification. I <br />do not think any software relies on this behavior, although we should <br />check to see if Morpho does -- that would be the only one I think. If <br />not, we should fix it to produce EML 2.0.1, but do so by changing the <br />method signature to allow clients to specify which version they want. <br />For example:</p>
<p>public Reader getACL(String docid, String namespace) throws<br /> NamespaceNotSupportedException;</p>
<p>The exception would be thrown when Metacat doesn't know how to generate <br />a particular ACL syntax. One reason I would want this is that there is <br />increasing use of SAML for ACL docs, and it would be a good thing to <br />have Metacat support ACL statements in SAML format as well as <br />eml-access. It would also allow us to support future eml versions.</p> Bug #2807 (Resolved): Data Set Upload for SAEONhttps://projects.ecoinformatics.org/ecoinfo/issues/28072007-03-28T17:44:01ZChris Barteaubarteau@nceas.ucsb.edu
<p>Create a web interface to upload data sets and metadata files for Kruger NP.<br />Includes login, and inserting new documents into metacat.</p>