prep for 2.2.0 release. include configuration value for metacatui deployment context.
initialize the SOLR home directory if it does not already exist.
include dataone.contactSubject in backup properties so it will be "remembered" during upgrades.
correct the metacat.properties help anchors.
correct the "?" links in the admin pages to the docs pages that are deployed as part of metacat.
use ObjectFormatInfo libclient utility to look up mimeType and filename extension during get() calls. Configurable mapping file is deployed by default to /var/metacat/dataone where it can then be augmented as needed. This location is controlled in the metacat.properties file (which is injected into the DataONE Settings values during weapp intitialization)....
Globally change the property 'dataone.memberNodeId' to 'dataone.nodeId'. This is more useful for both MNs and CNs implemented in Metacat. Also, change D1NodeService.getLogRecords() to return log entries with the actual node id rather than the IP address (looks like a cut/paste error)....
include systemmetadata and ore generation flags as "remembered" configuration values for the admin UI.
generate ORE maps only once -- and persist the flag to the main backup properties so that subsequent Metacat upgrades remember this value.
store D1 configuration properties in the main backup so that they persist between upgrades.
remove the D1 configuration group (header)
remove D1 configuration -- it has its own admin screen now
Removed extraneous comments.
Add boolean field for synchronization status.
A configuration section for DataONE Member Node properties.
include MetacatHandlerPlugin interface so that other projects [semtools] can extend the actions handled by Metcat without editing the codebase directly. The SemtoolsPlugin is the prototype for this and can be registered using the Metacat admin interface. Note that the plugin implementation class and supporting jars must be included in the webapp in order for the request to be handled correctly (the semtools build is injecting these as part of it's build process).
Persist skin properties across installations
include datamanager configuration in the /admin utility (for FIRST project...and others down the road)
Remove application.default-style from the global configuration screen and activate it in the skins configuration.
change generic authentication properties from ldap.* to auth.*
Add application.tempDir to configuration form and documentation.
Add functionality to write and read metadata documents to and from the file system.
Remove sqlserver references. Add some help locations.
Add TODO comment
Add help file sections and move application.tomcatDir to replication.logdir
move allowed submitters and denied submitters to main properties configuration section.
add deploy directory section
Add a value element to form dropdowns
Merge 1.9 changes into Head