Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362004-09-13T21:21:00ZEcoinformatics Redmine
Redmine Bug #1682 (Resolved): Error in handling of docid formatshttps://projects.ecoinformatics.org/ecoinfo/issues/16822004-09-13T21:21:00ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Errors generated when insert, update and delete actions tried with docid <br />formats such as a.c.t.t.c.a.1.1</p> Bug #1681 (Resolved): Access not checked while file uploadinghttps://projects.ecoinformatics.org/ecoinfo/issues/16812004-09-13T21:14:52ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>When user with id X uploads data as act.1.1, another user with id Y can upload <br />act.1.2 without requiring access for act.1.1</p> Bug #1680 (Resolved): New functions in Metacat Client APIhttps://projects.ecoinformatics.org/ecoinfo/issues/16802004-09-13T21:13:11ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>.. for read inline data and uploading data needed.</p> Bug #1679 (Resolved): Random string entry in action=insert leads to hanging of codehttps://projects.ecoinformatics.org/ecoinfo/issues/16792004-09-13T21:10:32ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Input of following type, hangs metacat code <br /> <a class="external" href="http://metacat_url?action=insert&docid=act.1.1&doctext=random_string">http://metacat_url?action=insert&docid=act.1.1&doctext=random_string</a><br /> <a class="external" href="http://metacat_url?action=insert&docid=act.1.1&doctext=&lt;random_string">http://metacat_url?action=insert&docid=act.1.1&doctext=&lt;random_string</a>></p> Bug #1671 (Resolved): editing registry entry deletes keywordshttps://projects.ecoinformatics.org/ecoinfo/issues/16712004-09-03T22:58:31ZMatt Jonesjones@nceas.ucsb.edu
<p>When a registry entry has keywords and the entry is edited through the web site,<br />the keywords are not propogated to the new form, and therefore are lost in the<br />process of editing. This was probably introduced when keyword fields in the<br />form were changed to be dynamically generated using javascript (rather than<br />being a fixed number as before).</p> Bug #1658 (Resolved): tracking bug for 1.4.0 releasehttps://projects.ecoinformatics.org/ecoinfo/issues/16582004-08-20T20:00:48ZMatt Jonesjones@nceas.ucsb.edu
<p>This is the tracking bug for last minute details for the 1.4.0 release of<br />metacat. Before releasing, we need to:</p>
<p>1) Review and revise documentation, including installation instructions<br />2) Check that the harvester code is properly integrated and documented<br />3) Create a function for re-indexing xml_nodes into xml_index<br />3a) make sure the new xml_index with larger path is created in each db<br />4) finish testing access control support for 2.0.1<br />5) change use_xmlindex to 'true'<br />6) develop a test case for inserting and reading both an EML 2.0.0 doc and an<br />EML 2.0.1 doc (the access control tests may satisfy this)<br />7) Update README with appropriate contributors list</p> Bug #1467 (Resolved): getprincipals action returns referal entries in url formhttps://projects.ecoinformatics.org/ecoinfo/issues/14672004-04-09T06:45:08ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>getprincipals right now returns urls instead of identities in case of referals. <br />So for example in case of LTER we get back, <br />ldap://knb.lternet.edu:389/uid=sacker1,o=lter,dc=ecoinformatics,dc=org,o=LTER,dc<br />=ecoinformatics,dc=org<br />What we want is:<br />uid=sacker1,o=lter,dc=ecoinformatics,dc=org</p> Bug #1466 (Resolved): getprinicpals action doesnt return trees for UCNRS and PISCOhttps://projects.ecoinformatics.org/ecoinfo/issues/14662004-04-09T06:15:54ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>The getprincipals right now return trees for all organizations except UCNRS and <br />PISCO. A similar scenario can be generated using ldapsearch command. <br />What is happening right now is <br />ldapsearch -C -x -b dc=ecoinformatics,dc=org objectClass=inetOrgPerson<br />What is wanted is <br />ldapsearch -C -MM -x -b dc=ecoinformatics,dc=org objectClass=inetOrgPerson</p>
<p>The difference is -MM arguement. From ldapsearch man page -MM does the <br />following:<br />Enable manage DSA IT control. -MM makes control critical.</p>
<p>Couldn't find out what that means. But found a call to make the search critical <br />and hence a hope of passing -MM arguement. But hopes dashed when found that <br />code uses javax.naming.directory classes right now. <br />Whereas call is found in javax.naming.ldap. These classes were created to <br />provide support for LDAPv3 extended operations and controls. Hence maybe the <br />functionality that search can be made critical.</p>
<p>Anyway more research needed. Maybe javax.naming.directory can be used in <br />conjunction with javax.naming.ldap.</p> Bug #1451 (Resolved): null returndoctype fails to return all documentshttps://projects.ecoinformatics.org/ecoinfo/issues/14512004-04-05T23:23:26ZMatt Jonesjones@nceas.ucsb.edu
<p>When the pathquery "returndoctype" filed is omitted, metacat is supposed to<br />return all matching documents. In fact, no documents are returned under version<br />1.3.1, because it filters out all documents in the returndoctype listt is empty<br />or null. Fixing this will require chaning the logic in the DBQuery module to<br />include results even when the returndoctype field is not present.</p> Bug #1427 (Resolved): xml_index constrains depth of paths that can be insertedhttps://projects.ecoinformatics.org/ecoinfo/issues/14272004-03-30T22:20:05ZMatt Jonesjones@nceas.ucsb.edu
<p>When an XML document contains a deeply nested structure, metacat accepts the<br />document for storage in xml_nodes, but during the subsequent indexing phase, it<br />throws an exception because the composite paths to the deep nodes are too long<br />to fit in the space allocated for the paths in the column in the xml_index<br />table. This column was limited to a a few hundred characters so that it is<br />indexable (Oracle had a limit on the total indexable width of columns).</p>
<p>These problems were discovered and reported by Wade Sheldon (GCE LTER) when he<br />submitted EML documents with fully filled out taxonomic coverage entries. We<br />definitely need to support realistically filled out EML documents.</p>
<p>So, two possible solutions:<br /> 1) make the column much wider<br /> -- this is a partial solution, because the column still might not be big <br /> enough for very deep docs or docs with long element names<br /> -- if its wider, it may not be indexable, which is why it exists<br /> 2) eliminate the dependency on the xml_index table altogether<br /> -- the recursive search needed isn't that much slower, and may not be<br /> slower at all as we tune the database<br /> -- insert/update/delete should be MUCH faster<br /> -- simpler database structure</p>
<p>We have decided to pursue (2) above because of the advantages listed. Rather<br />than completely removing the xml_index code, we are going to make it an option<br />whether or not it is used, but by default ship with it turned off.</p> Bug #1390 (Resolved): add UCNRS to the ldapweb.cgi management listshttps://projects.ecoinformatics.org/ecoinfo/issues/13902004-03-24T22:15:24ZMatt Jonesjones@nceas.ucsb.edu
<p>The UCNRS ldap tree can not be managed through the web scripts now, partly<br />because these entries are in a different tree (o=ucnrs.org) than ecoinfo<br />(dc=ecoinformatics,dc=org). Need to make the changes that allow creation of new<br />LDAP entries for UCNRS and changing and resetting the passwords for these accounts.</p> Bug #1346 (Resolved): The results sent back in response to query should be sortedhttps://projects.ecoinformatics.org/ecoinfo/issues/13462004-02-12T23:00:28ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>The results that are sent back to client from Metacat are random. It would be <br />helpful if the records are sorted. Maybe it would be even more helpful if you <br />could specify the field based on which they should be sorted.</p> Bug #1295 (Resolved): Registry: Button texts are ambiguous and need to be changed.https://projects.ecoinformatics.org/ecoinfo/issues/12952004-02-02T22:38:27ZSaurabh Gargsgarg@nceas.ucsb.edu
<p>Change the text of the buttons to following:</p>
<p><del>> Review Entry<br /></del>> Change reset to 'Cancel'</p>
<p><del>> Yes, submit.<br /></del>> No, go back to editing.</p> Bug #1235 (Resolved): enable passthrough parameters to support stysheet paramshttps://projects.ecoinformatics.org/ecoinfo/issues/12352003-12-10T09:22:21ZMatt Jonesjones@nceas.ucsb.edu
<p>Many different skins for metacat could take advantage of custom parameters in<br />the stylesheets. For example the OBFS registry has a need to add Edit and<br />Delete buttons to the resultset listing. A simple way to do this is to pass<br />paramters through metacat into the stylesheets to control the behavior of the<br />rendered output. This is currently hindered by the DBQuery.createSQuery()<br />function because it currently interprets all unknown parameters as XPaths that<br />should be written as an additional constraint in an squery. We need to<br />partially circumvent this feature in order for passthrough stlesheet parameters<br />to work.</p> Bug #1230 (Resolved): move metacat.properties out of jar filehttps://projects.ecoinformatics.org/ecoinfo/issues/12302003-12-05T20:56:06ZMatt Jonesjones@nceas.ucsb.edu
<p>The current configuration file for metacat (metacat.properties) is installed<br />inside of the metacat.jar JAR file. This makes changing the configuration<br />difficult for most users. Need to move it out of the jar, probably to a<br />location like ${context}/WEB-INF/metacat.properties. I have started code to<br />accomplish this change.</p>