Metacat

Added code so that metacat administrator can delete any document.

Added the trailing '/' that was ommitted when XPATH queries included attributes.
This is a partial bug fix for:

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2052

Fixed bug in command-line mode which caused array index out of bounds exception.

Changed default maxHarvests value to 0. Added logic to ignore maxHarvests value when it is set to 0 or a negative number. This allows Harvester to run indefinitely without shutting down after reaching a maximum number of harvests. The previous default value of 30 would cause Harvester to terminate after 30 harvests.

Added code to check if the document is indexed yet! So entry into xml_queryresult is only made if the doc is in xml_index.

Added code such that an offset can be specified in metacat.properties for entering records into xml_queryresult table. The value of xml_returnfield.usage_count should be more than the value specified in metacat.properties for records to be entered into xml_queryresult. so if you want results for any combination of returnfields should be stored in xml_queryresult only after that combination has been requested 50 times, set this value to 50

Changes for entering new records into xml_queryresult:

1. Added a function which checks if there is a record exsists in xml_returnfield table for a given combination of return fields. If a record is found, the id for the record is returned. otherwise a new record is created in the xml_returnfield table and the id of the new record is returned....

Added code for updating xml_queryresult for action=delete and action=update

For both actions, the entries in xml_queryresult are deleted.
This works for action=update because deletion of entry is simple and the entries will be created again when the docid is part of a search result next time.

Added a function which gives back a string which is generated by sorting the returnfields requested for given query specifications

Modified the offset which is used for creating the resultset. This helps in fixing the 'more than 1000 enteries in IN query' bug on Oracle.

Added a check for eml2.0.1 documents in ContentTypeProvider.java