Hi Alston,

To build on what Tom has said (which is all correct), repository software
alone (whether it's DSpace or Fedora or Hydra or something else) cannot
meet all the needs of a preservation plan. Repository software is an
important piece to preservation, but you often need to have other local
policies and procedures in place to fully achieve your preservation goal.

For example, in that NDSA list of actions (for various levels) here's some
of the things DSpace can achieve for you:
* Record file fixity and reverify at fixed intervals
* Identify who has read/write/delete authorization, and provide
restrictions on those rights
* Use metadata to inventory/describe your files. By default DSpace
concentrates on descriptive metadata (think dublin core), but it does
capture basic metadata about file formats, file size, provenance, etc. You
can also add custom metadata to DSpace as you see fit

However, DSpace (like other repository systems) CANNOT provide some of
these activities on its own
* Store multiple copies of files in different geographic locations.
However, a simply backing up your DSpace can do this, or you could use
the Replication
Task Suite plugin
<https://wiki.duraspace.org/display/DSPACE/ReplicationTaskSuite> to
auto-export DSpace content to an external location or to a service like
DuraCloud <http://duracloud.org/>.  DuraCloud itself is a service that is
geared towards replication of content to different geographic locations (as
well as detailed fixity reports, etc).
* Monitor file format obsolescence issues and perform format
migrations/emulation. This is not something any repository platform can
achieve. There are tools out there that can give you feedback and software
that may be able to perform very specific format migrations or emulations,
but this decision process and activity still must be driven by a human.

So, DSpace can be used as a piece in a preservation platform. But, alone,
it is not a preservation system. Repository software (in general) often has
basic preservation capabilities (that complement a larger preservation
plan). But, repositories are more geared towards providing long term access
to content/research than to generating detailed preservation metadata,
format monitoring, etc. In this way, DSpace is no different from other
repository platforms.

I hope that helps give more context to the role of repositories and DSpace
in a local preservation plan.

Tim


On Fri, Jan 13, 2017 at 9:18 AM Tom Hutchinson <thutc...@swarthmore.edu>
wrote:

> Hi Alston,
>
> Those criteria are mostly orthogonal to the software used. I would say
> that DSpace won't get in the way of these goals (unlike some
> commercial hosted solutions). I would argue that it's well architected
> to facilitate preservation goals. The technical aspects of
> accomplishing them mostly requires general Linux administration
> knowledge (as opposed to a high level of application specific
> knowledge). However something like identifying when a file format is
> obsolete and what format to convert to will require human
> intervention.
>
> Regards,
>
> Tom
>
> On Thu, Jan 12, 2017 at 12:30 PM, Matveyeva, Susan
> <susan.matvey...@wichita.edu> wrote:
> > I am interested to know this, too.
> >
> >
> >
> > Thanks
> >
> > Susan
> >
> >
> >
> > From: dspace-community@googlegroups.com
> > [mailto:dspace-community@googlegroups.com] On Behalf Of Alston Cobourn
> > Sent: Thursday, January 12, 2017 11:26 AM
> > To: DSpace Community <dspace-community@googlegroups.com>
> > Subject: [dspace-community] NDSA levels of preservation
> >
> >
> >
> > Does anyone know how the most recent version of DSpace stacks up against
> the
> > NDSA levels of preservation as described in this chart?
> >
> > ________________________________
> >
> > NDSA Levels for Digital Preservation
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DSpace Community" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to dspace-community+unsubscr...@googlegroups.com.
> > To post to this group, send email to dspace-community@googlegroups.com.
> > Visit this group at https://groups.google.com/group/dspace-community.
> > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "DSpace Community" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to dspace-community+unsubscr...@googlegroups.com.
> > To post to this group, send email to dspace-community@googlegroups.com.
> > Visit this group at https://groups.google.com/group/dspace-community.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-community+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-community@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-community.
> For more options, visit https://groups.google.com/d/optout.
>
-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-community@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to