Data Steward Track

Research data includes source measurements, datasets, logs, saved program states, and results. A data steward decides with the information owner where those files belong, who may use them, and what must happen when the project ends.

Complete this track if you organize shared datasets, checkpoints, logs, experimental results, or handover archives.

This page summarizes the track. Follow the current mission in your local Passport; do not use the links below as a second checklist.

Prerequisites#

• IT and Research Safety Core
• The project's information owner and supervisor are identified

Current Training Evidence#

Placement/collaboration check fictional choices; handover checks a bounded fictional document. They do not generate or approve a real map, permissions plan or reproduction result.

Use the current Passport lesson for sequencing. The competencies and evidence below describe later project capability and private owner review; they are not extra public submissions or automatic access grants.

Competencies#

You can:

• classify project information and document approved services;
• distinguish source data, working data, temporary data, and final records;
• choose NAS, Euler project/work, scratch, or local storage intentionally;
• preserve provenance, licenses, consent, and access restrictions;
• set collaborative permissions without making data world-writable;
• prevent Git repositories from becoming shared data stores;
• plan backup, retention, cleanup, and project handover;
• restore from snapshots or contact the correct support owner.

Mission Coverage#

1. Data and AI policy
2. NAS guide
3. Euler storage, when relevant
4. Data placement lab
5. Project handover lab

Evidence#

• A completed data-location map.
• A short README describing data owner, source, classification, access, environment, retention, and recovery.
• A safe shared-folder design for datasets, checkpoints, logs, and results.
• A .gitignore that excludes local data and generated files or results.

Understand Before Accepting AI Output#

• I verified paths before permission or deletion commands.
• I did not use recursive chmod 777.
• I know which locations are backed up and which are temporary.
• I know who approves access and data disposal.

Pass Criteria#

The data map is approved by the information owner or supervisor and another researcher can understand where the main approved and temporary copies belong.