-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transform FGDC/CSDGM source to DCAT-US #4564
Labels
H2.0/Harvest-Transform
Transform Logic for Harvesting 2.0
Comments
btylerburton
added
H2.0/Harvest-Transform
Transform Logic for Harvesting 2.0
and removed
H2.0/Harvest-General
General Harvesting 2.0 Issues
labels
Dec 19, 2023
Combined with this ticket #4565 |
Reopening in light of the fact that DCAT-US writer is not yet available. |
btylerburton
changed the title
Transform FGDC source to DCAT-US
Transform FGDC/CSGM source to DCAT-US
Dec 19, 2023
btylerburton
changed the title
Transform FGDC/CSGM source to DCAT-US
Transform FGDC/CSDGM source to DCAT-US
Dec 19, 2023
btylerburton
moved this from 📔 Product Backlog
to 📟 Sprint Backlog [7]
in data.gov team board
Feb 29, 2024
btylerburton
moved this from 📟 Sprint Backlog [7]
to 📔 Product Backlog
in data.gov team board
Feb 29, 2024
confirmed with johnathan that fgdc reader is in good shape. "it’s one of the better ones". |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
In order to test another facet of the transformation step in our pipeline, datagovteam would like to transform an FGDC/CSDGM WAF source to DCAT-US and push that into CKAN.
This story depends on:
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
WHEN I add that to our ETL Pipeline with the appropriate harvest source config
THEN I expect the mdTranslator to transform the source into valid DCAT-US datasets
AND I expect it to be able to pushed into a CKAN development instance without error.
Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
Security Considerations (required)
No work planned outside the cloud.gov boundary.
Sketch
The text was updated successfully, but these errors were encountered: