-
Notifications
You must be signed in to change notification settings - Fork 0
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
GBH: Validate that Assets don't get marked for transfer to AAPB when they don’t have all their children (XML only) #108
Comments
Kiah: Questions: Are Assets the only work type that gets transferred to AAPB? |
July 11, Kiah: Tally in Bulkrax and bulk ingester, final check in actor stack. /pushes endpoint <-- where transfers happen |
July 11, Kiah:
Yes
All instantiations and Essence Tracks.
Yes
|
July 17, Kiah: Passes QA on demo: |
Summary
Its is hard to know when all of the children have been attached to a work, and so some works are getting transferred even though they are not complete. We want to add a count to the work for how many children, and then flip a flag when the children are all present that then gives access to the transfer to AAPB button.
Acceptance Criteria
1 Only
AAPB PBCore - Zipped
(Batch Ingester) andPbcoreXmlParser
(Bulkrax) are in scope for this ticket. The remaining parsers and ingesters will be completed in future tickets.Testing instructions:
106-0000000q.xml
102-20fttgwp.xml
KYUK_migration5.zip
PbcoreXmlParser (Bulkrax)
AAPB PBCore XML
as the parserAAPB PBCore - Zipped (Batch Ingester)
AAPB PBCore - Zipped
as the typeKYUK_migration5.zip
file downloaded in Step 1Asset
s. Copy its ID to your computer's clipboardPhysicalInstantiation
,DigitalInstantiation
, orEssenceTrack
)Asset
. Edit and save the record (no need to make any changes)2/pushes/new
Asset
's ID into the text boxThe following IDs are missing child record(s): <Asset ID>
The following IDs are not found in the repository: fake-id
error message2 This will force the validation status to reevaluate
Notes
The text was updated successfully, but these errors were encountered: