Re: Functional requirements for open-source repositories

From: Murray, Gregory <gregory.murray_at_nyob>
Date: Wed, 7 Jun 2017 16:08:23 +0000
To: CODE4LIB_at_LISTS.CLIR.ORG
Paige,

This site is out of date as far as the information, but it nevertheless
could serve as a template for the kinds of features/requirements you may
want to look for -- supported file types, metadata formats,
harvesting/interoperability, import/export, etc. etc.

http://www.rsp.ac.uk/start/software-survey/results-2010/

My institution used it when comparing IR systems a few years ago.

Best,
Greg

Gregory Murray
Director of Digital Initiatives
Princeton Theological Seminary Library



On 6/7/17, 11:34 AM, "Code for Libraries on behalf of Paige Walker"
<CODE4LIB_at_LISTS.CLIR.ORG on behalf of paigemariewalker_at_GMAIL.COM> wrote:

>Dear collective wisdom,
>
>The Digital Library Program at Boston College is investigating new special
>collections repositories as we plan to replace our current one (Digitool)
>in the next year. The last time we surveyed the field, we were looking
>primarily at proprietary platforms, which was reflected in our functional
>requirements.
>
>To those who have considered open-source models, Iım wondering how this
>was
>reflected in your functional requirements?
>
>Thanks in advance,
>Paige
>
>PS: Sorry for cross-posting!
>
>
>------------------
>
>Paige Walker
>Digital Collections & Preservation Librarian
>Boston College
>617-552-3306
>paige.walker_at_bc.edu
Received on Wed Jun 07 2017 - 12:08:28 EDT