increase amount of text the 'xml_path_index.path' column can accommodate. I was seeing errors like this during indexing:knb 20120312-11:42:05: [ERROR]: DocumentImpl.buildIndex - SQL Exception while indexing document knb-lter-and.3147 : ERROR: value too long for type character varying(1000) [edu.ucsb.nceas.metacat.DocumentImpl]
eliminate the cross product that occurred when updating xml_access with a join
semicolons!
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)
Added DOI generation to the 2.0.0 upgrade process. To succeed, this script must be run on a fresh 2.0.0 database, or on a 1.9.5 version database, as those are the only ways to get the needed foreign keys to be marked as deferrable. The identifier conversion must be turned on by setting correct properties in metacat.properties. See the comments in GenerateGlobalIdentifiers for details. By default, conversion is set to false in the properties file. If you want to convert an instance to use DOIs, be sure to set metacat.properties up BEFORE running through the Metacat configuration and database upgrade.
use larger ("text") db field for guid in the xml_access.accessfileid column
remove flag for independent system metadata replication -- these entries are replicated along with the data/metadata objects or via hazelcast when the actual object is not on the server.
include 'archived' system metadata element in backing DB store
add ; to end of update command
only update accessfileid for our new guid-based records
include revision clause when updating the accessfileid on the xml_acccess table
refactor Metacat access handling to be on a per-revision basis so that it more closely aligns with the DataONE approachhttp://bugzilla.ecoinformatics.org/show_bug.cgi?id=5560
fixed a bug that using acces_log table name.
remove DataONE schema reference in xml_catalog
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.