|
Administrative
|
Technical Services |
After discussions of two different models for development, one exemplified
by the University of Indiana with one page per team, and the other exemplified
by the University of San Diego, California, with a single home page for all
teams' documentation, the TSWFTF and others in RS expressed a preference for
a single home page. We have developed several prototypes that reflect this basic
design:
G:\RS\TSWeb\TechServPrj\ts4.html
G:\RS\TSWeb\TechServPrj\ts7AB.htm
G:\RS\TSWeb\TechServPrj\ts8.html
You will note that the prototypes reflect a slight shift in scope to provide a page for internal technical services use only-see first structural feature recommendation below. At the current time Peggy has indicated that she sees no need for a web presence on this page, so Maintenance/Annex is not included.
Design features that we recommend:
· visually appealing but low use of graphics to speed loading
· use of a cascading style sheet and possibly templates for a cohesive
look and feel to the tech services pages (will be finalized once design is agreed
upon
· simple clear navigation bar at the top of the home page and appearing
on all pages
· search engine as part of header file to improve access to documentation
Structural features that we recommend:
· shifting links to documents used by public services colleagues to
the RS home page. This would include the list of team liaisons, the request
form for cataloging electronic resources, quarterly inventory reports, and the
Heckman binding schedule, among others. Such a realignment would make these
resources easier to find for our public services colleagues. (Alternatively,
we might provide a separate grouping of these documents on the Technical Services
documentation page at a point of high visibility). We would like some feedback
on this point.
· creation of a folder for each team to help sort out individual web
documents-- currently only OS has a folder; topical subfolders will also be
needed for large numbers of related documents (such as series authority documentation)
· all documentation no more than 3 clicks away
· all documents signed and dated to determine responsibility for procedures.
Authorization/conversion issues:
We recommend that team leaders and task force members have authorization to
add and edit the home page and their own team's documentation. Teams will have
the responsibility for selecting other individual team members to add/maintain
team documentation in a timely manner. All new documentation should be mounted
on the web; older documentation should be converted as each team finds convenient.
Submitted by:
Ann Ercelawn, Chair
Angel Bruner
Charlotte Lew