4/20/2017 - Purchase suggests

Owned by Charlotte Whitt
Last updated: Apr 25, 2017
ErikHow do we start our selection process? Pain points / comments (add initials)
TAMU

uses an online request form, which goes to a department where they perform triage on it, and then sends it to the appropriate department. E.g. if it is

  1. a monograph, or one-time purshase then it is send to the Acquisition Department
  2. a new serial request it goes to the collection librarian, and she adds it to a new serial database. TAMU uses an Access program created by a staff member a few years ago
  3. a database request, then the selector gets contacted.

Right now TAMU have their request data a lot of places. Coral is used as their ERM system, and one of the things TAMU are working on is to incorporate a request module within Coral, so that all the submitted requests, are feed in to Coral, rather than being stored in many different places. The request module in Coral would also include data about a trial requests - and these data would not be in amongst TAMU's actual subscriptions. If TAMU then decide to purchase or subscribe to on of these resources, then they would be able to 'hit a button' and put all data into TAMU's regular resource module.

 Implementing the Coral solution, and have all data in the right place, will save TAMU time by eliminate time to duplicate the work and all the information (EH)
Chicago

accepts a variety of ways to submit selection requests. E.g.

  1. a patron request form on their webpage. Through the form Chicago gets requests from faculty, student, and alumni
  2. an email from the patrons, about things they have discovered in an unconditional way.
  3. the majority of requests come through the vendors, e.g. through GOBI, Harrassowitz, Anomaly (question), Catalina etc.
  4. a spreadsheet in Google from the selectors
  5. a pdf document
  6. a word document send by email
  7. print on paper, and even
  8. requests mentioned directly to the librarians
Get the requests in a huge variety of ways, and would not want to limit that in any ways of shape and form (SM)
Duke

has the same procedure as Chicago. E.g.

  1. Duke has a centralized email address for requests on e-resources, continued resources, monographs, packages, and databases
  2. use vendor tools similar to what Chicago does, and that is a big part of what they do.
  3. receive spreadsheet requests - which could be attached to a form

At Duke 8 order specialist are working across a variety of languages.

 

Acknowledge that setting up a system which can feed directly into some sort of an ERM tool can work for e-resources, packages, and databases, but it is difficult to envision a system where all monograph orders would come in. Worried if trying to funnel all types of single requests would create more work than today (BV)
MIT

would primarily submit orders through GOBI. For e-journals, and databases purchase requests would be retrieved through MIT's web-form, that would feed into MIT's CRM system.

The CRM system - the Request Tracker Ticket is updated by feed from:

  1. a centralized email for the acquisition department
  2. a Suggested Purchase Web form for patrons
A selector at MIT would submit orders through GOBI, or use the centralized email address if the title was not in GOBI. If it is an e-journal then the selector would use the webform (DL)