Metacat

Add a client-side check: if user does not enter any search values, prompt the user with a dialog box to confirm that the user wishes to go ahead with a search for all documents. This is equivalent to the behavior in the simple search box.

Added a hidden input field for siteValue with a value of "ALLSITES". This is a substitute for the siteValue drop-down list that is used at LTER whose default value is also "ALLSITES". Either the hidden input field or the drop-down list should be commented-out, but not both. (This is documented in the internal comments.)

Modify the bean's get() methods that return String values to trim white space off the string prior to returning it. This is so that input fields that contain only white space will not be treated as valid search values.

Updated names of jar files in build.xml for LSID support.

Added axis servlet defs in web.xml

New libraries for axis 1.3.

New SQL tables and db upgrade scripts that define a new table stucture for identifiers and delete the previously unused accession_number table. This is in anticipation of supporting LSID identifiers. Currently these tables are unused by the servlet but are in place for discussion.

Cleaned up AccessionNumber class to get rid of unused methods. It seems the entire accession_number table is no longer used but has not been deleted from the build. Will do in subsequent commit.

1. Modified buildIndex() so that only one connection is used for both indexing nodes and indexing paths.
2. Modified the indexing algo so that indexing of paths is done while nodes are being indexed. Results in a much faster indexing algo
3. Replaced access to NodeRecord.<variable> with NodeRecord.<getVariable>

Change the code level of the MetacatHasDoc harvester operation from "Warning" to "Info". This is to reduce the amount of diagnostic output generated in the email reports to the site contact.

Change the maximum code level reported to the site contact from "info" to "notice". This is to reduce the amount of diagnostic output generated in the email reports to the site contact. Diagnositcs of type "error", "warning", and "notice" will be sent to the site contact, while messages of type "info" and "debug" will not (but they will still be sent to the Harvester Administrator).