Questions? Just contact us!

Login

Username

Password

Remember Login

Forgot your password?

Problem solving protocol

Resources for trouble-shooting
Tips for searching Navigator
Reclamation, batch loading etc. (why holdings may be inaccurate in WorldCat)
NRE (Navigator Request Engine)
Functional experts

Triage - the first process of reading and handling email problem reports.

Triage experts (only these individuals should perform triage): Mark, Nancy, Adriene, Jean, Michael, Shirien, Al


AM
8-12


PM
1-5

      


AM
8-12


PM
1-5

December 12
Jean
 --

January 1

none
none
December 15
Al
Michael
January 2
Michael
Kyle
December 16
Shirien
Al
January 5
Nancy
Adriene
December 17
Michael
Jean
January 6
Kyle
Jean
December 18
Jean
Shirien
January 7
Al

Kyle
December 19
Nancy
Nancy
January 8
Michael
Mark
December 22
Shirien
Mark
January 9
Kyle
Adriene
December 23
Mark
Shirien

January 12
Al

Adriene
December 24
none
none
January 13
Shirien
Mark
December 25
none
none
January 14
Michael
Shirien
December 26
Al
Al

January 15
Kyle
Mark
December 29
Jean
Michael
January 16
Jean
Kyle
December 30
Adriene
Nancy






December 31
none
none






Instructions:
1. If you read a message and do not take action, be sure to re-set the status as unread so someone else will see and read it.

2. If you read a message then you take responsibility for resolution.  Triage experts should call in addition to emailing front line responders for anything judged to be CRITICAL.

3. Always add a flag:
a. IN PROCESS (consulting with others, investigation, etc.)
b. CRITICAL, in BASECAMP
c. NON-CRITICAL, in BASECAMP
d. LOW PRIORITY (to work on later)
e. FINISHED
4. Reply to sender indicating we're working on it. Ask follow-up questions as necessary.

Notes for Triage experts:
Communication concerning significant problems
If two or more Triage experts confer and determine that information should be broadly disseminated then they will post an email message to Summit Borrowing Committee <summit-circ@lists.uoregon.edu> and Summit Migration Designated Contacts <summit-contacts@lists.uoregon.edu>.
Reports concerning new patron loads
When a problem report is just a report of a new patron load, please go to the problem reports on Basecamp, find the Summit Patron Load thread and add it as a comment.
 

Front line responders

When reviewing Navigator problem reports forwarded by Triage Extperts, the "front line responders" will take into consideration several factors:

Has this been reported previously?  If so, do we know the answer?
Provide an answer or reply?
NO. In some situations reports will be logged and reviewed, and due to time constraints the reviewer will not respond individually to the person submitting the report.
YES. If the reviewer determines that a response is necessary: answers will be supplied by referring to an Alliance web page whenever possible.
If the answer is known but not yet documented on a web page, it will be added to the web site as soon as possible.
When reviewing a problem that seems new (not yet reported or noted):
  • Is it repeatable?
  • Different user accounts? Different web browsers?
  • additional suggestions will be added here, for trouble-shooting specific kinds of problems (patron record loading, patron log in, staff log in, availability or holdings display, etc.)
Report it to OCLC. If the answer is not known, and the problem requires attention, it will be reported to the appropriate OCLC staff.
  • an individual issue for a single site, that affects that site only: will be reported, or may on occasion be reported by an institution contact that has been working with OCLC and the Migration Team
  • an issue that affects multiple sites, or the solution might affect multiple sites: will be reported only by one of the front line responders
  • an issue that will affect the look and feel, or operation, of Summit for all members: may be reported only by primary Alliance staff or designee (John Helmer, Kyle Banerjee, Nancy Nathanson, Mark Kibbey)