Add the code to add dataone schema v2 in the xml_catalog table.
use 2.5.0 for current DB version
Merge changes in the 2.4 branch into the trunk for the ORNL Mercury schema support. References https://projects.ecoinformatics.org/ecoinfo/issues/6619.
This schema is maintained by Jim Green (jgreen@iiaweb.com) and Ranjeet Devarakonda (devarakondar@ornl.gov). The schema uses a subset of the FGDC 1998 CSDGM elements, along with custom elements specific to the Mercury Metadata web application. Support is included in Metacat for Coordinating Node operations in the DataONE network.
add support for v2 DataONE API.
update to use 2.4.1 so the trunk has all artifacts for upgrades.
remove sensorML from the catalog since we don't actually ship it (yet?)
Add in Darwin Core schema support into xml_catalog, and insert it on upgrade as well. The schemas are cached in lib/schema/dwc, and Matt and Ben noted that the tdwg_basetypes.xsd and tdwg_dwctypes.xsd are part of the same namespace, but are xs:include'd rather than imported via namespace.
Add schema support for the DataONE, dublin Core, and Dryad schemas. Schemas get downloaded into lib/schema priior to jar and dist targets, and get loaded into xml_catalog on installation.
use v2.4.0 for documentation and upgrade scripts.
prep for 2.3.1 release
use 2.3.0 for this next release of metacat.
make sure all versions are using 2.2.2 of some sort -- thinking of making this release a 2.3.0 release because we will be branching/tagging from the trunk, not the 2.2.x branch.
prep project for 2.2.1 patch release -- will also merge to the 2.2.x branch.
prep for 2.2.0 release. include configuration value for metacatui deployment context.
[merge from branch to keep trunk up to date with upgrade history] prep for Metacat 2.1.1 release
upgrade to Metacat 2.1.0 on the trunk. This includes a new index_event table for storing indexing events that need to be reprocessed. https://projects.ecoinformatics.org/ecoinfo/issues/5944
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.
Merged in the D1_0_6_2_BRANCH changes that include the transition from ObjectFormat calls to ObjectFormatCache calls.
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 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
replace <script>.sql files with <script>-oracle.sql files since the base files are implicitly oracle scripts