You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
<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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: