Staff web
- 1. StaffWeb in the Swift Consortium Advantages and Limitations Lloyd Brady – Swift Systems Administrator
- 2. Why StaffWeb? • Low bandwidth “footprint” • No Client needed (just a browser) • Ideal for “outreach” type services (as in outside the library) • Simple interface for volunteers
- 3. StaffWeb for Swift • Campaspe library “depots” • Mobile Libraries • Schools
- 4. Controlling Access • User Access policies – Everything turned on by default!!
- 5. Controlling StaffWeb Admin • Restrict access in User Access Policy • Modify System Admin Library • Login to StaffWeb console as System Admin to make changes to Library
- 6. Standard Policies • Remember Current User – NO • Report In-House Use During Checkin – NO • Prompt on Exit for Add Brief Title – YES (note – standard circulation logins will not have access to Add Brief Title) • Shadow Brief Titles – NO • Auto Assign User ID – NO • Display Current Checkouts in Checkout – YES • Display Web Auth ID in Maintain Users – NO • Hold Range – SYSTEM • Extended Info Display in User Status Header – NOTE; COMMENT; DEBT-COLL • Print User Information Default Field – USER NAME; USER ID; LIBRARY
- 7. Receipt Configuration • Each library needed their own receipt configuration • System Administrator applied settings
- 8. Limitations • Holds – can’t change the range on the fly • Item Search defaults to Library, with no option for Search Groups • User Search defaults to Library • Limit on the browse list of users when searching • User Maintenance – limit on Categories • Receipt fields cannot be re-ordered