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 part of the childless records work, over 300K records will be re-uploaded with data from AMS1. Many records have been updated with extensive metadata in AMS2 which will be lost as part of this upload. The biggest impact will be to New Mexico and Peabody collections, but likely many more considering the scale of the re-write.
We will need to have a process in place to update the records with accurate metadata currently in AMS2.
Additional Information
A new ingester is going to be created
Some other ideas we considered:
Identify the GUIDS being replaced, have Kevin do a large export of these GUID records in AAPB
Use AAPB xml to create an update for records in AMS2
Other info
Mostly assets and contributors will be impacted by the childless records fix. Specific fields include: descriptions, titles, annotation fields (playlist group, playlist order), asset types, dates, producing organization, etc.
Done Looks Like
Metadata lost during resolution of childless records work is back in AMS
The text was updated successfully, but these errors were encountered:
Putting this here that if we have an opportunity to prioritize stations to be migrated to AMS2 first:
New Jersey News Network (we have rights to license this one, and MLA staff are held up on further work until it is in AMS2)
@foo4thought and @mivillesvik: I've ingested the missing guids mentioned in guids_aapb_2migrate2_ams2.txt. A couple of issues across the board that required me to update the pbcore (wrong date formatting mainly). Only one record gave me more trouble than I could handle right now (cpb-aacip-151-b853f4m48t). It contains annotationTypes currently not valid in AMS2.
User Story
As part of the childless records work, over 300K records will be re-uploaded with data from AMS1. Many records have been updated with extensive metadata in AMS2 which will be lost as part of this upload. The biggest impact will be to New Mexico and Peabody collections, but likely many more considering the scale of the re-write.
We will need to have a process in place to update the records with accurate metadata currently in AMS2.
Additional Information
A new ingester is going to be created
Some other ideas we considered:
Identify the GUIDS being replaced, have Kevin do a large export of these GUID records in AAPB
Use AAPB xml to create an update for records in AMS2
Other info
Mostly assets and contributors will be impacted by the childless records fix. Specific fields include: descriptions, titles, annotation fields (playlist group, playlist order), asset types, dates, producing organization, etc.
Done Looks Like
Metadata lost during resolution of childless records work is back in AMS
The text was updated successfully, but these errors were encountered: