|
Possible Functional & Usability Improvements
- Aim for clarity of design easy findability
- Incorporate both browsability AND searchability
- Main hp: less focus on ABOUT more on E-resources
- Incorporate "hierarchical Interface to LCC" when completed
- Consider including a weighting for importance for reference
sources
- Better, more consistent navigation
- More effective way to highlight NEWS important to inform users
about services and collections
- Confusion/conflict between "Reference" section of web and "digital
collections" hard for users to find e.g. E-journals not functional for
users
- E-journals presentation problematic
- Homepage and some lower level pages too wordy
- Terminology needs work jargon not good
- Develop a more interactive site that draws users in
- Need to decide what desktop configurations we're generally designing
for.
- Need to develop phased approach to redesign
|
LWEB Development Considerations
-
Functionality
(e.g., search/retrieval, navigation, interactivity,
end-user toolset; strategic platform for many/most library services)
-
Usability & Aesthetics
(e.g., ease of use for multiple audiences,
browsers, hardware platforms, bandwidth availability; consistency
of look, feel, navigation; graphically pleasing; accessible technology)
- Available Technology
(e.g., existing AcIS/CU tools; possible additional?;
interna development, commercially supplied; metadata; scalability;
SQL/HTML/XML migration)
-
Maintenance &
Adminstration
(e.g., support for distributed content provision;
coordination, review and selection of content; quality control &
link checking; evolution toward database-generated content; need
for easy updating of look & feel, graphics, etc.; phased/incremental
change; continued minimal central staff support; continued broad
staff participation in content creation;)
|
SWIFT