Libraries

1
Libraries Institutional Content Management
Systems

• Pamela F. Cabe MLIS, AHIP
• Coy C. Carpenter Library
• Wake Forest University
• School of Medicine

2
About Us

• Institution comprised of
• Wake Forest University Baptist Medical Centerand
• Wake Forest University School of Medicine

3
About Us

• Carpenter Library serves both entities.
• The Department of Public Relations and Marketing,
  a department of the Medical Center, is
  responsible for the institutions web site and
  departmental web space.

4
What is CMS?

• Content Management System
• A content management system (CMS) supports the
  creation, management, distribution, publishing,
  and discovery of corporate information.
  (Robertson, 2003, KM Column).
• A way of standardizing web development at our
  institution.

5
Why CMS?

• Volume of the WWW
• Institutional Branding-sites would be clearly
  defined as being part of the institution.

6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
Why CMS?

• Sites began to contain errors, missing images,
  broken links, old information, incorrect health
  information, etc.

10
(No Transcript)
11
(No Transcript)
12
Why was the library concerned?

• Because were librarians!

13
Why was the library concerned?

• Bulk of library budget supports electronic
  resources.
• These resources are physically housed on the
  librarys web site.
• Look, feel, organization and usability of the
  librarys web site is key to properly showcase
  these electronic resources.

14
CMS Software and Template Design

• Microsoft Content Management Server
• A template was designed by an independent web
  consultant.

15
WFUBMC Template
16
Medical School Disagreement

• Medical School disagreed with template.
• The Medical School Web Task Force was formed.

17
School of Medicine Template Modifications
18
Issues Encountered with Conversion to CMS

• Site Conversion Process
• Web Editing
• Non-Compatible Technology
• Ineffective Site Search Engine
• Push of Live Content to Server

19
Site Conversion Process Issues

• LONG process
• Solutions
• Let independent firm do conversion and then
  correct any errors.
• Do the conversion myself.

20
Site Conversion Process Issues

• Pluses
• Learned CMS software.
• Streamlined our existing site.
• Redesigned the site look and organization.
• Minuses
• LONG arduous process
• Editing tools formerly used to manage site do not
  work with CMS software.

21
Web Editing Issues

• Microsoft Word OR
• Microsoft CMS WYSIWYG

22
Web Editing Issues

• Solution
• CMS WYSIWYG
• Pluses
• Changes are made inside the Browser, preview of
  pages is easy.
• Minuses
• WYSIWYG is clunky, difficult to use and produces
  almost indecipherable HTML.
• Technologies utilized in the former site dont
  function in the CMS.

23
Microsoft CMS Web Editing Software
24
Microsoft CMS Web Editing Software
25
Non-Compatible Technology

• Javascript
• DHTML
• Shockwave Files
• XML
• Forms

26
Forms
27
Forms
28
Forms and other Non-Compatible Technology

• Solutions
• Negotiated web space outside the CMS template.
• The Medical School is investigating a forms
  program to handle forms, Sharepoint.OrForms
  will remain outside CMS on different server.
• Removed Javascript and DHTML

29
Forms and other Non-Compatible Technology

• Pluses
• Site simplification
• Removed additional movement
• Minuses
• Removed ability to use advanced
  scripting/technology

30
Site Search Issues

• Patrons had ability to search library site.
• The CMS template included a site search box which
  instead of searching the librarys site would
  search the entire institutional site.

31
Site Search Issues

• Solutions
• We were able to create a faux template page which
  was outside the CMS to house our Google! Site
  search.
• Pluses
• Google site search works great.
• Minuses
• The ineffective search box is still on our site
  in the template.
• Patrons can only access the library search from
  our site.

32
Site Search Wireless Access
33
New Site Search Using Google!
34
New Site Search Using Google!
35
Push of Content to the Server

• Old site was transferred via FTP.
• New site changes are sent daily during a global
  update.

36
Push of Content to Server

• Solutions
• Database content (electronic journal information,
  electronic textbook listings) will be saved live
  on the server.
• Obtained permission to request a manual push when
  necessary.

37
Push of Content to Server

• Pluses
• Databases changes are instantaneous.
• Databases owners can edit and see results
  immediately.
• Minuses
• No live control over web content.

38
Final Result?
39
Carpenter Librarys New Site
40
Strategies for Negotiating with Institutional Web
Masters

• Get to know institutional web masters.
• Identify issues you may encounter
• Technology Issues
• Editing Issues
• Updating Issues
• Use your statistics.
• Instead of flashy technology, use flashy graphics
  to fill the void.

41
Serenity Now! Accept the things you cannot change!