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

Consistency btwn CSV ingest and update #924

Open
ekemeyer opened this issue Sep 30, 2024 · 0 comments
Open

Consistency btwn CSV ingest and update #924

ekemeyer opened this issue Sep 30, 2024 · 0 comments
Labels
Feature Request New Feature

Comments

@ekemeyer
Copy link
Contributor

As a user, I want there to be consistency across the fields/columns used in the ingesters. For example:

  • Asset.description is a valid column for the AAPB CSV Ingester, allowing for descriptions to be added without a type. However, it is not a valid column for the AAPB CSV Asset Attribute Update Ingester.

The above limitation has caused an issue with cataloging materials post-digitization, when additional descriptions become available. An example: https://ams2.wgbh-mla.org/concern/asset_resources/cpb-aacip-191-300zpg4s.xml.

<pbcoreDescription>No description available</pbcoreDescription> had been used as a placeholder until more information could be added. Ideally the cataloguers would have the option of batch updating or deleting this tag.

@ekemeyer ekemeyer added the Feature Request New Feature label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New Feature
Projects
None yet
Development

No branches or pull requests

1 participant