Skip to content
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

Migrate custom fields that match common core metadata #125

Open
philipashlock opened this issue Jun 30, 2014 · 0 comments
Open

Migrate custom fields that match common core metadata #125

philipashlock opened this issue Jun 30, 2014 · 0 comments

Comments

@philipashlock
Copy link
Member

There's at least one place where one of the fields in the common core metadata is shown as a separate custom field. On the record for Best of Charts of Note 2013 the dataQuality field should be handled by the "Meets Agency Data Quality" dropdown menu. The way it's currently handled as a custom field is causing it to be exported as a string rather than a boolean.

I'm not sure if this was an issue with a direct import that was converted incorrectly or if it's legacy from data entry before the option to specify "Meets Agency Data Quality" was implemented, but any custom field that matches at common core metadata field like this need to be mapped properly.

This was initially reported at GSA/project-open-data-dashboard#31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant