Skip to content

Home

Jump to bottom
Susan Valente edited this page Aug 28, 2026 · 4 revisions

Welcome to the dcat-us wiki!

DCAT-US 3 Interagency Engagement, Agency Workflow, and Data.gov Implementation Tracking

Executive Summary

This paper summarizes the interagency engagement structure, agency-facing resources, request workflows, and internal Data.gov tracking processes supporting agency implementation of the DCAT-US 3 metadata standard.

The engagement model includes two recurring interagency meetings:

  1. DCAT Interagency Q&A Office Hours
    A bi-weekly office hours session focused on agency questions related to DCAT-US 3 implementation, metadata standards, harvesting, validation, and display on Data.gov. This session does not include prepared presentations or scheduled training material.

  2. DCAT Interagency Info Sharing Session
    A monthly information sharing session that may include presentations, demonstrations, walkthroughs, Q&A, and open floor discussion related to DCAT, DCAT-US 3, metadata standards, agency implementation efforts, harvesting, and Data.gov display considerations.

Agencies have several resources available to support DCAT-US 3 implementation:

Data.gov uses two primary tracking boards to manage implementation work:

  • Harvest Source Management Board:
    https://github.com/orgs/GSA/projects/431
    Used to track harvest source requests received through the Harvest Source Change Request Form, including agency communications, notes, request details, and the current stage or status of each request.

  • Data.gov Team Board:
    https://github.com/orgs/GSA/projects/11/views/1
    Used to track technical implementation issues, enhancements, and defects across Data.gov products, including Harvester, Catalog, Inventory.data.gov, and related services.

Together, these meetings, resources, forms, and tracking boards provide a structured process for helping agencies implement DCAT-US 3, request new or updated harvest sources, validate metadata, and coordinate with the Data.gov team.

1. Purpose

The purpose of this paper is to document the recurring interagency meeting structure, agency-facing implementation resources, harvest source request workflow, and Data.gov team tracking processes that support implementation of the DCAT-US 3 metadata standard.

As agencies apply DCAT-US 3 to their data inventories and metadata management processes, they may need support interpreting the standard, creating or updating metadata files, validating harvest sources, requesting harvest source changes, and understanding how metadata decisions affect harvesting and display on Data.gov.

This paper provides a consolidated overview of:

  • Recurring DCAT-US 3 interagency meetings
  • Agency implementation resources
  • Harvest source request and validation tools
  • Inventory.data.gov access process
  • Data.gov team tracking boards
  • Data.gov team workflow for processing harvest source change requests
  • Final acceptance criteria for new or updated harvest sources

2. Meeting Schedule

The DCAT-US 3 interagency engagement structure includes two recurring meetings:

  1. DCAT Interagency Q&A Office Hours
    Bi-weekly, every two weeks on Wednesday.

  2. DCAT Interagency Info Sharing Session
    Monthly, on the second Thursday.

Any updates to the meeting schedule, meeting links, or related DCAT-US 3 engagement information will be posted at:

DCAT-US 3 Updates:
https://resources.data.gov/resources/dcat-us-3-updates/

3. DCAT Interagency Q&A Office Hours

3.1 Meeting Details

Meeting Name: DCAT Interagency Q&A Office Hours
Format: No presentation / open Q&A
Cadence: Bi-weekly, every two weeks on Wednesday
Time: 12:00–12:50 p.m. Mountain Time
Time Zone: America/Denver
Google Meet: https://meet.google.com/txc-zcym-aky
Dial-in: +1 502-667-4043
PIN: 183 533 120#
More phone numbers: https://tel.meet/txc-zcym-aky?pin=5035736242438

Meeting Notes:
Gemini will take meeting notes. Notes and transcripts will be shared based on meeting settings.

3.2 Purpose

The DCAT Interagency Q&A Office Hours are a recurring bi-weekly session intended to provide an open forum for agencies implementing the DCAT-US 3 metadata standard.

This session is focused on agency questions related to applying the standard to agency data inventories, metadata management processes, harvesting, validation, and display on Data.gov.

This meeting may also be used to raise questions about related metadata standards or implementation considerations.

3.3 Important Note

This is an office hours session, not a formal training or presentation.

No prepared presentation materials or scheduled instruction will be provided. Agencies are encouraged to bring questions, examples, implementation scenarios, or issues they would like to discuss.

The meeting is driven by participant questions and discussion. If no questions or discussion topics are raised by participants, the meeting may remain open in silence or conclude early.

3.4 Recurring Agenda

1. Opening and Welcome

  • Confirm the purpose of the office hours
  • Invite participants to raise questions or discussion topics

2. Agency Q&A on DCAT-US 3 Implementation

  • Questions about required, recommended, or optional metadata fields
  • Interpretation of DCAT-US 3 elements
  • Applying the standard to agency-specific datasets and catalogs
  • Handling edge cases or implementation challenges

3. Metadata Harvesting and Data.gov Display Questions

  • How agency metadata decisions may affect harvesting
  • Potential impacts on Data.gov display, search, filtering, or discoverability
  • Troubleshooting metadata visibility or quality issues

4. Related Metadata Standards or Policy Questions

  • Discussion of other metadata standards, mappings, or interoperability questions as time allows
  • Cross-agency considerations or common implementation patterns

5. Open Discussion

  • Additional questions from participants
  • Peer-to-peer sharing of implementation approaches or lessons learned

6. Wrap-Up

  • Identify any follow-up items, if applicable
  • Note questions that may need additional research or referral
  • Confirm the next office hours session

4. DCAT Interagency Info Sharing Session

4.1 Meeting Details

Meeting Name: DCAT Interagency Info Sharing Session
Format: Information sharing session with variable format, including presentation, demonstration, Q&A, and open floor discussion
Cadence: Monthly, on the second Thursday
Time: 12:00–12:50 p.m. Mountain Time
Time Zone: America/Denver
Google Meet: https://meet.google.com/uat-sger-zhu
Dial-in: +1 260-232-3104
PIN: 868 852 959#
More phone numbers: https://tel.meet/uat-sger-zhu?pin=6856503468446

Recording and Notes:
This meeting will be recorded, and AI tools will be used to take notes.

4.2 Purpose

The DCAT Interagency Info Sharing Session is a recurring monthly forum for interagency information sharing related to DCAT, DCAT-US 3, metadata standards, agency implementation efforts, and related Data.gov harvesting and display considerations.

Unlike the bi-weekly office hours, this session may include prepared content, demonstrations, structured discussion, and participant Q&A. The format may vary each month depending on current topics, agency needs, implementation issues, and available presenters.

This session is intended to support cross-agency learning, coordination, and awareness as agencies work through DCAT-US 3 implementation and related metadata management activities.

4.3 Recurring Agenda

1. Welcome and Session Overview

  • Introductions, if needed
  • Review of the session purpose and format
  • Overview of planned topics or speakers for the month

2. Featured Presentation or Topic Discussion

  • Presentation on DCAT, DCAT-US 3, metadata standards, implementation practices, or related policy/technical topics
  • May include updates, lessons learned, issue deep dives, or agency use cases

3. Demonstration, Walkthrough, or Example Review

  • Live demonstration or walkthrough, as applicable
  • Examples may include:
    • Metadata records
    • Catalog implementation patterns
    • Validation approaches
    • Harvesting workflows
    • Data.gov display considerations

4. Agency Q&A

  • Questions about the featured topic or demonstration
  • Questions about DCAT-US 3 implementation, metadata standards, harvesting, or Data.gov-related impacts

5. Open Floor Discussion

  • Opportunity for agencies to raise related topics, challenges, questions, or information-sharing needs
  • Cross-agency discussion of implementation approaches, lessons learned, and common issues

6. Wrap-Up and Next Steps

  • Capture follow-up items, if applicable
  • Identify potential topics or presenters for future sessions
  • Confirm the next meeting date

5. DCAT-US 3 Implementation Resources

Agencies should use the following resources to support DCAT-US 3 implementation, metadata preparation, validation, and harvest source transition planning.

5.1 DCAT-US 3 Updates Page

Resource:
https://resources.data.gov/resources/dcat-us-3-updates/

The DCAT-US 3 Updates page is the primary location for updates related to the interagency meeting schedule and related DCAT-US 3 engagement information.

Agencies should refer to this page for updates to:

  • DCAT Interagency Q&A Office Hours
  • DCAT Interagency Info Sharing Session
  • Meeting schedule changes
  • Related DCAT-US 3 implementation updates or resources

5.2 DCAT-US 3 Implementation Guide

Resource:
https://resources.data.gov/resources/dcat-us-3-implementation/

The DCAT-US 3 Implementation Guide is the primary reference for agencies implementing the DCAT-US 3 metadata standard.

Agencies should use this guide when preparing, reviewing, or updating metadata to support DCAT-US 3 compliance and Data.gov harvesting.

The guide supports agency implementation activities such as:

  • Understanding DCAT-US 3 requirements
  • Reviewing metadata field expectations
  • Preparing DCAT-US 3 compliant metadata files
  • Aligning agency data inventories and catalogs with the DCAT-US 3 standard
  • Supporting metadata quality, validation, harvesting, and display on Data.gov

5.3 DCAT-US 3 to M-25-05 Crosswalk

Resource:
https://resources.data.gov/resources/dcat-us-3-crosswalk/

The DCAT-US 3 to M-25-05 Crosswalk provides a reference for understanding how DCAT-US 3 metadata elements relate to M-25-05-related requirements or considerations.

Agencies may use this crosswalk to support implementation planning, metadata review, and internal coordination when aligning agency metadata practices with DCAT-US 3 and related federal expectations.

This resource may help agencies:

  • Understand relationships between DCAT-US 3 fields and M-25-05 considerations
  • Review how metadata elements support related reporting or policy needs
  • Identify metadata fields that may require agency attention during implementation
  • Support internal conversations between data, policy, technical, and governance teams
  • Prepare questions for office hours or the monthly information sharing session

Agencies should use the crosswalk alongside the DCAT-US 3 Implementation Guide.

5.4 DCAT-US 3 Technical Implementation FAQs

Resource:
https://github.com/GSA/dcat-us/wiki

Frequently asked questions related to the technical implementation of the DCAT-US 3 metadata standard are being posted to the DCAT-US GitHub wiki as they are developed.

Agencies should use this resource to review emerging guidance, common implementation questions, technical clarifications, and recurring issues identified through agency implementation efforts, office hours, information sharing sessions, validation, and harvest source request processing.

This resource may include information related to:

  • Common DCAT-US 3 implementation questions
  • Technical interpretation of metadata fields
  • Validation issues and troubleshooting
  • Metadata formatting questions
  • Harvesting-related implementation considerations
  • Clarifications that arise through interagency discussions
  • Frequently encountered edge cases or implementation patterns

6. Agency Tools and Request Process

Agencies have several tools available to support the creation, review, validation, and submission of DCAT-US 3 harvest source requests.

6.1 Inventory.data.gov Access Request Form

Resource:
https://touchpoints.app.cloud.gov/touchpoints/9145dd7e

Agencies that need access to Inventory.data.gov to create a DCAT-US 3 compliant file can request access by submitting the Inventory.data.gov Access Request Form.

Inventory.data.gov may be used by agencies as part of their metadata creation and management process, including the creation of files intended to comply with the DCAT-US 3 metadata standard.

Once an Inventory.data.gov account is established, agencies must re-submit the same form once per quarter to maintain access.

Agencies may use this form to:

  • Request initial access to Inventory.data.gov
  • Support creation of a DCAT-US 3 compliant file
  • Maintain continued access to Inventory.data.gov
  • Complete the required quarterly access renewal process

6.2 Current Harvest Sources

Resource:
https://harvest.data.gov/

Agencies can view their current harvest sources at harvest.data.gov.

This site allows agencies to review the harvest sources currently associated with their agency. Agencies should use this information to understand their existing harvest source configuration before requesting a new DCAT-US 3 harvest source or submitting a change to a current harvest source.

Reviewing current harvest sources can help agencies determine whether they need to:

  • Request a new DCAT-US 3 harvest source
  • Update an existing harvest source
  • Correct harvest source information
  • Confirm the status or configuration of existing harvest sources
  • Identify whether a current source should be replaced, updated, or retired

6.3 Harvest Source Validation Tool

Resource:
https://harvest.data.gov/validate/

Agencies can use the Harvest Source Validation Tool to check whether their harvest source is expected to pass validation.

This tool can be used before submitting a request for a new DCAT-US 3 harvest source or before requesting a change to an existing harvest source.

Using the validation tool can help agencies identify and resolve metadata issues earlier in the process, before the request is submitted through the Harvest Source Change Request Form.

Agencies may use the validation tool to:

  • Test whether a proposed harvest source passes validation
  • Identify metadata errors or warnings
  • Confirm that a DCAT-US 3 harvest source is structured correctly
  • Resolve validation issues before requesting that Data.gov add or update the harvest source
  • Reduce back-and-forth during the harvest source review process

If the harvest source does not pass validation, agencies should review and correct the identified issues before submitting a new or updated harvest source request, where possible.

6.4 Harvest Source Change Request Form

Resource:
https://touchpoints.app.cloud.gov/touchpoints/ffb7e9d0

The Harvest Source Change Request Form is the agency-facing intake mechanism for requesting either a new DCAT-US 3 harvest source or a change to an existing harvest source.

Agencies should use this form when they need to:

  • Request creation of a new DCAT-US 3 harvest source
  • Request a change to an existing harvest source
  • Update the source URL for a harvest source
  • Change a harvest source from DCAT-US 1.1 to DCAT-US 3
  • Correct or update harvest source configuration information
  • Request other harvest-source-related changes needed to support metadata harvesting by Data.gov

Before submitting the form, agencies should review their current harvest sources at:

https://harvest.data.gov/

Agencies should also validate whether a proposed or updated harvest source is expected to pass validation at:

https://harvest.data.gov/validate/

Once a request is submitted, it is tracked by the Data.gov team on the Harvest Source Management Board.

7. Recommended Agency Workflow for DCAT-US 3 Harvest Source Requests

Agencies should use the following general workflow when preparing to request a new DCAT-US 3 harvest source or a change to an existing harvest source.

Step 1: Review DCAT-US 3 Implementation Resources

Agencies should begin by reviewing the primary DCAT-US 3 implementation resources:

These resources help agencies understand DCAT-US 3 requirements, review related M-25-05 considerations, prepare metadata for validation and harvesting, and find answers to common technical implementation questions.

Step 2: Determine Whether Inventory.data.gov Access Is Needed

Agencies that need to use Inventory.data.gov to create a DCAT-US 3 compliant file can request access using the Inventory.data.gov Access Request Form:

https://touchpoints.app.cloud.gov/touchpoints/9145dd7e

Once an account is established, this same form must be re-submitted once per quarter to maintain access.

Step 3: Create or Update the DCAT-US 3 Compliant File

Agencies prepare their metadata file using their selected process or tool, including Inventory.data.gov if applicable.

Step 4: Review Current Harvest Sources

Agencies can view their current harvest sources at:

https://harvest.data.gov/

This allows agencies to confirm existing harvest source information before requesting a new harvest source or submitting a change to a current harvest source.

Step 5: Validate the Proposed Harvest Source

Agencies can test whether their harvest source is expected to pass validation at:

https://harvest.data.gov/validate/

Agencies should address validation errors or issues before submitting a new or updated harvest source request, where possible.

Step 6: Submit a Harvest Source Change Request

If a new DCAT-US 3 harvest source is needed, or if a change to an existing harvest source is required, agencies should submit the request through the Harvest Source Change Request Form:

https://touchpoints.app.cloud.gov/touchpoints/ffb7e9d0

Step 7: Request Tracking and Agency Communication

Requests submitted through the Harvest Source Change Request Form are tracked on the Harvest Source Management Board:

https://github.com/orgs/GSA/projects/431

The board is used to track request details, communications with agencies, notes, follow-up actions, and the current stage or status of each request.

Step 8: Technical Implementation Tracking, If Needed

If a harvest source request identifies a broader Data.gov technical issue, enhancement, or defect, that work may be tracked on the Data.gov Team Board:

https://github.com/orgs/GSA/projects/11/views/1

8. Data.gov Tracking Boards

8.1 Harvest Source Management Board

Resource:
https://github.com/orgs/GSA/projects/431

The Harvest Source Management Board is used to track harvest source requests received through the Harvest Source Change Request Form.

This board supports the management of requests for new DCAT-US 3 harvest sources and requests to change existing harvest sources.

The board provides a place to track the full request lifecycle, including information received from agencies, communications with agency contacts, internal notes, and the current stage or status of each request.

Relevant information tracked on the Harvest Source Management Board may include:

  • Requests submitted through the Harvest Source Change Request Form
  • Requests for new DCAT-US 3 harvest sources
  • Requests to update or change existing harvest sources
  • Agency contact information or communication history, as appropriate
  • Notes received from agencies
  • Internal notes related to request review or implementation
  • Current stage or status of each request
  • Follow-up actions or pending questions
  • Coordination needed with agency representatives or Data.gov team members

This board helps provide visibility into the progress of harvest source requests and supports coordination between agencies and the Data.gov team from intake through completion.

8.2 Data.gov Team Board

Resource:
https://github.com/orgs/GSA/projects/11/views/1

The Data.gov Team Board is used to track technical implementation work across Data.gov products.

This includes issues, enhancements, defects, and related development tasks for products such as:

  • Harvester
  • Catalog
  • Inventory.data.gov
  • Other Data.gov services

This board provides visibility into technical work that may affect metadata harvesting, catalog functionality, inventory workflows, Data.gov display, and related user-facing or back-end platform capabilities.

Relevant work tracked on the Data.gov Team Board may include:

  • Technical implementation issues
  • Product enhancements
  • Defects or bugs
  • Harvester-related development work
  • Catalog-related development work
  • Inventory.data.gov updates
  • Metadata workflow improvements
  • Data.gov platform or service updates
  • Cross-product technical dependencies

This board is distinct from the Harvest Source Management Board, which is focused on tracking harvest source requests received through the agency-facing Touchpoints form.

9. Data.gov Team Workflow for Harvest Source Change Requests

Once an agency submits a request for a new DCAT-US 3 harvest source or a change to an existing harvest source through the Harvest Source Change Request Form, the Data.gov team will review and process the request through the Harvest Source Management workflow.

Requests are tracked on the Harvest Source Management Board, including agency communications, notes, request status, troubleshooting items, and the current stage of the request.

9.1 Initial Review and Testing Tasks

After receiving a harvest source change request, the Data.gov team will complete the following initial tasks:

  • Confirm and test the source URL link.
  • Add the new harvest source to the Data.gov Harvester development environment.
  • Send the Harvester development environment test report to the agency point of contact.
  • Confirm with the agency point of contact whether the request will follow Path A or Path B.

The purpose of this initial review is to confirm that the proposed source URL is accessible, can be tested in the Harvester development environment, and is ready for the appropriate transition approach.

10. Harvest Source Transition Paths

After initial testing, the Data.gov team and agency point of contact will determine whether the request should follow Path A or Path B.

10.1 Path A: Add a New DCAT-US 3 Harvest Source While Temporarily Maintaining the Existing Source

Path A is used when an agency will have a new, additional DCAT-US 3 harvest source created while the existing harvest source remains available temporarily.

This allows the agency to transition datasets or other metadata records from the existing DCAT-US 1.1 harvest source to the new DCAT-US 3 harvest source over time.

Path A Tasks

  • Set up a new, additional harvest source record so the agency has an additional DCAT-US 3 harvest source.
  • Turn on harvesting for the new harvest source.
  • Allow the agency to transition datasets or other metadata records from the DCAT-US 1.1 harvest source to the DCAT-US 3 harvest source.
  • Wait for the agency to confirm that all datasets or other metadata records have been transitioned.
  • Clear and then delete the old harvest source.
  • Send confirmation to the agency point of contact.
  • Note any troubleshooting items in the request comments or tracking record.

10.2 Path B: Update an Existing Harvest Source to DCAT-US 3

Path B is used when an existing harvest source will be stopped, updated, and resumed using the DCAT-US 3 metadata format/profile.

This path requires coordination with the agency to confirm timing and ensure the agency has made the necessary changes to its JSON file before harvesting resumes.

Path B Tasks

  • Confirm the date to stop harvesting the old harvest source.
  • Make note of harvest source timing as daily, weekly, monthly, or other.
  • Edit the harvest source to stop harvesting and send notification to the agency.
  • Wait for the agency to switch, modify, or edit its JSON file and send confirmation back that changes have been made.
  • Edit the harvest source to reference DCAT-US 3 and resume harvesting as previously noted.
  • Send confirmation to the agency point of contact.
  • Note any troubleshooting items in the request comments or tracking record.

11. Final Acceptance Criteria

A harvest source request may be considered complete when the following acceptance criteria have been met:

  • A new or updated metadata harvest source exists under the correct parent organization.
  • The harvest source uses the confirmed source URL.
  • The source is configured for the appropriate metadata format/profile.
  • An initial harvest has completed successfully.
  • Any harvest errors or validation issues have been reviewed and documented.
  • Follow-up actions, if any, have been captured in the request issue or linked issues.

12. Relationship Between Meetings, Tools, Forms, and Boards

The DCAT-US 3 implementation support structure combines recurring engagement forums, agency-facing tools, request intake forms, and Data.gov tracking boards.

The DCAT Interagency Q&A Office Hours provide a question-driven forum where agencies can ask implementation questions, discuss metadata issues, raise validation concerns, and ask how metadata decisions may affect Data.gov harvesting and display.

The DCAT Interagency Info Sharing Session provides a broader forum for interagency learning and coordination. This session may include presentations, demonstrations, structured discussions, agency use cases, Q&A, and open floor discussion.

The DCAT-US 3 Implementation Guide, DCAT-US 3 to M-25-05 Crosswalk, and DCAT-US 3 Technical Implementation FAQs support agency preparation and implementation of the metadata standard.

The Inventory.data.gov Access Request Form allows agencies to request access to Inventory.data.gov to create a DCAT-US 3 compliant file. Once access is established, the same form must be re-submitted once per quarter to maintain access.

Agencies can review their current harvest sources at harvest.data.gov and validate a proposed or updated harvest source at harvest.data.gov/validate/.

If an agency determines that a new DCAT-US 3 harvest source is needed, or that a current harvest source needs to be changed, the agency should submit the request through the Harvest Source Change Request Form.

Requests submitted through the form are tracked on the Harvest Source Management Board, which captures request details, agency communications, notes, follow-up actions, troubleshooting information, and the current stage or status of each request.

The Data.gov Team Board is used separately to track technical implementation issues, enhancements, and defects across Data.gov products, including Harvester, Catalog, Inventory.data.gov, and related services. If a harvest source request identifies a broader product issue, enhancement, or defect, that work may also be reflected on the Data.gov Team Board.

Together, these resources help connect agency implementation needs with Data.gov technical work, harvesting processes, metadata validation, and cross-agency coordination.

13. Conclusion

The DCAT-US 3 implementation support structure provides agencies with recurring opportunities for discussion, implementation support, and information sharing, while also establishing clear tools and workflows for harvest source requests and Data.gov tracking.

The bi-weekly DCAT Interagency Q&A Office Hours provide an open, question-driven forum for implementation support. The monthly DCAT Interagency Info Sharing Session provides a broader space for presentations, demonstrations, Q&A, and cross-agency discussion.

Agency-facing resources, including the implementation guide, crosswalk, FAQs, Inventory.data.gov access form, harvest source validation tool, and harvest source change request form, help agencies prepare and submit DCAT-US 3 harvest source requests.

The Harvest Source Management Board and Data.gov Team Board support internal tracking, communication, technical implementation, and issue resolution.

This combined approach supports agency adoption of DCAT-US 3, improves transparency around harvest source changes, and strengthens coordination between agencies and the Data.gov team.

DCAT-US 3 Implementation Support

Meetings

Implementation Resources

Data.gov Team Process

FAQs

Reference

DCAT Interagency Maintenance Team

Clone this wiki locally