Repository navigation
Capture harvest source descriptions #5390
Description
Activity
catalog-harvest-info.json is the current harvest source info to add in (in case this is done after the CKAN harvester is gone).
Describe the harvest source. (Does not relate to publisher).
7 remaining items
- removed a parent issue
on Jun 25, 2026 - removed a parent issue
on Jul 23, 2026 - added a parent issue
on Jul 23, 2026 - moved this from 📥 Queue (up next) to 📟 Sprint Backlog (Top Priority) in data.gov team board
on Sep 8, 2026 - moved this from 📟 Sprint Backlog (Top Priority) to 🏗 In Progress in data.gov team board
on Sep 17, 2026 - linked a pull request that will close this issue5390: Old Capture harvest source descriptions #945
on Sep 17, 2026 - moved this from 👀 Needs Review to ✔ Done in data.gov team board
on Sep 23, 2026 Ran script to add descriptions to harvest sources from the json above @SueValente @jbrown-xentity. Results:
- 797 sources in prod
- 613 updated with new descriptions
- 165 skipped because they had empty descriptions in JSON
- 19 sources exist in prod but not in the json file
Reacted by James Brown@jaredb96 I saw the description addition yesterday during DCAT-US3 office hours! Very helpful added search.
Thanks!
Metadata
Metadata
Assignees
Type
Projects
- Status
User Story
In order to capture harvest source subscriptions, data.gov admins (and data providers) want the H2.0 model updated to allow for a description.
Acceptance Criteria
WHEN a sync between CKAN and H2.0 occurs
THEN the description (where available) is available on H2.0.
Background
See prod example here: https://catalog.data.gov/harvest/about/census-5-digit-zip-code-tabulation-area-zcta5-national
Ironically, the description is cut off in the view. However, as we lack context on many of these harvest sources, it will be helpful to have this information for future.
Security Considerations (required)
None
Sketch
This would involve a DB migration, but only adding a field (which is minor by DB migration standards).
descriptionto the harvest_source table model via a migration.