Description

Moving processed Collection Sets is not supported. 
If it becomes neccessary to move Collection Sets, there are steps that can be taken in order to limit the administrative overhead involved.
 
A. Use the same URN path for the new location if possible.
B. Determine if only the Collection Set needs to be moved (Content and Metadata Sets) or if both the Collection Set and Tasks need to be moved to the new location (Metadata Only Sets) See Step 1 below.

 
STEPS:
1. Determine what data needs to be copied and possibly re-processed...
- Grep the destination location for: false within the Collection Set.xml file for each Collection Set.
 
Notes:
a. If the URN path is different: either the Set or the Task content must be copied.  Metadata Only Sets use the Task Content folder, even though the Set most often contains a Content folder, it is not used.
 
b. If the URN path is the same: Only the Set Content folder needs to be copied to the new location.
 
c. 'False' indicates a Metadata Only Collection Set.
 
d. 'True' indicates a Content and Metadata Collection Set.

(To double check the Grep functionality, switch the value to 'true' and run again.  The results will be the Sets not included in the first
run).
 

2. Copy each correct Content folder into its own location

****************************************************************************
Note: If the same URN path is used, the job is complete, otherwise continue:
****************************************************************************

3. Ingest each Content folder (from its new location) as a Case Folder Source
-- This allows the deDupe process to function.
-- After ingestion, the data will be 100% duplicates and the processed Glyph will remain yellow.  0 items processed (100% duplicates).
 
 
 
Questions:
- Do cache jobs need to be re-run?  Does anything need to be cleared in order for the cache to work?
 
A: In order to take advantage of the speed and efficiency derived from cached items, yes the cache jobs need to be run again after ingestion of
the duplicate items.

- Do existing Production folders need to be unlock/Unproduced and again Lock/Produced after the ingestion of the duplicate items?
 
A: No, the existing production items have already been cached from the original data.

- What happens to the license?

A: Ingestion of the duplicate data will double the consumption license usage.  Archiving the case will release the entire usage consumed.