TSWeb Combined Team Minutes, Aug. 30, 2005
Technical Services Web Group meeting, Aug. 30, 2005
Present: M. Jacyna, N. Solla, S. Lockwood, N. Rupp (chair), J. Spear, L. Purcell, M. Nichols, D. Warfield, J. Alberts (recorder).
1. Review of the previous meeting guided by Marty Kurth.
a. We noted the importance of full but respectful communication of views.
b. Turnaround times on email?The sender should specify turnaround time when necessary.
c. Group members should keep their CorporateTime up to date.
d. Responsibilities of the chairs.
i. CC Karen on final version of group minutes
ii. Send out meeting agendas in a timely manner
e. Decision making within the group (supplement to previous discussion)
i. Members should always support proposals with information and data
ii. If necessary, the chairs can call for a vote on time-sensitive decisions.
f. Group members should be sensitive to confidentiality issues with TS information when necessary.
2. Discussion of values/motivations/goals for new TSWeb site
a. Desire to create a dynamic web product that will raise the bar for other web development across Technical Services.
b. Valuing the process (crafting recommendations, making decisions, learning, building a new sense of community) as well as the product
c. Creating recommendations for best practices and implementing best practices across the new LTS documentation
d. Opportunity to redesign the look and feel of the current TSWeb.
e. Sally stressed the importance of keeping our users in mind, especially internal to TS and outside (primarily public services staff)
f. Nate noted the importance of serving numerous potential audiences (inside LTS, other Cornell constituencies, TS staff from other institutions, etc.); Nate also noted the University of Oregon Metadata and Digital Library Services site (http://libweb.uoregon.edu/catdept/home/index.html) as a potential example of quality TS web design.
g. Correct and up-to-date information; "realistic, understandable, and current"
h. Margaret noted the importance of creating a site that will be usable and approachable for staff in processing units new to LTS who have not had much previous experience using Olin TS documentation and procedures.
i. Nancy S. discussed the current importance of training within LTS and the potential for TSWeb to help coordinate training schedules and opportunities for LTS staff.
j. We need to create a new culture in LTS to emphasize distributed web maintenance and development, especially in regard to the procedures; Michal noted the importance of training in raising staff comfort levels with CommonSpot.
k. Several group members noted the importance of entrepreneurial services and using the web site as a marketing tool for LTS; ideas included ITSO, metadata services, CLAMSS, Harvester, TS "toolbox" features, and possibly columns/opinion pieces by TS staff.
3. Discussion of subgroup progress so far.
a. The Tech. Group has met with Melissa Kuo and Jim Riedy for preliminary discussions regarding web development in CommonSpot, and is working on a critical inventory of current CTS and TSWeb sites. The group mentioned the need for a new domain name for the site and tentatively proposed http://lts.library.cornell.edu.
Other ideas for a new domain name include:
? " www.technical.library.cornell.edu" (intuitive for TS & non-TS users)
? " www.technicalservices.library.cornell.edu" (intuitive for TS & non-TS users, but Karen might not approve of its length)
? " www.techservices.library.cornell.edu" (only intuitive for TS users, but not for non-TS users)
b. The Procedures Group has been reviewing procedural documents, working on a style guide to ensure adherence to best practices in procedure creation/revision, and creating frameworks and recommendations for metadata creation and a procedures taxonomy.