TSWeb Technical Team Minutes, Sept. 21, 2005
Attending: Michal Jacyna, Sally Lockwood, Nathan Rupp (chair), Nancy Solla
Banner
1. Nate talked to Maureen Morris about what kind of banner the Library Gateway is considering, and she said that CUL Administration will soon be issuing its interpretation of the CU identity guidelines. This interpretation will mandate that the library gateway include a two line signature: Cornell University/Library. It is currently unclear whether sub-library unit pages (like LTS Web) will also fall under this mandate.
2. We will choose a banner color until we?re done with the web site so we can determine what color goes best with the rest of what we do.
Template
1. We will go with the "banner only" template?essentially design our own content and place a Cornell approved banner at the top of the site.
2. The one column template may work well for procedures pages.
Audiences (and how a front page could look to them)
1. Tech services audiences
a. Cornell LTS ? links to procedures, tools (dictionaries), projects (expanded Database Management list), contacts, training opportunities, structural/ committees (WGC, MWG), initiatives (ERM)
b. Technical services staff at other university libraries ? links to procedures, tools (ITSO, Harvest), projects (expanded Database Management list), contacts, training opportunities (we may develop our own training opportunities that could be useful to others), structural/committees (WGC, MWG), initiatives (ERM)
c. Technical services groups outside academia, including vendors (OCLC)
2. Non tech services audiences
a. Other CUL staff
b. Non-technical staff at other university libraries
c. Other CU staff
d. Staff at other universities
e. Non university/non technical services staff
3. Karen Calhoun ? wants a page that reflects the organization?s structure
We?ll finish going through the other audiences at our next meeting, but so far, it appears that the Cornell LTS staff and technical services staff at other universities may be interested in the same things.
Structural Issues
1. Functional vs. Hierarchical/Structural ? The structure of the current LTS Web site?s front page reflects the organization?s structure/hierarchy. Is this helpful, or should we structure the front page along functional lines? One important audience wants the site to reflect the organization?s structure. Is there a way to structure the page both ways? Can the organization?s structure be portrayed as a function?it could answer questions about the organization?s structure in much the same way the other categories answer other questions. If we were to stick with a functional design, the front page could include the following categories: procedures, tools, projects, contacts, training opportunities, initiatives, and structural/committees. This last category could be called "LTS Organization" and contain information about the organization?s structure and the committees. After all, the committees are part of the organization.
2. Periodic vs. frequent accessibility? Are there topics that staff access periodically and others that they access more frequently? What do we highlight on the front page? Can we highlight both? How?
Next Meeting
Friday, September 23, from 9-10:15 in Mann 361. We?ll continue our discussion of the various audiences who might use LTS Web.