# Evaluate & Archive Stage

<figure><img src="https://1394946355-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZL4sEq1AZ78TabPPsj8G%2Fuploads%2FlQFeb9f3ZJqB2dgsq2Zn%2FEvaluate%20and%20Archive.jpg?alt=media&#x26;token=3e2f08d5-5bfe-4fa8-b9f1-a876f93eee26" alt=""><figcaption><p>Evaluate &#x26; Archive Stage</p></figcaption></figure>

## **Evaluate and Archive Stage – Summary Table**

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Category</strong></td><td><strong>Details</strong></td></tr><tr><td><strong>Stage Purpose</strong></td><td>Transition inactive research data from active project environments to long‑term archival systems (data vaults) to optimize current system performance and ensure secure, cost‑effective retention.</td></tr><tr><td><strong>Primary Objectives</strong></td><td><ol><li>Free active storage to improve server/database performance.</li><li>Retain static data in specialized archival or preservation systems for long‑term accessibility and regulatory compliance.</li></ol></td></tr><tr><td><strong>Archiving vs Preservation</strong></td><td><ol><li>Archiving moves inactive data to secure, cost‑efficient systems for retention and occasional retrieval. </li><li>Preservation ensures format sustainability, metadata completeness, and accessibility over required retention periods.</li></ol></td></tr><tr><td><strong>Retention Requirements</strong></td><td><ol><li>UCPH / reNEW: Follow faculty retention policies and store on approved infrastructures (e.g., ERDA, national services).</li><li>EU Funders (Horizon Europe/ERC): Data must remain accessible for at least the funder‑mandated retention period, typically 5–10+ years.</li></ol></td></tr><tr><td><strong>Key Activities</strong></td><td><ol><li>Identify inactive data suitable for archiving.</li><li>Migrate to approved archival storage (ERDA, institutional/national vaults).</li><li>Verify metadata and documentation for future findability.</li><li>Plan for long‑term format migration and maintenance.</li></ol></td></tr><tr><td><strong>Team Responsibilities</strong></td><td><ol><li>Confirm which data must be retained in accordance with scientific, regulatory, and contractual obligations.</li><li>Maintain access controls and retrieval procedures.</li><li>Coordinate with data stewards/IT for ongoing preservation and periodic validation.</li></ol></td></tr><tr><td><strong>Benefits</strong></td><td><ol><li>Compliance with UCPH, reNEW, and EU funder policies</li><li>Protects scientific integrity and enables future reproducibility. </li><li>It also supports impact assessments and potential reuse of archived datasets.</li></ol></td></tr></tbody></table>
