Metacat: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362001-10-16T18:29:20ZEcoinformatics Redmine
Redmine Bug #298 (Resolved): Problem with Export functionhttps://projects.ecoinformatics.org/ecoinfo/issues/2982001-10-16T18:29:20ZDan Higginshiggins@nceas.ucsb.edu
<p>If a dataset which includes a data document is inserted into production Metacat<br />context and then 'Exported' the export of the data document appears to work<br />(because there is also a local copy?) However, if local dataset is deleted and<br />then one 'Exports' from Metacat, the data document contains an error message<br />rather than the data!</p>
<p>It is currently not clear whether this is a Morpho or a Metacat problem. Thus,<br />this error has been entered to both.</p> Bug #293 (Resolved): Extend Metacat.pm perl module to Metacathttps://projects.ecoinformatics.org/ecoinfo/issues/2932001-10-08T05:17:45ZChris Jonescjones@nceas.ucsb.edu
<p>Add getCookie subroutine to Metacat.pm so that the index.cgi that calls login()<br />can pass the JSESSIONID to the browser for maintaining state.</p> Bug #291 (Resolved): knb context of Metacat fails to find eml-attribute dtdhttps://projects.ecoinformatics.org/ecoinfo/issues/2912001-10-03T17:04:45ZDan Higginshiggins@nceas.ucsb.edu
<p>Inserting a new datapackage to Metacat from Morpho fails with message about not<br />being able to find eml-attribute dtd.</p> Bug #280 (Resolved): provide support for multiple UI styles in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/2802001-09-14T20:26:54ZMatt Jonesjones@nceas.ucsb.edu
<p>Metacat currently allows a mapping between one document type to a particular<br />stylesheet for HTML transformation. We want to be able to use the same metacat<br />instance for presenting multiple user interface perspecitves, like a KNB<br />interface, an NRS interface, and a OBFS interface.</p>
<p>Proposed solution: remove all references to XSL stylesheets from the<br />xml_catalog table, and instead provide this information in a series of metacat<br />configuration files, which I will call a "style set". Each style set will have a<br />name, and will specify the mapping between a particular document type and the<br />stylesheet that should be used to transform that type into HTML. It will also<br />provide a default style in case there isn't an exact match. The main<br />metacat.properties file will have a property that indicates which user interface<br />style is the default. In addition, the semantics of the qformat parameter to<br />metacat will be extended, so that the name of a style set can be provided in<br />qformat, and that name will then determine the set of style sheets to use.</p>
<p>This change will allow a single metacat instance to display mutiple user interfaces.</p>
<p>The style set configuration file might be something like this:<br /><?xml version="1.0"?><br /><style-set name="knb"><br /> <default-style>file://styles/generic-style.xsl</default-style><br /> <stylesheet src="file://styles/dataset.xsl"><br /> <doctype>-//NCEAS//eml-dataset-2.0//EN</doctype><br /> <doctype>-//NCEAS//eml-dataset//EN</doctype><br /> <doctype>-//NCEAS//eml-resource//EN</doctype><br /> </stylesheet><br /> <stylesheet src="file://styles/access.xsl"><br /> <doctype>-//NCEAS//eml-access-2.0//EN</doctype><br /> </stylesheet><br /></style-set></p>
<p>and would be found in a file named "knb.xml" in xmltodb/lib.</p> Bug #279 (Resolved): entity resolver sometimes failshttps://projects.ecoinformatics.org/ecoinfo/issues/2792001-09-12T18:56:29ZMatt Jonesjones@nceas.ucsb.edu
<p>The DBEntityResolver is used durning XML document parsing to find the locations<br />of the DTDs to be used to validate a document. The current entity resolver<br />works for the DOCTYPE entity and properly finds the proper dtd from the metacat<br />dtd directory. However, when that dtd references another using an external<br />entity, that secondary included DTD is not resolved. This is becuase the entity<br />resolver takes a very document centric view of what it should do, and needs to<br />be fixed to resolve all entities.</p>
<p>External entities generally use a relative SYSTEM id of the form:<br /> <!ENTITY % resource SYSTEM "./eml-resource-2.0.dtd"><br />This system id needs to be interpreted and mapped to a file that is stored in<br />the metacat dtd directory. Because the system ID can be relative, we need to<br />register both the public ID and the relative system IDs (possibly two or more<br />forms ("eml-resource.dtd", and "./eml-resource.dtd") for mapping to the true<br />file location.</p>
<p>In addition, the Entity resolver class depends on DBSAXHandler to find the<br />public ID. This may be an obsolete requirement based on older, buggy xerces<br />parsers. We need to update Xerces and see if we still need this sax handler<br />reference to make the resolver work correctly. Theoretically at least all of<br />the needed info should be contained inthe "resolveEntity(String publicID, String<br />systemID)" call that is made to the resolver. If the sax handler is no logner<br />needed for proper resolution, we should eliminate it to simplify the<br />DBEntityResolver class.</p> Bug #272 (Resolved): install production root LDAP serverhttps://projects.ecoinformatics.org/ecoinfo/issues/2722001-08-31T17:12:24ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to install the 'production' root LDAP server on ecoinfo so that it can be<br />used by the production metacat server. The hostname will be<br />'ldap.ecoinformatics.org'. It should be accessible via SSL.</p>
<p>This new LDAP server will use the DN convention that bojilova has worked out. It<br />will be of the form:<br /> uid=jones,o=NCEAS,dc=ecoinformatics,dc=org<br /> uid=oeddins,o=LTER,dc=ecoinformatics,dc=org</p>
<p>The organization component (o=NCEAS) will be used to determine referrals from<br />one LDAP server to another. By default, all queries will be handled by the<br />ecoinfo root LDAP server, unless the organization is handled by referral (e.g.,<br />o=LTER), in which case it will be referred.</p>
<p>Need to coordinate this with installation of an LDAP interface on the LTER<br />personell database.</p> Bug #271 (Resolved): production metacat installhttps://projects.ecoinformatics.org/ecoinfo/issues/2712001-08-31T17:06:01ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to take the current release of metacat and install a 'production' version<br />on ecoinfo so that it is completely distinct from our development versions<br />(located on dev). This production version should be integrated with a<br />production version at LTERnet and should replicate all info between the two systems.</p> Bug #270 (Resolved): change LDAP interface to get complete DN from clienthttps://projects.ecoinformatics.org/ecoinfo/issues/2702001-08-31T16:52:47ZMatt Jonesjones@nceas.ucsb.edu
<p>Metacat currently retrieves a userid from the client, and uses this along with a<br />single configuarable baseDN parameter to determine the string that is used to<br />look up the user in LDAP, and ultimately to authenticate them. This will not<br />work if we have LDAP configured to refer some authentication to alternate<br />servers (like the LTER personell db). In the new scheme, metacat MUST get the<br />complete DN from the client, so that it can be passed to the correct LDAP server<br />for authentication.</p>
<p>So, instead of passing:<br /> jones<br />Morpho must pass:<br /> uid=jones,o=NCEAS,dc=ecoinformatics,dc=org<br />in order for metacat to use referral properly.</p> Bug #248 (Resolved): id finder needed for metacathttps://projects.ecoinformatics.org/ecoinfo/issues/2482001-07-10T23:40:46ZChad Berkleyberkley@nceas.ucsb.edu
<p>Metacat needs a utility function so that morpho can query it and find the last <br />id used by a specific user. right now, if a user goes to another computer, his <br />id sequence is reset, causing id conflicts when the documents are uploaded. <br />the <profile>.xml file in morpho needs to be able to be updated with the latest <br />id that was used in metacat. this should be done dynamically when morpho <br />starts up. I will also enter a bug for morpho for this.</p> Bug #199 (Resolved): changes in Access Control mechanismhttps://projects.ecoinformatics.org/ecoinfo/issues/1992001-04-09T20:04:56ZMatt Jonesjones@nceas.ucsb.edu
<p>The "public" attribute has been elimanted form eml-access. Need to accomodate<br />this by searching for a special "public" user who can be granted permissions. <br />This user can be considered a group that consists of all users on the system. <br />Also need to change mechanism for associating access rights to docids because<br />now we need to use the triples found in the new "resource" module. There will<br />need to be parallel changes on Morpho.</p> Bug #189 (Resolved): add <, >, and numeric = operators to pathquery languagehttps://projects.ecoinformatics.org/ecoinfo/issues/1892001-04-09T19:33:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to have less than, greater than, and numeric equals operator support in the<br />pathquery language so that we can do spatial and othe rimportant queries.</p> Bug #185 (Resolved): replication security holehttps://projects.ecoinformatics.org/ecoinfo/issues/1852001-04-09T19:10:15ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to fix security hole in Metacat replication feature where host name can be<br />spoofed, allowing complete access to the server's data.</p> Bug #182 (Resolved): uneeded field in xml_documentshttps://projects.ecoinformatics.org/ecoinfo/issues/1822001-01-24T18:28:13ZChad Berkleyberkley@nceas.ucsb.edu
<p>There is a field, 'updated', in xml_documents that is not used for anything. It<br />should be removed from the xmltables.sql script.</p> Bug #180 (Resolved): return of DTD comments with documents should be eliminatedhttps://projects.ecoinformatics.org/ecoinfo/issues/1802001-01-08T20:07:31ZDan Higginshiggins@nceas.ucsb.edu
<p>Currently, if I submit an XML metadata document to Metacat and then retrieve <br />that document, the retrieved document contains<br />comment fields from its DTD that were NOT present in the original document. A <br />user should retrieve a document<br />from metacat that is a duplicate of the one submitted and comments in the DTD <br />should remain in the DTD only. Putting them into a returned<br />document tends to confuse the user into thinking that the retrieved document is <br />not the same one as submitted.</p> Bug #178 (Resolved): error in the processing of relation urlshttps://projects.ecoinformatics.org/ecoinfo/issues/1782000-12-08T19:00:00ZChad Berkleyberkley@nceas.ucsb.edu
<p>There is an error in DBQuery.findDocuments() where it is assumed that the next<br />parameter after a / in a url is the docid of a document. This was an old piece<br />of code that somehow got left in. It needs to be replaced with code that allows<br />for the format metacat://dev.nceas.ucsb.edu/berkley/servlet/metacat?docid=xxx<br />instead of just metacat://dev.nceas.ucsb.edu?docid=xxx</p>