Task #2857
Story #2720: KNB, LTER, PISCO, ESA, SANPARKS roll out
Create DOI conversion script for LTER node
100%
Description
The KNB will have definitive knowledge of where each document originated and therefore which docids should have which DOI prefixes (if at all).
-KNB will generate DOIs for KNB, PISCO, and LTER on the KNB node
-LTER will only generate DOIs for objects it owns (home server)
-PISCO will only generate DOIs for objects it owns
-The will use the complete list of identifiers from the KNB (in the identifiers table) to update the identifiers table on LTER with the correctly assigned DOIs so that the LTER node has DOIs for the KNB and PISCO replicas it houses.
This will be a manually applied Postgres change consisting of a source data file (KNB.identifiers) and an SQL script that uses the included data and makes the necessary update to LTER's identifier table.
This should be performed after the 2.0.0 upgrade but before any System Metadata is generated on the LTER MN.
History
#1 Updated by Ben Leinfelder over 12 years ago
- Status changed from New to Closed
uses the guid from KNB in place of the guid that LTER has in the identifier table. Pretty straight forward once you scp the data (csv) file over from the KNB server.
