Page History

...

• Web based system
• Must support two options for login. Both should be persistent and have very long timeouts so that staff don't have to log in repeatedly. (Zsuzsa: there are desks that are staffed by students who turn over very frequently. Maintaining who has access rights with every staff change would become too much of an overhead. The other issue is that it is more convenient and less threatening for desk staff, so not having it would make the system harder to sell)
  • CU WebAuth based for individual login
  • Location/Workstation based shared login for staff and students working at help desks.
• Interface presents the question sequence on one page, with appropriate components expanding and contracting based on responses (JavaScript). Page design must assist in keeping the process of data entry quick and easy. Recording of most transactions needs to take less than 15 seconds. Optional questions must be clearly separated at the bottom of the page (see detailed sequence in 2/19/10 question draft from Zsuzsa).
• Need to know some details from login: date, time, which library, which department, what staff level. THIS NEEDS BETTER DEFINITION
  • both: know time, date
  • CU WebAuth - know user from login
  • Location/Workstation based - know location, department from login (though these would have to be maintained as settings with those accounts)
  • Zsuzsa: "Could system allow for personal preferences being set by computer?" – Is this about workstation based shared logins or detection of location for individual logins?
• System should have date and time fields prefilled with current date and time but these should be allowed to be changed
• System should allow the adding and editing of old entries as well and easy input of a sequence of entries at the same time
  • Assume there will be edit/submit for each but optimize to minimize data entry/time
  • Sequence: what fields should be carried forward from one submit to the next?

...