Paige,
You could take a look at this - https://wiki.harvard.edu/confluence/display/LibraryStaffDoc/Harvard+Library+Open+Source+Project+Considerations
Randy
On Jun 8, 2017, at 5:00 AM, CODE4LIB automatic digest system <[log in to unmask]<mailto:[log in to unmask]>> wrote:
There are 6 messages totaling 331 lines in this issue.
Topics of the day:
1. Functional requirements for open-source repositories (4)
2. worldshare management services (2)
----------------------------------------------------------------------
Date: Wed, 7 Jun 2017 11:34:08 -0400
From: Paige Walker <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Functional requirements for open-source repositories
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
[log in to unmask]<mailto:[log in to unmask]>
------------------------------
Date: Wed, 7 Jun 2017 16:08:23 +0000
From: "Murray, Gregory" <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Re: Functional requirements for open-source repositories
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"
<[log in to unmask]<mailto:[log in to unmask]> on behalf of [log in to unmask]<mailto:[log in to unmask]>> 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
[log in to unmask]<mailto:[log in to unmask]>
------------------------------
Date: Wed, 7 Jun 2017 09:46:54 -0700
From: Kyle Banerjee <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Re: Functional requirements for open-source repositories
Hi Paige,
Most libraries (including every one I've worked at) create a list of
required, preferred, and optional requirements. The basic idea is you make
a grid and check off which of those requirements is supported and move
forward from there.
However, the devil is in the details and the meaning of the word "support"
is so slippery as to be virtually meaningless in both the open source and
proprietary spheres. Even in a perfect world where all software bugs have
gone extinct, support for standards, functions, technologies, and processes
is inevitably based on assumptions of needs which in turn presume things
like workflows, data, etc. -- so it is common to find yourself where a
product can legitimately claim to support exactly what you need and be
totally useless even before you consider whether the product is a good fit
for your environment. Conversely, the mechanisms through which a product
behaves may be able to easily achieve what you need even though it
theoretically doesn't support it at all.
The most important thing is to understand what you need and the mechanisms
by which various products can meet those needs. I personally feel there is
no substitute for talking directly to people with intimate understanding of
your needs who can provide a balanced picture of how a product might meet
your needs.
kyle
On Wed, Jun 7, 2017 at 8:34 AM, Paige Walker <[log in to unmask]<mailto:[log in to unmask]>>
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
[log in to unmask]<mailto:[log in to unmask]>
------------------------------
Date: Wed, 7 Jun 2017 11:28:25 -0600
From: Christopher Davis <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Re: Functional requirements for open-source repositories
Paige,
Kyle's reply to your message reminds me if an important truth which I learned a few years ago- no software app or system (open source or proprietary) will succeed in this world without an open and active support community made up of users and developers. How many people actually pay Microsoft for technical support these days? Instead, when one has a problem, they search or ask a forum of users and developers for a solution.
If software does not offer such a community to my project (even if it offers every feature under the sun and is bug free), then I do not consider it. Thanks to Terry Reese's advice, I will always look at the interoperability of software and protocols as well (I think that healthy support communities and interoperability almost always come hand-in-hand though).
FWIW,
Christopher Davis
Uintah County Library
On June 7, 2017 10:46:54 AM MDT, Kyle Banerjee <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi Paige,
Most libraries (including every one I've worked at) create a list of
required, preferred, and optional requirements. The basic idea is you
make
a grid and check off which of those requirements is supported and move
forward from there.
However, the devil is in the details and the meaning of the word
"support"
is so slippery as to be virtually meaningless in both the open source
and
proprietary spheres. Even in a perfect world where all software bugs
have
gone extinct, support for standards, functions, technologies, and
processes
is inevitably based on assumptions of needs which in turn presume
things
like workflows, data, etc. -- so it is common to find yourself where a
product can legitimately claim to support exactly what you need and be
totally useless even before you consider whether the product is a good
fit
for your environment. Conversely, the mechanisms through which a
product
behaves may be able to easily achieve what you need even though it
theoretically doesn't support it at all.
The most important thing is to understand what you need and the
mechanisms
by which various products can meet those needs. I personally feel there
is
no substitute for talking directly to people with intimate
understanding of
your needs who can provide a balanced picture of how a product might
meet
your needs.
kyle
On Wed, Jun 7, 2017 at 8:34 AM, Paige Walker
<[log in to unmask]<mailto:[log in to unmask]>>
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
[log in to unmask]<mailto:[log in to unmask]>
------------------------------
Date: Wed, 7 Jun 2017 14:46:20 -0400
From: Eric Lease Morgan <[log in to unmask]<mailto:[log in to unmask]>>
Subject: worldshare management services
For libraries who subscribe to OCLC’s Worldshare Management Services, is there a way to: 1) create a set of records of interest, and 2) export those records in MARC (“communications”) format? I’m talking about back-end operations here, not public consumption interfaces. Inquiring minds would like to know. —Eric Lease Morgan
------------------------------
Date: Wed, 7 Jun 2017 19:10:14 +0000
From: "McDonald, Stephen" <[log in to unmask]<mailto:[log in to unmask]>>
Subject: Re: worldshare management services
1) Yes
2) Yes
This can be done through the WorldShare Collection Manager. The Collection Manager does not need a subscription to WorldShare Discovery, or any other extra subscription; it is available to any member of OCLC. Collection Manager is designed for collections of electronic resources, and provides a knowledge base of many hundreds of e-resource collections. But it can also be used to create local collections of print or electronic titles.
There are two types of local collections you could create:
* a collection of titles loaded from a KBART file. The file can include OCLC numbers, or can be linked to OCLC records after loading.
* a query collection. This query will search WorldCat and produce a list of titles matching the query.
Once you have a collection, you can download the MARC records. You can choose to have downloads come through the Collection Manager interface, or have OCLC set up an FTP download site for you. The files will be in standard MARC format, with a .dat extension.
There may be other methods of doing similar things specifically for WorldShare Discovery customers that I am not familiar with.
It is also possible to do a batch search in OCLC Connexion Client, and export the records into a file. You may not even need something as complicated as Collection Manager, depending on exactly what you want to do.
Steve McDonald
[log in to unmask]<mailto:[log in to unmask]>
-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Eric Lease Morgan
Sent: Wednesday, June 7, 2017 2:46 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [CODE4LIB] worldshare management services
For libraries who subscribe to OCLC’s Worldshare Management Services, is there a way to: 1) create a set of records of interest, and 2) export those records in MARC (“communications”) format? I’m talking about back-end operations here, not public consumption interfaces. Inquiring minds would like to know. —Eric Lease Morgan
------------------------------
End of CODE4LIB Digest - 6 Jun 2017 to 7 Jun 2017 (#2017-130)
*************************************************************
