COPRSETR WORKSHEET
Validated metadata record, disclosure decision, license and privacy review, approved records schedule
Geospatial Data Act federal agency compliance · Step 6 · Validate metadata, privacy, confidentiality and records treatment- Who prepares it
- Data steward + Privacy officer + Records officer + Security + Subject-matter reviewer
- When to prepare it
- At creation and every material update; before external disclosure
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional metadata check
- A census-block layer has complete provenance but no documented coordinate reference or limitations. The validator blocks release, assigns the GIS lead to correct both fields, and reruns schema validation after the owner signs off.
- Privacy decision
- A point layer could identify a person’s home and a protected service location. The privacy reviewer compares aggregation and masking options, records residual re-identification risk and approves only the release version with controlled precision.
Gather first
- Dataset and lineage
- Selected FGDC or agency profile
- Privacy analysis
- License and partner terms
- Security classification
- NARA-approved schedule
How to prepare it
- Select the current required metadata standard and target profile. Follow the agency’s GeoPlatform/Data.gov schema and FGDC-endorsed standards; verify whether ISO 19115, a profile or a transition exception applies. Do not assume the older CSDGM is the sole current standard.
- Validate title, abstract, publisher, owner, source, lineage, vintage, geographic extent, coordinate reference, accuracy, limitations, update cadence, access constraints, contact and distribution link. Preserve validation output and fix failed mandatory fields.
- Before disclosure, assess Privacy Act implications and re-identification risk, including small-area combinations and sensitive locations. Check confidentiality, security, partner rights, license conditions, records schedule and any permitted redaction or aggregation. Approve the public metadata and dataset as separate release objects.
Review
The public record accurately describes the dataset, passes the applicable schema and has a documented disclosure decision.
Handoff
Keep the signed review with the release version, not only in the project’s email thread.
Use the issuer’s current instructions and any required forms when you submit.
FGDC endorsed metadata standards and guidance (opens in a new tab)