...
- "Topic": Enter a value, such as the name of the resource involved. Example: roper ipoll, books24x
- "Other staff involved": If you collaborated with other staff, add their names.
- "How did patron find us": Libit-l, almost always. Might be Proquest, personal email.
- "Notes": Keep it brief. We have discussed using hashtags to simplify record keeping, and possibly use the hashtags to survey which types of problems arise frequently. Possible hashtags:
- #activation - resource needs to be activated, or re-activated; replacement access needs purchased
- #blockednetid - patron netid blocked, probably due to a compromised netid, and/or an excessive downloading event
- #browser - issue related to the browser; ex. cache and cookies, browser extensions, specific browser issues
- #excessivedownload (maybe #excessiveDL for brevity)- publisher notification of an excessive downloading event
- #ezproxy - resource needed to be added to ezproxy, or needed an ezproxy tweak
- #eternal - referring to issues which seem to take forever to resolve
- #festering - well, we just liked this one
- #holdings - the holdings information was incorrectly represented in our catalogs
- #IP- IP list incorrect at vendor's end
- #missing_content - content is missing; may be a corrupt file, or a pdf which is not there, author does not allow access to article
- #openurl - issues related to openURLs, such as the problem reports we get from ProQuest
- #payment - we have not paid the publisher, either through our fault or theirs
- #permit - permits associated with the patron netid don't allow access to CUL resources
- #url - issues related to the url, such as link no longer working
- #vendor_records - ex. records pulled for unknown reason, or record not pulled out in time (Safari), cataloging errors
- #walkthrough - spent time with the patron on the phone, or through email, explaining each step of the process to get access
...