<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2769" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#008080 size=2>Scott,</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#008080 size=2>I recognize your concern and think a
lot of it has to do with your institution's policy and who is responsible for
providing which service. If the policy is that DSpace is used as a repository
for archiving/long term preservation, the policy will likely be that
everything that is entered into DSpace can not be deleted/modified. E.g. it is
archived and can only be deleted by authorized persons, because of retention
times and/or specific (user) requests.</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2>In case of Dr. Smith, if he is still
working on his document (e.g.. part of the creation process and not yet ready
for archiving) he can not blame DSpace/the library when something goes wrong in
this part of the process. Of course there can and should be another
safety-net provided by the IT department to keep content/files that are
under construction available for their users in case a local PC fails or a user
makes a mistake. This should be taking care of by the (normal) IT services
provided to university users. It will be part of their (server) back-up
services, when Dr. Smith works on a IT supported network drive.</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#008080 size=2>Hope this helps a bit in your
discussion. In any case try to include your local IT department in these
discussions and make them feel responsible as well.</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#008080 size=2>Regards,</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#008080 size=2>Peter</FONT></DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #008080 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=smuir1@emich.edu href="mailto:smuir1@emich.edu">Scott P. Muir</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=dspace-general@mit.edu
href="mailto:dspace-general@mit.edu">dspace-general@mit.edu</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, January 04, 2006 10:40
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [Dspace-general] DSpace
Archiving</DIV>
<DIV><FONT face=Arial color=#008080 size=2></FONT><FONT face=Arial
color=#008080 size=2></FONT><FONT face=Arial color=#008080 size=2></FONT><FONT
face=Arial color=#008080 size=2></FONT><FONT face=Arial color=#008080
size=2></FONT><FONT face=Arial color=#008080 size=2></FONT><FONT face=Arial
color=#008080 size=2></FONT><FONT face=Arial color=#008080 size=2></FONT><FONT
face=Arial color=#008080 size=2></FONT><FONT face=Arial color=#008080
size=2></FONT><BR></DIV>I am envisioning the following situation<BR><BR><BR>In
May Dr. Smith enters a document into the DSpace repository. Over <BR>the
next few days through a series of edits, Dr. Smith accidentally <BR>deletes
the document out of DSpace, but isn't aware of the <BR>mishap. Dr. Smith
then leaves for the summer. In September, Dr. <BR>Smith comes back,
tries to look at the document and discovers it is <BR>not there. Dr.
Smith then calls the library demanding to know what <BR>happened, and
informing the library that the missing document was the <BR>only copy.
Another scenario could have a document become corrupted <BR>through some bad
editing, e.g. poor use of find/replace.<BR><BR><BR>We are exploring this on
two tracks: 1- not letting anyone, but a <BR>very few defined number of
people, delete or replace documents once <BR>they are in the repository or 2)
developing a comprehensive long term <BR>strategy for retention of backups of
the documents, etc, in DSpace so <BR>that we could restore a
document.<BR><BR>Has anyone else discussed this and come up with what you feel
is an <BR>appropriate solution?<BR><BR>Thanks for the input.<BR><BR>Scott P
Muir<BR>Associate University Librarian<BR>Bruce T. Halle Library, Room
200F<BR>Eastern Michigan University<BR>955 West Circle Drive<BR>Ypsilanti,
MI 48197-2207<BR><BR>734.487.0020 x2222 (voice)<BR>734.484.1151
(fax)<BR><A
href="http://www.emich.edu/halle/">http://www.emich.edu/halle/</A><BR><BR><A
href="mailto:scott.muir@emich.edu">mailto:scott.muir@emich.edu</A>
<BR><BR>_______________________________________________<BR>Dspace-general
mailing list<BR><A
href="mailto:Dspace-general@mit.edu">Dspace-general@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/dspace-general">http://mailman.mit.edu/mailman/listinfo/dspace-general</A><BR></BLOCKQUOTE></BODY></HTML>