Use 2.0.7 version number in configuration/upgrade/docs (trunk, even though we will not be releasing 2.0.7 from trunk, we want to have the upgrade scripts included here)
ready Metacat for 2.0.6 release (docs, db version, build files etc).
use version 2.0.5
prep for 2.0.4 release
prep for 2.0.3 release
prep for 2.0.2 release by updating the version numbers.
include eml2.0.0beta4 DTD during Metacat build so that we can continue to accept (and validate) beta4 documents.This arose when testing Metacat as DataONE Coordinating Node where legacy documents are being housed in the CN.
register stmml-1.1 schema (distributed as part of EML 2.1.0) in an effort to avoid unnecessary network traffic or the failed retrieval of the stale XSD sitting on unofficial servers
remove DataONE schema reference in xml_catalog
change upgrade scripts/routines to use 2.0.0 version number instead of 1.10.0
only include 0.6.4 schemas for D1. Will also need to update this when we release whatever v1 ends up being.
Modified Metacat to build against the D1_SCHEMA_0_6_1 branch of the dataone schemas by incorporating the 0.6.1-SNAPSHOT version of d1_common and d1_libclient libraries, and refactoring Metacat code references to the d1 schema changed types.
Include the DataONE 0.6.0 type schema in the SQL schema and DTD loader script.
add support for EML 2.1.1
changes for new d1 schemas
changes for dataone .5 schema updates
updated DB scripts for D1 schemas
new values for mets namespace
added METS schemas to db scripts
Add support for getting the DataONE schemas from SVN and copying them into metacat's schema catalog. Still need to update the oracle scripts as well.
Add upgrade scripts for 1.9.2 (scheduler tables)
Update version to 1.9.1. Add nrs ldap properties to configuration.
Add the service registration xml schema to the database. The ecogrid build will add the schema files to the application (see seek)
Add schema locations for 2.1.0
Merge 1.9 changes into Head