Icon - KMLM List KMLM List

View email archives for the history of this mailing list.

List Home All Archives Dates Threads Authors Subjects
seruinfo - RE: [seruinfo] How does SERU fit into your Library workflow? Message Thread: Previous | Next
  • To: "Davis, Anthony" <anthonydavis@xxxxxxxxxxxxxxxxxxxxxx>, "Selden Lamoureux" <selden_lamoureux@xxxxxxxx>, <seruinfo@xxxxxxxxxxxxx>
  • From: "Anne Campbell" <acampbell@xxxxxxxxxxxx>
  • Date: Thu, 14 Jul 2011 16:09:42 -0400
Send Email to seruinfo@list.niso.org:
Send new message
Reply to this message

Thank you for your response Anthony.  Sounds like you’ve implemented an excellent procedure.  I want to propose that we at Swets to a similar process.  We have a tool called License Bank.  I want to include SERU (as you have done in your Verde Licensing Module) and then reference the Publishers who are on the registry.  In the same breath, we can the indicate at the customer level if they are registered with SERU.  So, when we send orders to pubs, we can indicate the SERU “agreement” between the two parties. 

 

Anne

 

 

Anne Campbell

E-Processing Manager

 

Ask about our COUNTER compliant, instantly accessible usage statistics!

SwetsWise Selection Support

Analyze. Compare. Decide.

 

SWETS

904 Black Horse Pike

Runnemede, NJ 08078

T 856-312-2150

F 856-632-7150

E acampbell@xxxxxxxxxxxx

 

Like us on Facebook

Follow us on Twitter

 

Swets Simplifies - ISO 9001:2008 Globally Certified -EContent 100 Company since 2003

 

CONFIDENTIALITY NOTICE: This electronic message, including any attachment(s), is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this message or an agent responsible for delivering it to the intended recipient, please notify the sender immediately by replying to this message and then delete the original message and any copies of it from your computer system. Any use, dissemination, distribution, or reproduction of this message and/or any of its attachments (if any) by unintended recipients is strictly prohibited and may be unlawful.

 

 

From: Davis, Anthony [mailto:anthonydavis@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, July 12, 2011 4:50 PM
To: 'Selden Lamoureux'; seruinfo@xxxxxxxxxxxxx; Anne Campbell
Subject: RE: [seruinfo] How does SERU fit into your Library workflow?

 

When a publisher or vendor indicates that they grant access under SERU, our internal process is simplified.  We’re using Verde, so I’ve set up a default license in the Verde licensing module based on our best interpretation of how the SERU agreement maps to the ERMI licensing values.  I simply attach the default license to the electronic resource record and the acquisitions workflow proceeds as if I had approved a negotiated license.

 

Anthony Davis Jr.

Electronic Resources & Copyright Librarian

Pollak Library

California State University, Fullerton

Ph (657) 278-5838

Fax (657) 278-2439

anthonydavis@xxxxxxxxxxxxx

 

 

-----Original Message-----
From: seruinfo@xxxxxxxxxxxxx [mailto:seruinfo@xxxxxxxxxxxxx] On Behalf Of Selden Lamoureux
Sent: Tuesday, July 12, 2011 1:42 PM
To: seruinfo@xxxxxxxxxxxxx; Anne Campbell
Subject: Re: [seruinfo] How does SERU fit into your Library workflow?

 

 

Hi Anne.  I'm also curious.  At NCSU we make it part of the initial Acquisitions process, asking staff to check the SERU Registry to see if the publisher is on it.  But we could do more to promote the use of SERU to publishers who aren't aware of it.

 

 

Several colleagues have shared their "standard" SERU emails:  when the publisher is registered, asking if the publisher would like to use SERU and Copyright law for the order; when the publisher isn't on the SERU Registry, asking if they would be interested in more information about SERU.

 

 

The SERU Standing Committee has been pulling together some preliminary documents to post to the SERU site on How to DO SERU.  I'd be very interested in hearing how libraries and publishers have been going about it, and especially glad to have examples (templates, emails, or forms) to share on the site.

 

 

Thanks for asking

Selden

(Co-Chair, SERU Standing Committee)

********************************************

Selden Durgom Lamoureux

Electronic Resources Librarian

North Carolina State University Libraries

Campus Box 7111

Raleigh, NC 27695-7111

 

phone:  919-513-2728

fax:  919-515-7282

email:  selden_lamoureux@xxxxxxxx

********************************************

 

 

>>> "Anne Campbell" <acampbell@xxxxxxxxxxxx> 7/12/2011 4:35 PM >>>

Hi all,

 

 

 

I'm curious to know how Libraries are adding SERU to their internal

workflow when purchasing electronic content.

 

 

 

Thanks in advance for any feedback supplied.

 

 

 

Anne

 

 

 

 

 

Anne Campbell

 

E-Processing Manager

 

 

 

SWETS

 

904 Black Horse Pike

 

Runnemede, NJ 08078

 

T 856-312-2150

 

F 856-632-7150

 

E acampbell@xxxxxxxxxxxx <mailto:acampbell@xxxxxxxxxxxx

 

 

 

Like us on Facebook

<blocked::http://www.facebook.com/pages/...NJ/Swets-Americas/15010564168

0717>

 

Follow us on Twitter

<blocked::file:///C:/Documents%20and%20Settings/ballxkm/Application%20Da

ta/Microsoft/Signatures/twitter.com/Swets_Americas> 

 

 

 

Swets Simplifies - ISO 9001:2008 Globally Certified -EContent 100

Company since 2003

 

 

 

CONFIDENTIALITY NOTICE: This electronic message, including any

attachment(s), is intended only for the person or entity to which it is

addressed and may contain confidential and/or privileged material. If

you are not the intended recipient of this message or an agent

responsible for delivering it to the intended recipient, please notify

the sender immediately by replying to this message and then delete the

original message and any copies of it from your computer system. Any

use, dissemination, distribution, or reproduction of this message and/or

any of its attachments (if any) by unintended recipients is strictly

prohibited and may be unlawful.

 

 

 

 

 

 


By Date: Previous | Next Current Thread By Thread: Previous | Next