Deleting Items (SobekCM Builder / Bulk Loader)

General Concept

Digital libraries and other trust institution systems support permanence of materials for preservation as well as for access. Access needs continue even if items are removed for some reason. For instance, if an item was removed or suppressed because of copyright concerns, then the metadata would still need to remain to support ongoing citation needs. Because citation needs continue even when items cannot be available online, digital libraries and other trust institution systems normally have policies for how to update metadata for items that have been removed from public access (e.g.; UF procedure for handling removals).

Because most removals are actually suppressions or removals of files only and not metadata, actual deletions are rarely done.

Deletions can be done by Administrators following the policies of the institution by an administrator using a METS-based process or the online tools. Individual items can be deleted through the online interface ( View help here )

Process Description

To delete a number of items through the builder, you will need to either create SobekCM-compliant METS files, or download the METS files from the SobekCM system. This can be done with simple scripting or using the SMaRT Tool currently.

The RECORDSTATUS on the METS file should be set to DELETE. Then, the METS files can be uploaded (no folders necessary), into an incoming folder for the builder.

Before the builder will accept DELETE files from a folder, it must be configured to do so. Runnnig the configuration file in the config subfolder of the Builder app allows you to set all the flags for the incoming folders, and one flag governs whether DELETE METS are accepted.

Once the DELETE METS file is processed, the item will be deleted from the database, and the resources files will be moved into a top-level DELETE folder under the digital resource content folder. This is done as a precaution to ensure files are not completely deleted by accident.