1. Tracking electronic resources acquisitions: Using a helpdesk system to succeed where your ERMS failed Charleston Conference 2009 Xan Arch Electronic Resources and Technology Librarian Acquisitions Department Stanford University Libraries Jason Price, Ph.D. Science Librarian Head of Collections & Acquisitions Claremont Colleges' Library

2. The ERMS promise - 2005 FLOWCHART

3. What was delivered “With [our ERMS] we have all the information in one place” http://www.weewonderfuls.com/2006/02/huh.html Licenses Contacts Notes Status indicator Reminders Access info

4. Reality of Claremont’s e-resource acquisitions workflow

5. Some key advantages of using a ticketing system for ERA Designed to track ‘issues’ through stages to resolution Structures ‘metadata’ relating to an issue and shares it with others enabling coordination Flexible enough to allow a customized set of steps for each issue & distributed implementation Collects email trail relating to each ‘issue’

6. Stanford’s solution Xan Arch Electronic Resources and Technology Librarian Stanford University Libraries

7. Selector License Negotiations Ordering Unit Payments Activation Cataloging What we had: Defining our process What we had: Defining our process Tracking our orders

8. What we needed: Defining our problems What we needed: Defining our problems

9. Enterprise-level bug tracking software from Atlassian Already in use in our Digital Library department Finding a solution Finding a solution

10. Each order goes through the same steps o In Progress – Licensing o In Progress – Ordering o In Progress – Electronic Resources o In Progress – Metadata JIRA notifies the department or individual by email when they are required to act on an issue Standardized: Solution Standardized: Solution

11. Centralized: Solution Centralized: Solution The web form

12. Transparent: Solution Transparent: Solution Display in Wiki

13. JIRA Workflow - Acquisitions

14. Completely in place in Acquisitions department Less established in Collections, some selectors initiating orders through webform, others still sending email Some types of purchases still ambiguous – major database renewals, new e-journals Recent developments have pushed adoption further along A work in progress A work in progress

15. The future The future Use of JIRA for other projects in Acquisitions Moving webform to Drupal forms

16. Questions ? Questions ?

17. Claremont’s solution: eRATS in Footprints by Numara Jason Price Claremont Colleges’ Library Claremont University Consortium

18. Claremont’s eRATS was designed to address specific problems: In order of importance: 1.Delays (or loss!) due to dropped communication 2.Incomplete listing/activation of resources 3.Standardization of required metadata 4.Lack of transparency as to resource progress

19. Tracking-system supported workflow

20. Stage 0: Resource request form

21. Stage 1: Under Review

22. Tracking-system supported workflow

23. Stage 2: In negotiation

24. Tracking-system supported workflow

25. Resource fully available 3 Resource fully implemented Acquisition staff implements 2 Collection librarians determine 1 Stage 3: Pending activation

26. Next steps Beta – then implementation Configure public display of progress Design Acq reports (delivered from Footprints) Output to ERM?

27. Summary / Overview “Smart” Checklist –Periodic required decisions as stage changes –Shared in real time Workflow-based –Each update noted in history entry & encourages indication of next step –Issues can be assigned to one or more people for the next action(s) Information repository –‘Issues’ (resource records) can send and receive email –Stored as one text field—fully searchable –Appropriate metadata extracted into fixed fields as available