drop old identifier when upgrading from 1.9.5 to 2.0.0
move the DataONE 1.0.0-SNAPSHOT
change upgrade scripts/routines to use 2.0.0 version number instead of 1.10.0
add User-Agent logging to support D1 requirements
only include 0.6.4 schemas for D1. Will also need to update this when we release whatever v1 ends up being.
remove ORE mapping from system metadata
include obsoletes and obsoletedBy for system metadatarepurpose the "provenance" table as the ORE mapping table for system metadata
add option for replicating system metadata (dataone)https://redmine.dataone.org/issues/1626also make sure the latest table changes are included in upgrade scripts
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.
do not drop nonexistent table (identifier is not in 1.9.3)
add support for temporal element query in pathqueryhttp://bugzilla.ecoinformatics.org/show_bug.cgi?id=2084
fixed bugs in listObjects
adding fields for additional system metadata info
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 schema to the catalog
updated folder name for schemas
do not attempt to drop 'identifier_id_seq' - it does not seem to exist
Added SQL lines for registering D1 schemas in the upgrade process.
Removing drop statements from upgrade scripts because the systemmetadata tabledoes not exist in 1.9.2, so these objects can't be dropped on upgrade.
added systemMetadata table to the upgrade scripts
Modified table structure to change identifiers table (previously unused) to represent a mapping between arbitrary string identifiers and metacat docids.More information in https://trac.dataone.org/ticket/361. Modifications toOracle schemas were made but not tested.