search

sul-dlss / preservation2017

Story repo for preservation core work done summer/fall 2017
0 stars 0 forks source link

Story: Implement a Preservation Policy strategy #22

Open LynnMcRae opened 6 years ago

LynnMcRae commented 6 years ago

While the default treatment for Preservation Core objects will be Moab + Local Archive + 2 Cloud copies, we already know one possible exception coming soon -- a policy to keep only archive copies of Google Scanned Books. Similar needs will likely arise in the future, e.g., making DPN or LOCKSS replication an option. Need the rudiments, likely just additional information housed in the object, to be defined at the DOR/Admin Policy level first.

julianmorley commented 6 years ago

I've been calling this a Replication Policy, since it deals with the placement of objects on replication endpoints. But it could just as easily be called the Archive policy, since it deals with the placement of archive objects.

We should pick one, though. Thoughts? Which best describes the goal here? (probably not Archive Replication Policy)

LynnMcRae commented 6 years ago

Archiplication? Archive is better than Replication so we avoid a policy that has "replicas only" as in the Google Books case -- sounds like we lost the original :) But I think "Preservation Policy" would be safest, since it covers something more complex like the google books case where Moab might be metadata only with archive objects carrying the content. Plus it's a policy for Preservation Core.

julianmorley commented 6 years ago

Preservation Policy it is, then!