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
We need ingest routines that (1) allow for the creation of SIPs for complex objects outside of the repository environment and (2) that result in DIPs with no further intervention from library staff. To elaborate, the parent object would be created as part of the ingest process, and, with no further intervention on the staff side, the ingest process would take in all the constituent files as well as the descriptive, structural, technical, and preservation metadata. The ingest process would then create a DIP that understands the relationships among the files in order to and facilitate navigation in the access layer.
This is needed because (1) we use external tools to create our complex objects and (2) our objects contain many constituent files that are not separately described. It is not sustainable or cost effective for us to manually build digital objects in the repository environment.
A use case:
we currently ingest METS digital objects that are exported from the Archivists Toolkit/ArchivesSpace. If needed, we have the capacity us to transform the METS into a different format for ingest to Hybox. For a detailed description see the 201500305 news item on the BLC wiki: http://blcspecialcoll.pbworks.com/w/page/73429475/FrontPage
The text was updated successfully, but these errors were encountered:
We need ingest routines that (1) allow for the creation of SIPs for complex objects outside of the repository environment and (2) that result in DIPs with no further intervention from library staff. To elaborate, the parent object would be created as part of the ingest process, and, with no further intervention on the staff side, the ingest process would take in all the constituent files as well as the descriptive, structural, technical, and preservation metadata. The ingest process would then create a DIP that understands the relationships among the files in order to and facilitate navigation in the access layer.
This is needed because (1) we use external tools to create our complex objects and (2) our objects contain many constituent files that are not separately described. It is not sustainable or cost effective for us to manually build digital objects in the repository environment.
A use case:
we currently ingest METS digital objects that are exported from the Archivists Toolkit/ArchivesSpace. If needed, we have the capacity us to transform the METS into a different format for ingest to Hybox. For a detailed description see the 201500305 news item on the BLC wiki: http://blcspecialcoll.pbworks.com/w/page/73429475/FrontPage
The text was updated successfully, but these errors were encountered: