diglib: libweb guidelines & exceptions: meeting 8/28 3:00 pm

["Andrew R. Bonamici" <bonamici@uoregon.edu>]

All:

I talked with Mark this afternoon & confirmed that we *are* going to gather 
at 3:00 pm on Thursday, 8/28 to discuss these issues. This message is going 
to a lot of people, so please let Sheila know if you plan to attend -- a 
headcount will be needed before we can determine a location.

Thanks,

ARB

=======
BACKGROUND FYI:

Admin, Ron, Juanita, Ted, Kellie Ann, Normandy, JQ, Sara, Cara:

In recent library admin meetings and e-mail threads, we have spent some 
time discussing current Web guidelines, potential exceptions, main site & 
subsite maintenance, compliance with standards, development of a library 
logo, & general communication. Juanita wisely suggested merging these 
threads & an initial attempt is pasted below. Before sending out to the 
entire faculty & staff, presumably as a message from WAG, how about getting 
together as a manageably-sized group of key stakeholders to refine this 
summary statement as needed? We could use the fourth Thursday non-conflict 
time for this (8/28 at 3:00 pm) or set up another time.

In addition to the "guidelines and exceptions..." statement, this might 
also be a good opportunity to brainstorm ways of ensuring communication and 
coordination between the various individuals, units, departments, and 
groups responsible for the Libraries's overall web presence.  Examples of 
library-wide and cross-divisional groups include WAG, Diglib, & the 
Exhibits Committee. Current communication channels include
  - WAG list/archive (subscriptions are restricted to current WAG members; 
archive is public)
  - DigLib list/archive (any interested person can subscribe; archive is 
public)
  - TechTalk list/archive (any interested person can subscribe; archive is 
public)
  - Faculty & staff lists/archive (everyone is automatically subscribed; 
archive is public)
  - more?

Other thoughts in the meantime?

ARB

========

Draft statement re. UO Libraries web development: guidelines & exceptions

1. The goal is a reasonable degree of consistency. Refer to WAG guiding 
principles at <http://libweb.uoregon.edu/iris/wag/>.

2. As a default, libweb authors are expected to adhere to published 
guidelines for content and design, using standard libweb styles and 
templates. Refer to Web Guidelines at 
<http://libweb.uoregon.edu/Webtools/guidelines/>. Within the guidelines, 
additional templates or design patterns may need to be developed for some 
types of content, for example, pages developed specifically for use in 
classroom instruction.  Libweb authors who identify categories of content 
that may require new templates or design patterns will discuss their needs 
with the WAG, who will provide referrals to other sources of help as 
appropriate.

3. It is recognized that standard libweb templates and guidelines may not 
be appropriate for unique projects with complex, multifaceted content 
and/or partners and audiences extending beyond the Libraries. Examples 
might include but are not limited to digital library projects, online 
exhibits, courseware, consortial projects, grant-funded projects, etc., 
where strict adherence to the templates could present barriers to database 
functionality, appropriate recognition of partners, or ability to highlight 
unique content at the top level of the site. Web authors who believe that 
their project may require exemption from the guidelines will discuss 
options with the WAG, who will provide referrals to other sources of help 
as appropriate. These could include the IMG for design help, Catalog Dept 
for metadata consultation, Systems for database and hardware support.

Digital library project proposals require prior review and approval of the 
Digital Collections gatekeeper group (DigColl) and Library Administration; 
refer to <http://darkwing.uoregon.edu/~jqj/diglib/archive/doc00012.docOnline>.

Exhibit proposals require prior discussion and approval by the Exhibits 
Committee; refer to <http://libweb.uoregon.edu/exhibits/exhibit_policy.html>.

4. All Library web pages need to reflect current library and UO identity 
and branding elements. This includes pages otherwise exempt from standard 
guidelines, with the understanding that the presentation may vary, 
especially for projects with multiple partners or sponsors. As a minimum 
threshold, all library-based public web presentations -- including but not 
limited to libweb pages, digital library projects, exhibits, catalog/dbase 
search result screens, etc. -- will display
     a) the "O" (UO primary mark) and
     b) "University of Oregon Libraries" as linked text &/or in a graphic 
(as in current template banner).

When non-UO or non-Libraries logos/identifiers are mandated, they should be 
incorporated into the design in a straightforward manner. Strategies that 
require development of new banners or other major design efforts should be 
avoided if possible.  The UO mark & Library identification need to be 
maintained as stated above.

Note re. a UO Libraries logo (secondary mark): Although a library logo 
could be useful as a design element, we are not proceeding with a logo 
development process at this time (August 2003). First, logo development is 
typically associated with organization-wide identity, marketing & branding. 
These efforts are underway (or forthcoming) at the campus level, and we may 
be able to capitalize on that work. Also, the UO Libraries are in the midst 
of a broad-based effort to articulate our shared mission and values; this 
should also be used to inform any future logo/identity development process.


===============
Andrew R. Bonamici
Associate University Librarian, Instructional Services
115D Knight Library, University of Oregon
Eugene, Oregon 97403-1299 USA
bonamici@uoregon.edu
voice (541) 346-2682
fax   (541) 346-3485
http://libweb.uoregon.edu