The Infodome Dispatch

Gosh, it’s been awhile. Welcome to Keven Jeffery, our new Digital Technologies Librarian. He’ll be on Webteam now, too.

The campus Content Management System project is rolling. We’ve selected Dreambox Creations as our vendor. Please post or email any sites that you like us to consider as we build out new CMS’d site.

CMS team members are (in no particular order):

• Lisa Lamont
• Brian Lenz
• Bruce Harley
• Barry Dworak
• Ellen Jarosz
• Michael Perkins
• Anne Turhollow
• Keven Jeffery
• Carolyn Baber

Based on our progress this year and the rapid changes in Website development, Webteam members feel that it would be better to have a stable core group of team members, rather than a constantly rotating membership.

This core group will be supplemented by ad hoc members who are pulled in for specific projects or to offer a perspective. The recommended core group is:

Carolyn Baber [Chair, Public services rep]
Ellie Dworak [Electronic Systems and Services Librarian]
Marilyn Hall [COIIL rep]
Mark Lester [Administration rep]
Nicole Shibata [Special Collection rep]
Brian Lenz [SCC rep]

Notice in the upper right side of the nav bar that there’s a new page about developing content for Infodome. I’ve tried to condense the instructions from the pagemaster’s guide into this quick reference. Next step: work with John P. to simplify those evil selectfiles pages. I’d like to get rid of them, but I’m not sure how yet.

This is part of a message I sent to Webteam this morning outlining a process for making, recommending, and stewarding change in the Library Web presence. I’m curious to see how it works out.

STEP ONE:
Please review our charge before the next meeting. I’ve posted it on the blog here.

STEP TWO:
We need to agree on the vision for our Website. To recap, my general concept is this, with perhaps sub-points below each item:

1. All the content users need in an easy to use and engaging format.

2. Content development so easy that technical skills are moot.

3. Professional look and feel, in keeping with our Library brand.

STEP THREE:
Review the strategic planning documents for ideas, projects, directions that are Web-y. List each in one of the above three categories. Add anything else we think is important.

I would like these items to be discreet. Instead of something amorphous like ‘massive website redesign,’ for instance, we can say ‘review major categories using card-sort tests and change as needed,’ ‘update content and layout of 2nd level navigation pages,’ and ‘improve layout and design for a more professional look.’

STEP FOUR:
Sort the items into these categories:

A. Just do it.
B. Discuss with appropriate people, then just do it.
C. Needs some planning, do that and then just do it.
D. Needs broad input, recommend a team be formed.
E. Should wait for IST Director.
F. Ideas, directions, etc. for future discussion.

STEP FIVE:
For items in categories A, B, and C list in temporal order and note who to confer with for each. For those items in categories C-F, create documentation of some sort that goes to whomever we decide it should go to.

STEP SIX:
Move forward. Rinse and repeat as necessary.

This charge was drafted back when I started working here. The Website has become so central to the mission of our organization, that it can be overwhelming. It’s good to go back to the basics and consider what we are charged to do:

The overall charge of this team is to make recommendations regarding the Library Website and issues that surround the Library’s portal to the world. This team is not necessarily comprised of everybody in the Library who is contributing Web content or is involved in html production, but is a steering committee that will gather input (both internal and external to the Library), make recommendations, research and implement solutions, serve as a clearinghouse for Web-based projects, and recommend policy. This team will further be engaged in an iterative process of evaluation and improvement.

The team will be comprised of five to seven members from various Library units, and will be chaired by the Electronic Systems and Services Librarian. Membership is open to all interested SDSU Library and Information Access faculty and staff. Volunteers will be solicited and selected by the Electronic Systems and Services Librarian and approved by the Dean of the Library and Information Access. Ex officio members may be selected by the Chair to serve as consultants.

This isn’t official yet, but I’m starting to list things that we’ll need to discuss/do:

• Minutes-keeping - taking turns
• Update on subject db pages (Carolyn Baber)
• Hours pages
• Mission/objectives/goals for the Website - it’s time to review and revise in light of strategic planning.
• Content inventory - what we have, what we need, what’s most important.
• Ongoing Cool Sites project

Chair:
Ellie Dworak

Appointed Members:
Carolyn Baber [January 2008]
Marilyn Hall [January 2008]
Mark Lester [January 2008]
Steve Savage [January 2007]
Nicole Shibata [January 2008]
Toni Whitley [January 2007]

Ex officio members:
Brian Lenz (Lfolks Webmaster)

1. Database pages-
   Carolyn Baber and Anne Turhollow will work on reviewing our current subject database pages and subject categories. Ellie will ask Sandy Neer to combine the alphabetical list of databases with the list of fulltext journals.
2. Changes to website-
   We will spend some time exploring a new mode for presenting databases and also most subject guide content. This will likely be driven by a db back end, so we need to design the output before building anything.
3. Marilyn Hall volunteered set up an ongoing ’sticky doc’ of problems, ideas, and websites we like. Team members will send their ideas to her.
4. It was noted that all of the secondary navigation pages need revision. We will start with the “research” page and continue with the others. A “community” navigation page was suggested.
5. The ‘hours’ page also needs revision to be more clear, since the Library building has somewhat complex hours. Team members should send ideas to Mark Lester, who will compile them and distribute before our next meeting.
6. Marilyn suggested exploring a clustered format for presenting information. She will point team members towards some resources for more information.
7. The various maps on our Website need to be reviewed for accuracy. Mark Lester noted that this may be addressed in another committee. It should still go on our list of things to address, and when we’re ready to do so, we can interface with that group.