Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. "Topic":  Enter a value, such as the name of the resource involved.  Example: roper ipoll, books24x
  2. "Other staff involved":  If you collaborated with other staff, add their names.
  3. "How did patron find us": Libit-l, almost always.  Might be Proquest, personal email.
  4. "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:
    1. #blockednetid - patron netid blocked, probably due to a compromised netid, and/or an excessive downloading event
    2. #cookies - issue solved by clearing cache and cookies
    3. #excessivedownload (maybe #excessiveDL for brevity)- publisher notification of an excessive downloading event
    4. #ezproxy - resource needed to be added to ezproxy, or needed an ezproxy tweak
    5. #eternal - referring to issues which seem to take forever to resolve
    6. #festering - well, we just liked this one
    7. #holdings - the holdings information was incorrectly represented in our catalogs
    8. #openurl - issues related to openURLs, such as the problem reports we get from ProQuest
    9. #payment - we have not paid the publisher, either through our fault or theirs
    10. #permit - permits associated with the patron netid don't allow access to CUL resources
    11. #url - issues related to the url, such as link no longer working
    12. #walkthru - spent time with the patron on the phone, or through email, explaining each step of the process to get access
    13. #content #missing_content - content is missing; may be a corrupt file, or a pdf which is not there
    14. #activation - resource needs to be activated, or re-activated

...