Harvest Documentation #5657

User Story

In order to better support federal data providers, data.gov admins want clear documentation on expectations, requirements, and details on what harvest.data.gov requires to get data onto data.gov catalog.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN a data provider doesn't know where to start
  WHEN they go to data.gov
  THEN a webpage exists detailing the data.gov harvest process
  AND details on transformation, requirements, standards, etc are readily available.

Background

This webpage already exists, but is not ready for the new harvester and new catalog process. https://resources.data.gov/resources/data-gov-open-data-howto/

Security Considerations (required)

None

Sketch

When updating/creating content, the following should also be considered:

• Should this webpage be clearly linked on data.gov or catalog.data.gov or harvest.data.gov?
• Should this content be re-formatted?
• Should DCAT-US3.0 be included?
• What part of the transformation crosswalk should be included? Should https://resources.data.gov/resources/podm-field-mapping/ be overwritten, or removed with a completely new version?
• Are there future tickets that should be created to make the process as currently constructed easier?