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
New event logs will include stages of tape ingestion. The provenance of tapes being sent to BIL should be noted as they are sent. Currently we plan to track things from the collection level, essentially the collection must be created for it to have an event log.
I'm thinking we should have the user specify through the portal that they plan to send tapes prior to sending them out. This could be logged through the proposed "/bil/tapes/" directory structure. Instead of "Create Collection" user would select something like "Send Tapes", give information about the tape itself and that form would trigger a bil_uuid to be created under /bil/tapes/username/bil_uuid. This way we can mitigate the possible issue of the user not creating a landing zone collection once the tapes are ingested at BIL. Validation and metadata ingestion steps would not be affected if this process were to come true.
This being the case, certain BIL staff would then need a view for tapes to update the state of the tape ingestion and have it be reflected in event_log. This view should give the staff member a view of all tapes (collections) under /bil/tapes/ and allow an update field with a drop down of the event types to submit the form and update the collection's status in the database. This can then be reflected in the user view to see what stage their tape is in. Once QC is finished and tape is confirmed to be fully ingested, validation and publication will be business as usual.
The text was updated successfully, but these errors were encountered:
New event logs will include stages of tape ingestion. The provenance of tapes being sent to BIL should be noted as they are sent. Currently we plan to track things from the collection level, essentially the collection must be created for it to have an event log.
I'm thinking we should have the user specify through the portal that they plan to send tapes prior to sending them out. This could be logged through the proposed "/bil/tapes/" directory structure. Instead of "Create Collection" user would select something like "Send Tapes", give information about the tape itself and that form would trigger a bil_uuid to be created under /bil/tapes/username/bil_uuid. This way we can mitigate the possible issue of the user not creating a landing zone collection once the tapes are ingested at BIL. Validation and metadata ingestion steps would not be affected if this process were to come true.
This being the case, certain BIL staff would then need a view for tapes to update the state of the tape ingestion and have it be reflected in event_log. This view should give the staff member a view of all tapes (collections) under /bil/tapes/ and allow an update field with a drop down of the event types to submit the form and update the collection's status in the database. This can then be reflected in the user view to see what stage their tape is in. Once QC is finished and tape is confirmed to be fully ingested, validation and publication will be business as usual.
The text was updated successfully, but these errors were encountered: