Community updates (introductions, updates, implementations, plans, etc)
Updates on ocfl-index - creates a sql database that allows for hierarchical relationships and querying. andrew woods/harvard has been helping with testing things. aimed at creating a lightweight access layer to a storage root.
Purge/permanently remove a file from an object for legal or compliance reasons.
they still want to maintain a record that the file was there at some point, including the hash related to the file
trying to identify a way to record the purge, with a tombstone file including metadata about the file and the sha512 of the purged file.
how do you preserve the UUID? at stanford they retain information in the repository that says the object at one time existed but don't really display this to end users, only for staff
its infrequent that this happens so most places say its ok if its hard.
purpose of the extension: system that is already running that builds up bagits for media objects, for museums and exhibitions. they are delivered from different cultural areas with different file names. started to clean up the file names, table with old name and new name. with ocfl this renaming isn't necessary anymore. upgrading bagit tool to ocfl.
how to differentiate between object extensions and file root extensions, what is the difference?
University of Chicago has been migrating stuff into OCFL.
Thinking through tombstones is helpful to hear about.
Writing OCFL into an NEH grant application they are applying for. They'll send the editors the grant application and editors can perhaps write a letter of support.
John Young is creating something similar to Seth's ocfl-index project.
Next community meeting: Wednesday June 8th 12am GMT / 7pm EDT / 4pm PDT | Thursday June 9th 10am AEDT (Convert to your time zone)