Page History

...

Steps involved:

Gather common data

• Comparable forms which are set to gather common data
  OR
• Separate email aliases, as we have now, which are set to push email to a common tracking system.  The tracking system would then ideally give IP, DNS, Browser/OS, Referring URL.
• If permissions are not sent to the tracking system, we may need a procedure to look them up.

Access to each others systems and information

• Ordering/Payment info - Voyager, EBSCOnet, etc.
• Access to one another's e-resources from "on-campus" (VPN) and "off-campus" (remotely) 

Common responses and procedures - wiki?

...

Access to all relevant systems - is

• Is there a need to inform vendors that this group may be working on each others issues?

Ingest problem into common tracking system

• What changes at each CUL required?  i.e. Cornell does not gather some of the user info that Columbia does via form.   
  • What info is most useful or essential?  IP/DNS, patron permissions?, Browser?, Referring page

All staff looking at each others issues - milestone - how long does this need to go on before we move to next phase?

• Period of training/adjustment for each CUL as staff adjust to the new tracking systems. (This is a public service; it should be done well!)
• Able able to respond to each others lists & assign issues within the tracking system.

Begin joint troubleshooting on XXXX

• What issues immediately go to home institution?
• What can be handled jointly?
• What must wait until X system is better integrated?

Possible Issues to Address

• Union issues?
• Privacy issues?
• Vendors working with one CUL on the other's behalf, i.e. we're no their "contact of record"