Re: [CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Andrew Weidner]

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 object
bitstreams, and then export that metadata for preservation ingest and
versioning as deemed appropriate for the local environment.

Andrew


On Thu, May 12, 2016 at 10:13 PM, Rosalyn Metz 
wrote:

> 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, 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 concerned with the ability to retrieve
> > bitstreams and metadata from preservation cold storage in the event that
> we
> > lose data and our intermediate backup systems fail. I've visualized one
> > possible data restoration model in the following slides:
> >
> >
> >
> https://docs.google.com/presentation/d/1x3YlQbQUitaRLH1qVVWYHZVonrffzoAKJTY905PpjK8/edit?usp=sharing
> >
> > I'm curious what the C4L collective brain thinks about such an approach,
> > especially any pitfalls we should watch out for if we should choose to
> > implement this model.
> >
> > Andy Weidner
> >
> >
> >
> > On Wed, Mar 23, 2016 at 8:59 AM, Brian Kennison 
> > wrote:
> >
> > > >>
> > > >> 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/8482 >
> > >
> > > —Brian
> > >
> >
>

Re: [CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Rosalyn Metz]

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, 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 concerned with the ability to retrieve
> bitstreams and metadata from preservation cold storage in the event that we
> lose data and our intermediate backup systems fail. I've visualized one
> possible data restoration model in the following slides:
>
>
> https://docs.google.com/presentation/d/1x3YlQbQUitaRLH1qVVWYHZVonrffzoAKJTY905PpjK8/edit?usp=sharing
>
> I'm curious what the C4L collective brain thinks about such an approach,
> especially any pitfalls we should watch out for if we should choose to
> implement this model.
>
> Andy Weidner
>
>
>
> On Wed, Mar 23, 2016 at 8:59 AM, Brian Kennison 
> wrote:
>
> > >>
> > >> 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/8482 >
> >
> > —Brian
> >
>

Re: [CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Andrew Weidner]

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 concerned with the ability to retrieve
bitstreams and metadata from preservation cold storage in the event that we
lose data and our intermediate backup systems fail. I've visualized one
possible data restoration model in the following slides:

https://docs.google.com/presentation/d/1x3YlQbQUitaRLH1qVVWYHZVonrffzoAKJTY905PpjK8/edit?usp=sharing

I'm curious what the C4L collective brain thinks about such an approach,
especially any pitfalls we should watch out for if we should choose to
implement this model.

Andy Weidner



On Wed, Mar 23, 2016 at 8:59 AM, Brian Kennison  wrote:

> >>
> >> 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/8482 >
>
> —Brian
>

Re: [CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Brian Kennison]

>> 
>> 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/8482 > 

—Brian

Re: [CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Stuart A. Yeates]

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 spaces)

These two roads diverge in a yellow wood...

cheers
stuart


--
...let us be heard from red core to black sky

On Tue, Mar 22, 2016 at 9:12 AM, Andrew Weidner 
wrote:

> 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 have an object's descriptive metadata closely
> associated with the object's files in the same directory in a human
> readable plain text format. So that one directory would contain all of the
> object's files and descriptive metadata in an easy to read package.
>
> Alternatively, descriptive metadata for many objects could be stored in a
> single external file, say at the root of a preservation accession
> directory, according to a recognized standard like METS. That requires more
> work to reconstruct an object, and the linkage between an object's files
> and descriptive metadata is looser, but it seems more efficient.
>
> How do others approach this problem? Are there recognized best practices to
> adhere to?
>
> Thanks,
>
> Andy Weidner
>

[CODE4LIB] Preserving Digital Objects with Descriptive Metadata

[Andrew Weidner]

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 have an object's descriptive metadata closely
associated with the object's files in the same directory in a human
readable plain text format. So that one directory would contain all of the
object's files and descriptive metadata in an easy to read package.

Alternatively, descriptive metadata for many objects could be stored in a
single external file, say at the root of a preservation accession
directory, according to a recognized standard like METS. That requires more
work to reconstruct an object, and the linkage between an object's files
and descriptive metadata is looser, but it seems more efficient.

How do others approach this problem? Are there recognized best practices to
adhere to?

Thanks,

Andy Weidner