I believe it is possible to implement SUSHI without an ERM if you have programming/technical support. For example, here is a tool developed for this very application:
http://foss4lib.org/package/sushi-py
Has anyone on the list used this?
Thank you,
Margaret
……………………………………………………………
Margaret Hogarth, MLIS, MS Environmental Studies
Electronic Resources and Acquisitions
margaret_hogarth@cuc.claremont.edu
909-607-8839
x78839
Claremont University Consortium
Records Center
2048 West 11th Street
Upland, CA 91786
………………………………………………………..
From: SERIALST: Serials in Libraries Discussion Forum [mailto:SERIALST@list.uvm.edu]
On Behalf Of Evans, Thomas W
Sent: Thursday, September 06, 2012 7:20 AM
To: SERIALST@LIST.UVM.EDU
Subject: [SERIALST] SUSHI Implementation
Hello. I’m trying to decide if it would be worth our while to implement SUSHI. Currently we are using the clunky method of an Excel spreadsheet and having to contact each vendor for statistics. We are a small academic library, so we’re
talking 60 or so databases. I’m wondering if anyone can give brief responses to the following questions:
1) do you need an ERM to implement SUSHI
2) are there any cost/fees involved in implementation
3) some database vendors “provide” software for SUSHI implementation (ACM Digital for example); do we pay for this? how does it work (set up, proprietary software, etc.)
4) can we manipulate the data to suit our data needs
5) does a vendor need to be COUNTER compliant to participate in SUSHI
6) any pros/cons to SUSHI
I realize these questions are rather broad but I thank you in advance for any information you can give me. You can answer off list if you would rather.
Sincerely,
Tom Evans
Serials Librarian
Andrew L. Bouwhuis Library
Canisius College
2001 Main Street
Buffalo, NY 14208
Phone: 716-888-8418
Fax: 716-888-8420
***********************************************
* You are subscribed to the SERIALST listserv (Serials in Libraries discussion forum)
* To post a message: SERIALST@LIST.UVM.EDU
* For additional information, see
SERIALST Scope, Purpose and Usage Guidelines.
***********************************************