rseng-data-management-planslisted

# Data management plans A DMP answers, before the data exists, the questions that hurt when answered too late: what data will the project produce, where will it live, who may see it, what does that cost, and what survives the grant. Funders require one with most proposals; the useful version is not the compliance document but the honest operating plan - and because it describes practices this pack already engineers, most of a good DMP can be drafted from, and checked against, the project itself. The software counterpart (rseng-management-planning's SMP practice) shares this design; write the two consistently and cross-reference them. ## What a plan covers The standard sections, each answered from project reality: 1. Data description: types, formats, expected volumes, sources - name open formats deliberately (rseng-scientific-file-formats) and reused third-party datasets with their licenses and terms. 2. Documentation and metadata: data dictionaries, READMEs, community metadata standards for the domain (rseng-data-management owns the practice; the DMP states which). 3. Storage and backup during the project: where working data lives, replication, who administers it - institutional storage beats lab improvisation; sensitive data goes where the steward says (rseng-regulatory-compliance). 4. Access, sharing and legal: who can access what and when, embargo plans, consent and GDPR constraints, anonymization strategy - with honest limits stated (rseng-r