1 / 35

Penn State University Libraries

Penn State University Libraries. Initial Content Management Investigation, Spring 2003. Who We Are. University Libraries Department for Information Technologies (I-Tech) http://www.libraries.psu.edu/itech/

yaakov
Télécharger la présentation

Penn State University Libraries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Penn State University Libraries Initial Content Management Investigation, Spring 2003

  2. Who We Are • University Libraries Department for Information Technologies (I-Tech) http://www.libraries.psu.edu/itech/ • Dept. of about 10 people working with staff technology training, technical support, and R&D • Partner with ITS/Digital Library Technologies on many initiatives

  3. Libraries- LIAS Home Page

  4. Our Environment • Thousands of Libraries-produced Web pages – and counting • “Organic” development where each unit has strong feelings about both its content and the presentation (look and feel) • Growing recognition that a functional Web site needs to have usability, coherence, good navigability, search features, etc.

  5. What we’re Not doing in this investigation • Choosing a content management system for the Libraries Web site • Expecting our demo product to be “the answer”

  6. What we Are doing in this investigation • Gaining some basic expertise in CMS among staff in I-Tech • Developing a means for demo’ing the content management philosophy of Web development to our colleagues

  7. What we had to work with • Strong desire to investigate the content management concept • No $$ • Busy developers, minimal time to spend • Development server available for R&D • Our own department Web site as a test bed

  8. Planning for a speedy development process • Found interest group in the department • Surveyed available resources • Developed checklist of features (deal breakers, desirable, optional) • Developed list of open source products • Developed ambitious timeline

  9. Critical requirements for our test CMS software product • Open source (or very low cost licensing) • Work with current infrastructure App server – Cold Fusion or PHP Web server – Apache or IIS Database – MySQL, Access, SQL server • Work in Windows 2000/XP environment

  10. “Nice to have” • User support community for open source • Compliance with accessibility guidelines • Admin & user customization • Levels of permission granularity • Easy updating • Support for other devices (pda’s etc.) • Multi-language capability • Etc.

  11. Process and Timeline

  12. Completed checklist example

  13. Content Management with phpWebSite Requires MySQL, Apache, and PHP. Meets the W3C's Web Accessibility Initiative requirements

  14. Core Features [as printed on the website] • phpWebSite allows an individual or group to easily maintain an interactive, community-driven web site. In fact, you're using it right now. A brief summary of features is outlined below: • Easy, web-based administration - minimal computer experience is needed to maintain site content. • Flexible layout control - site page layout can be changed at anytime. • Catagory-based content - organize site information by category with automatic related information. • Interactive content - visitors can post comments, submit announcements and web links. • Customized user experience - themes allow each vistor to customize the web site for his or her preferences or special needs. • XHTML and WAI compliance - we are committed to meeting XHTML 1.0 specifications by our 1.0 release. Current errors are minimal if any. • Expendable content - through announcements, blocks, pages, dynamic forms generation, calendar, comments, photoalbums, FAQ, and polls.

  15. User and Administrator Settings

  16. User and Administrator Settings • Personal Settings (Users) • Layout (theme selection) • Language (set user’s default language) • Announcements (create an announcement) • Notes (create and send notes) • Comments (set method and display of comments)

  17. User and Administrator Settings Authorized groups and administrators • Content, security, and core modules are for authorized groups and administrators. Changes made to these functions set the default theme, layout, and active modules for all users.

  18. I-Tech Modules • I-Tech has activated these modules so far: • User Login • Announcements • Articles (I-Tech staff, training, welcome) • FAQs (technical, training, informational) • User survey (poll) • Calendar of events

  19. Submitting News Authorized groups and administra-tors can submit news and set an expiration date to send the announcement to a searchable archive.

  20. I-Tech Article Announcements and articles also allow the insertion of images.

  21. FAQs Set FAQ categories. Displayed next to each category is the number of questions and answers for that category.

  22. FAQs Click the category, select the question and view the answer.

  23. FAQs Each FAQ includes an option for the reader to score the helpfulness of the FAQ. A search box is available to search the FAQ database.

  24. Calendar The site also includes a Calendar of Events. The highlighted dates cue the reader that there are events scheduled.

  25. Calendar Clicking highlighted event takes the reader to details of the event

  26. Calendar To submit an event, an authorized user clicks the submit event button and fills in the detailed boxes of the event screen.

  27. “Live” page from Appalachian State

  28. “Live” page from Appalachian State

  29. “Live” page from Appalachian State

  30. Still to do • Finish installing modules • Figure out how it all works • Expand our available dept. content • Start to demo the concept

  31. What we’ve learned so far • Advance planning is probably the most important step in successful large-scale change • People like the idea of templates; wide diversity of opinion about what that means in practice • Creating buy-in will be a gradual process

  32. Future? For us, any content management decision will be complex - many players - what systems (open source or commercial) would scale to our needs? - time and $$ - availability in library world of some customized commercial products with some of the features of a CMS

  33. Contact info: Linda Friend lxf5@psulias.psu.eduor Brian Hoffman (Database Admin/Webmaster) bjh1@psulias.psu.edu Penn State University Libraries Dept. for Information Technologies 102 Paterno Library, University Park, PA 814/865-3612

More Related