Metacat

use a temporary table to calculate the maximum revision for a given docid and use that when setting the accessfileid during upgrade. the query plan for the all-in-one statement must be brutal as it's been running for 4 hours at this point....

do not insert duplicate GUID entries when adding rows from the xml_revisions table

add "IF EXISTS" clause to identifier table drop in case it does not exist on the given deployment (as is the case on the KNB)

use UTC serialization for log entries so that the timestamp, not just the date, is preserved
https://redmine.dataone.org/issues/2257

edited the configuration docs, swapped in new fully-configured screen shot
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5516

Update the MNodeServiceTest to test the validity of the node document returned by getCapabilities() by parsing it with the TypeMarshaller.

Update the D1Admin class to set the dataone.contactSubject property. I've added the property to the http request to be added to the JSP form, but for now am setting the property using the dataone.subject field value. Not sure if we want to expose the contact subject in the form yet or not.

marked the properties that are only editable manually in metacat.properties
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5516

Add the dataone.contactSubject property to be used when getCapabilities() returns the MN node instance.

In MN.getCapabilities(), the required contact subject was not being added to the node instance from the dataone properties. Add it in.