Provide the ability for librarians to change the content and headers of the modules manually.Allow the addition of Learning Objects (small movies that instruct students on research concepts or library tools ).Provide the ability to generate an RSS feed for the page.Provide the ability to view RSS feeds on the page.Provide the ability to choose which databases to search in the federated search.Provide the ability to choose which modules appear in the web page.Provide a web interface for content input.Enable librarians without technical knowledge to create pages.Generate course assignment pages with a consistent look and feel.Modules to provide greater interactivity.Link to chat service for live librarian help.Modules that help students find books, articles, the best web sites, style guides, course reserves, news feeds.A quick search box (federated search tool).Pages that have content recommended by instructors as well as librarians.Pages that are discoverable by course number.Library course pages that are easily found on the OSU Libraries home page.The project requirements fell into two large categories: When we reached this stage of the project, we realized we needed to hire a programmer, and before we did so, we wrote use case scenarios and distilled from those the baseline project requirements. We tested static HTML templates as an early prototype of the course assignment pages, but they did not allow librarians to easily publish or re-use content. OSUL has a long-term plan to move the library web pages into a content management system, but it was not in place when we started this project. Blackboard is not used universally across our institution, it is not as flexible and customizable as we envisioned our pages, and it was not apparent that the Blackboard team had the resources to work with us on developing a new service. Because we wanted to integrate library resources with particular courses, we carefully considered the campus course management system, Blackboard, but there were several challenges with a potential Blackboard integration. We were interested in the possibility of developing a tool that integrated with campus portal software, but it was not an option, as our institution evaluated and declined to purchase a campus portal system.
#Icap wiki software
Because we wanted to lower barriers to participation, we were wary of implementing library portal software that would require students to log on and create profiles. We investigated a variety of ways to deliver the course-centric, interactive web pages: library portal software, campus portal software, course management software, content management systems, and web page templates. The internal name we have been using for the project is “Interactive Course Assignment Pages,” or ICAPs. Rather than developing generic subject or college portals, we focused on library help pages that are tightly aligned with courses and assignments, include some interactive or Web 2.0 features, and are also simple for subject librarians to create and maintain. They prefer clear starting points for library research, need to save time, and are very interested in resources that have been recommended by their instructors. Undergraduates, especially lower division students, identify more with courses they are currently taking than with a specific college or subject. Initially, we considered building undergraduate portals based on colleges or subjects, but as we gathered data, read about undergraduate research activities and habits, and listened to students, we changed the direction of our subsequent project. We were particularly interested in lowering the barriers to library use for undergraduates searching for topical information. This project originated in a 2005 needs assessment conducted by Oregon State University Libraries (OSUL) to determine the best approach for connecting students with the wealth of information available to them through the library. By Margaret Mellinger and Kim Griggs ICAP Project Background