Access Problem Solving (digprob)
Managing the Messages to the esubs List
We use the esubs list as a way for vendors to contact us about title activation, changes in titles and packages, press releases, a way to tell us a site will be down, etc. Messages sent to the list are of course sent to everyone on the list (currently, Ellen, Kim, Jake, Walter, and Sally). So that we are sure that each message is dealt with, we agreed to the following procedures.
I. We agreed to assume that followup will happen automatically, without response by one of us to the list, for the following topics for the following people:
Kim
- Messages that need Ellen's attention (Kim will forward to Ellen)
- SD Connect (newsletter from Elsevier about ScienceDirect)
- Invoices (no matter what they are for)
- Swets FYI Access Confirmation messages (Kim will forward to appropriate expert)
Walter
- Barton coverage updates (once a week, comes out every Wednesday night)
- Serials Solutions (both the messages announcing that our bimonthly file of records is ready to download and any press releases or advertising that may come)
Jake
- Eye to Eye (newsletter from Ingenta)
- Ingenta
- JSTOR
- Project Muse
- SFX reports (message from SerCat)
- usage statistics (any message saying anything about usage stats)
- JAMA & Archives Alerting: Topic Collection Alert (just delete these; they won't stop coming!)
- IMF: forward messages about new titles and other news to Kate McNeill-Harman at Dewey.
II. For messages that don't fall into any of the categories listed above, we agreed that message would be handled by the package level expert. For example, if a message comes from Taylor & Francis, Jake will reply back to the esubs list (or actually, forward the message back to the list) to say "I've got it."
III. Jake will make sure that all messages each week either fall into the "automatic" category, or have been claimed. Each Thursday, Jake will review the list activity and forward back to the list any message(s) of which he is unsure of the status.