Project

General

Profile

Task #2060

Story #2056: Metacat upgrade procedure

Map legacy Metacat docids to newly minted Metacat ids (e.g. DOIs)

Added by Ben Leinfelder over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Metacat
Start date:
2011-11-28
Due date:
% Done:

100%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

If we generate new DOIs for every Metacat object, we need to map those DOIs to the existing docid. the DOI will be used for the DataONE SystemMetadata identifier so we should do the EZID generation before generating the SystemMetadata records. (or do thaem concurrently).

History

#1 Updated by Ben Leinfelder over 12 years ago

  • Assignee set to Ben Leinfelder

This can be done after SystemMetadata has been generated but before ORE maps are generated (because ORE maps contain identifiers in their RDF/XML content).
The columns in Metacat that will need to be updated with the DOI prefix are:
identifier.guid
systemMetadata.guid
systemMetadataReplicationPolicy.guid
systemMetadataReplicationStatus.guid
xml_access.guid
xml_access.accessfileid

#2 Updated by Matthew Jones about 12 years ago

  • Assignee changed from Ben Leinfelder to Matthew Jones

#3 Updated by Matthew Jones about 12 years ago

  • Status changed from New to In Progress

#4 Updated by Matthew Jones about 12 years ago

  • Category set to Metacat
  • Milestone changed from CCI-0.6.4 to CCI-1.0.0
  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

Task completed. The Metacat 2.0.0 upgrade procedure now includes the ability to generate DOIs for GUIDs when upgrading, but must be configured before starting the upgrade process.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)