LISTSERV mailing list manager LISTSERV 16.5

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  June 2017

CODE4LIB June 2017

Subject:

Re: CODE4LIB Digest - 6 Jun 2017 to 7 Jun 2017 (#2017-130)

From:

"Stern, Randy" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 8 Jun 2017 06:07:25 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

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)
*************************************************************

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

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
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