forked from infopolicy/dcat-us
-
Notifications
You must be signed in to change notification settings - Fork 5
DCAT US 3 Technical Implementation FAQ
David Aguiar edited this page Aug 31, 2026
·
9 revisions
this page is draft and should be filled in soon
Core DCAT-US 3.0 support in the harvester has landed and has no open known defects as of this writing. We appreciate agencies testing against it, and it's likely we'll need to make some fixes as this is new. Testing against a test harvest source is reasonable, and the ingested output should be a fair preview of production behavior.
A couple of caveats before relying on it for anything final:
- Guidance on some edge cases is still being finalized, including how to represent
theme: geospatialand how to link ISO/CSDGM records as distributions. - A standardized "dev/test report" process, so agencies can get a clear before-you-go-live confirmation, is still in development. Until it's ready, the harvest source's own validation output is the best signal available.
Bring any edge cases you hit to DCAT Interagency Q&A Office Hours.
— DA, last edited 2026-08-31
- DCAT-US 3 Implementation Resources
- Agency Workflow for DCAT-US 3 Harvest Source Requests
- Inventory.data.gov Access
- Harvest Source Review and Validation
- Harvest Source Change Requests
- FAQ Overview
- DCAT-US 3 Technical Implementation FAQ
- Harvest Source Request FAQ
- Inventory.data.gov Access FAQ
- Meeting FAQ
- Tracking and Issue Routing FAQ
- DCAT Interagency Maintenance Team
- DCAT IMT CHARTER
- Maintenance Process Overview
- Roles and Responsibilities
- Issue Triage and GitHub Workflow
- Semi-Annual Release Cycles
- Agency Feedback and Participation
- Release Communications and Outreach
- Annual Retrospective
- Maintenance Meeting Schedule
- Maintenance Templates