LISTSERV mailing list manager LISTSERV 16.0

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  May 2013

CODE4LIB May 2013

Subject:

Re: On-going support for DL projects

From:

Tim McGeary <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 21 May 2013 15:25:25 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (108 lines)

I'm trying to see if I can lump my response to some of the responses above.
 Glad to see so much conversation around this.

We've considered setting up VMs, but even that can be quite costly,
especially if a project is or becomes dormant.  Developing a sustainable
"container" is certainly necessary.  Someone earlier said that the Library
often gets projects dumped on them to preserve longterm.  This isn't a
sustainable view of the Library.  These aren't booked dumped out of a
retiring faculty's office.  If one wants to use that comparison, then
Libraries need to assert authority to pick and choose what to maintain.
 Given that these projects usually involve actual faculty output rather
than a faculty's personal library of other people's output, that curation
needs to be more delicate.

Even exporting out of widely used applications, like Omeka, can be a
challenge.  What if it that project is using an Omeka from 4 versions
before?  Or what if the latest Omeka is supporting a lower PHP version than
the campus IT security standards allow?  This is no longer an easy problem
to solve from a technology standpoint because there, and will continue to
be, a growing number of scenarios to try to support.

I hesitate to want to use "it's broken" as a trigger to pull something down
because the impression could be that the Library can't support what it has
committed to support.  I'd rather there be term limits and re-evaluations
at a term limit.  Additionally in the face of decreasing funding, I'm not
seeing a lot of institutional prioritization that includes funding.  So the
expectation has to be support through neutral funding or less.

Tim


On Mon, May 20, 2013 at 10:06 AM, Edward M Corrado <[log in to unmask]>wrote:

> I agree with both Tom and Stuart. It is an easy problem to solve from a
> technology standpoint. It is, or least can be, a difficult one from a
> management standpoint. If institutional support is there figuring out the
> technology is easy. In this case, I'd start investigating the  technology
> part with something like Heritrix.
>
> Edward
> --
> Edward M. Corrado
>
> On May 20, 2013, at 0:58, Tom Johnson <[log in to unmask]>
> wrote:
>
> > That doesn't sound like an easy answer at all! Given that we all try to
> > play nice with institutional funding, all you've said is that in an ideal
> > world some other group will have a similar mandate. It doesn't get us (in
> > all seriousness) anywhere. Hopefully our institutions have higher
> > preservation goals! "collections policy" doesn't help at all--and may
> take
> > us backward.
> >
> >
> > On Sun, May 19, 2013 at 1:39 PM, stuart yeates <[log in to unmask]
> >wrote:
> >
> >> On 18/05/13 01:51, Tim McGeary wrote:
> >>
> >>> There is no easy answer for this, so I'm looking for discussion.
> >>>
> >>>    - Should we begin considering a cooperative project that focuses on
> >>>    emulation, where we could archive projects that emulate the system
> >>>    environment they were built?
> >>>    - Do we set policy that these types of projects last for as long as
> >>> they
> >>>    can, and once they break they are pulled down?
> >>>    - Do we set policy that supports these projects for a certain period
> >>> of
> >>>    time and then deliver the application, files, and databases to the
> >>> faculty
> >>>    member to find their own support?
> >>>    - Do we look for a solution like the Way Back Machine of the
> Internet
> >>>    Archive to try to present some static / flat presentation of these
> >>> project?
> >>>
> >>
> >> Actually, there is an easy answer to this.
> >>
> >> Make sure that the collection is aligned with broader institutional
> >> priorities to ensure that if/when staff and funding priorities move
> >> elsewhere that there is some group / community with a clear interest
> and/or
> >> mandate in keeping the collection at least on life support, if not
> thriving.
> >>
> >> Google "collections policy" for what written statements of this might
> look
> >> like.
> >>
> >> cheers
> >> stuart
> >> --
> >> Stuart Yeates
> >> Library Technology Services http://www.victoria.ac.nz/**library/<
> http://www.victoria.ac.nz/library/>
> >>
>



-- 
Tim McGeary
[log in to unmask]
GTalk/Yahoo/Skype/Twitter: timmcgeary
484-294-7660 (cell)

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager