... so that I can support more streamlined ingestion of only deltas to past releases, versus full SIPs for the entire bundle. lessens the strain on the NSSDCA for needing to recognize those diffs from past releases. also helps support possible staging of data on-prem vs. in the cloud for download.
📖 Additional Details
N/A
Acceptance Criteria
Given a bundle that has been previously released and delivered to NSSDCA
When I perform pds deep archive execution on that bundle
Then I expect to generate a SIP, AIP, and accompanying manifests for only the diffs of the bundle from the past release.
Checked for duplicates
Yes - I've already checked
🧑🔬 User Persona(s)
Node Operator
💪 Motivation
... so that I can support more streamlined ingestion of only deltas to past releases, versus full SIPs for the entire bundle. lessens the strain on the NSSDCA for needing to recognize those diffs from past releases. also helps support possible staging of data on-prem vs. in the cloud for download.
📖 Additional Details
N/A
Acceptance Criteria
Given a bundle that has been previously released and delivered to NSSDCA When I perform pds deep archive execution on that bundle Then I expect to generate a SIP, AIP, and accompanying manifests for only the diffs of the bundle from the past release.
⚙️ Engineering Details
N/A