Inventory.data.gov users get correct program and bureau codes to datasets created with new form

GSA / datagov-ckan-multi

Other

10 stars 6 forks source link

Inventory.data.gov users get correct program and bureau codes to datasets created with new form #557

Open hkdctol opened 3 years ago

hkdctol commented 3 years ago

User Story

As an inventory.data.gov user, I want to ensure that the required fields on program code and bureau code are populated with the correct corresponding codes for my organization so that metadata is correct for these fields in datasets I create with the new metadata form.

Acceptance Criteria

[ ] When I create a new dataset on inventory.data.gov using the new form, and publish a dataset, the published dataset reflects the correct program and bureau codes corresponding to my organization.

Details / tasks

Use the real values for these codes (links are available in the schema) https://resources.data.gov/resources/dcat-us/#bureauCode rather than dummy codes

adborden commented 3 years ago

I think for implementation, we'd want to do something similar to how we're handling publishers. A CKAN command to read the CSV and update organization group_extras.

adborden commented 3 years ago

FWIW, bureau code can be a list, for example when multiple agencies collaborate on a dataset. It's okay to ignore this requirement for now since USMetadata did not support that use case either.

FuhuXia commented 3 years ago

User reported newly created datasets in inventory are getting wrong bureau code. https://inventory.data.gov/organization/railroad-retirement-board. All datasets are supposed to be using 446:00 as bureau code, but newly created datasets are getting 015:11.

hkdctol commented 3 years ago

omb_bureau_codes (10).xlsx I can tell from recently added GSA datasets - yes all new datasets are using 015;11 so would it be doing something similar to how we're handling the publishers for each organization in inventory.data.gov. We have this OMB bureau code spreadsheet and not clear whether there's been any update by OMB or whether OMB will continue to use them, but we can't change much until there is a formal metadata schema update.