Hi Rosalyn,
Yes, I see the RDF and EAD preservation ingests as text files. The key
affordance of this model, in my mind, is flexibility. Metadata producers
can create and maintain their data in systems designed for that purpose on
a schedule that is decoupled from preservation ingest for digital o
in the preservation space you describe, the files would presumably be small
text files. if that's the case it might be useful to ask, what would
keeping the metadata separate from the content files afford you?
On Mon, May 9, 2016 at 9:26 AM, Andrew Weidner
wrote:
> Thanks for your replies, Stua
Thanks for your replies, Stuart and Brian.
The information you provided got me to thinking more generally about what
comprehensive preservation could look like for the digitized cultural
heritage materials we are managing. As a content administrator for an
access repository, I am primarily concern
>>
>> How do others approach this problem? Are there recognized best practices to
>> adhere to?
>>
I’m still trying to put the CDL model into practice. <
https://confluence.ucop.edu/display/Curation/D-flat >
And Stanford has similar but different model <
http://journal.code4lib.org/articles/84
There is a standard
https://en.wikipedia.org/wiki/Open_Archival_Information_System Which leads
to software like fedora commons.
There is also archive.org. For a low annual subscription you can have
fine-grained control over regular harvests of your web spaces (including
password protected web spac
Hi Code4Lib,
We are in the process of designing new workflows for preservation and
access of our digital stuff, and I'd like to get a sense of how people
understand digital objects in the preservation space.
My gut tells me that it might be useful for future digital
archivists/archaeologists to h