CUWL Wiki - Recently Updated Pages

CUWL Reorganization Assessment

VMalzacher — Wed, 04 Nov 2009 17:55:47 CST

Charge:
The “Report on CUWL Subgroups" which was approved by CUWL January 24, 2007 mandates that the new organizational structure be formally assessed to determine whether or not it should continue or if another structure should be put in place. In order to assess the effectiveness of this new model, CUWL is appointing a separate working group. The group will conduct its review the 08/09 fiscal year with a final report due to CUWL at its Spring, 2009 meeting. The group will have representation from the four Coordinating Committees through each of the Chairs who were involved since the initiation of this structure, a CUWL liaison, UWSA representative plus those involved in the original group who will make up this group. The group will recommend whether to continue or discontinue the existing structure and what changes might be needed.

Members:
Marlys Brunsting, UW-Green Bay (Chair, Library Technology Coordinating Committee)
Anita Evans, UW-LaCrosse
Steve Frye, UW-Madison (Chair, User Services Coordinating Committee)
Lisa Jewell, UW-System Administration
Valerie Malzacher, UW-River Falls, Chair
Joshua Ranger, UW-Oshkosh (Chair, Digital Initiatives Coordinating Committee)
Richard Reeb, UW-Madison (Chair, Collections and Resource Sharing Coordinating Committee)
Mary Rieder, UW-Colleges

Working Group on CUWL Subgroups Final Report, approved by CUWL on January 24, 2007

Report to CUWL on Survey Results, May 5, 2009

CUWL Subgroup Assessment Final Report, October 26, 2009

Resource Discovery

steve.frye — Wed, 28 Oct 2009 21:47:48 CDT

Note: comments, questions, and general feedback concerning any of the information provided below should be directed to the CUWL Resource Discovery Experimentation Working Group using the email alias: cuwldiscover-l@library.wisc.edu.

The links below are meant to help UW System library staff gain an understanding of the term 'resource discovery' and how proposed solutions to resource discovery might transform the way students and faculty search for and discover resources within our campus libraries. By 'resources' we are including content currently accessed via our OPAC, article databases, Minds@UW, etc. There are resource discovery solutions being considered that would replace and/or transform our OPAC and federated search tools. Some of these solutions already exist and are being implemented at a growing number of colleges and universities.

The CUWL Resource Discovery Exploratory Task Force spent the first half of 2009 creating a vision for resource discovery within the UW System. Our vision and recommendations are included in our report linked below. We would ask that you review the information below in the order presented. There are four items we would like you to read or view: (1) Chronicle article, (2) UW Forward Presentation, (3) Archived webinar on Summon, and (4) the CUWL RDETF final report. We also provide additional information that you might find beneficial.

There will be a CUWL User Service Coordinating Committee webinar on Thursday, November 19th from 12-1pm that will focus on the work of the Resource Discovery Exploratory Task Force. This session will primarily be a time for you to ask questions and engage in a discussion concerning resource discovery ideas and options. All those attending should read and view the four items listed below prior to attending this event. Information on how to attend this webinar will be distributed to the cuwluser email list. Information on joining the cuwluser email list can be found here: http://uwlib.uwsa.edu/committees/.

RESOURCE DISCOVERY

After Losing Users in Catalogs, Libraries FInd Better Search Software - September 28, 2009
Short article from the Chronicle of Higher Education.
UW Forward Presentation - July 21, 2009
50 minute presentation on the UW Forward project. UW Forward could become our central interface for accessing library material - including OPAC data, locally created digital content, institutional repository metadata, customized local services, and even article level metadata using an API (application program interface). For a visual description of how UW Forward might fit into the larger vision described in the CUWL RDETF final report, see the image below #4. In this image, UW Forward would encompass the silo labeled 'UW Builds and Manages Silo' and could provide the 'Resource Discovery Interface' as well. In other words, the UW Forward project includes both the gathering of our data/metadata into a single pre-indexed silo of content and the interface used to access that content. With the use of APIs, the UW Forward interface could also become the interface used to access article level and other licensed content. For example, using the Summon API (see presentation linked below), the UW Forward interface could become the search interface for both the locally managed data/metadata as well as licensed data/metadata managed externally.

Here's a JING video showing you exactly how to access this archived presentation if you're having difficulty.

See also: UW Forward Project Home; You can also search a live test instance of UW Forward. Examples of other libraries that use the Project Blacklight open source code include: Stanford University and University of Virginia.

See also: Sadler, E. (2009). Project Blacklight: a next generation library catalog at a first generation university. Library Hi Tech. 27 (1), 57 - 67. (Summary). Provides a technical overview of Project Blacklight, the underlying open source software behind UW Forward.

While Project Forward is built on the code provided by Project Blacklight, some colleges and universities have elected to build similar systems using several other competing open source products, including: VuFind and Extensible Catalog (XC).
Library Journal Webinar on Implementations of Summon - September 22, 2009
Use the email address: sfrye@library.wisc.edu to login and view this archived webinar.
63 minute webinar on the experiences of three universities who have implemented Serials Solution's Summon. We are focusing on Summon because it is the only product currently available that provides non-federated access to a massive silo of pre-harvested and pre-indexed article level content. By massive we mean 6,000+ publishers' content including 50,000+ journal and periodical titles which comprise 400+ million items. This content can be searched using the Summon interface or by using another interface by way of the Summon API. Similar products are being developed that may also provide access to a massive silo of pre-harvested and pre-indexed article level content. These products include: ExLibris Primo Central and Ebsco Discovery Service. Both of these emerging products have expected public release dates of 12/2009. OCLC is also partnering with Ebsco and others to expand the searchable content within their OCLC Local product.

It is important to note that in the RDETF vision, single silos of pre-harvested and pre-indexed licensed content would significantly reduce the need for federated searching. Instead of searching a limited number of pre-selected article databases and returning a limited number of results (up to 30 results per database) after 60 to 90 seconds, products like Summon search content equal to hundreds of article databases in seconds and return all results. These results are then ranked by relevancy or chronology and can be further organized using faceted browsing.

For a visual description of how a product like Summon might fit into the larger vision described in the CUWL RDETF final report, see the image below #4. In this image, Summon (and similar products) would encompass the silo labeled 'Vendor Builds and Manages Silo' and could provide the 'Resource Discovery Interface' as well. In other words, the Summon product includes both the gathering of licensed data/metadata into a single pre-indexed silo of content and provides an interface that could be used to access that content. Furthermore, Summon (and similar products) could ingest all of our locally managed data/metadata into their managed silo - providing our users with a central access point to most of the resources that we provide, including OPAC content, article level content, digital collections metadata, institutional repository metadata, etc.

Here's a JING video showing you exactly how to access this archived webinar if you're having difficulty.

See also: The following Summon implementations:
http://gvsu.summon.serialssolutions.com/
http://dartmouth.summon.serialssolutions.com/
http://wmich.summon.serialssolutions.com/

See also: Breeding, M. (2005). Plotting a new course for metasearch. Computers in Libraries, 25 (2), 27-29. Breeding's vision, as expressed in this article, is made real in the products and projects that are now coming online - including Summon. This article appears to be in full text via Ebsco's Academic Search Premier.
CUWL Resource Discovery Exploratory Task Force Final Report - August 14, 2009

Meebo Widget Test Page

steve.frye — Wed, 28 Oct 2009 19:00:07 CDT

Richland

mrieder — Mon, 26 Oct 2009 16:31:10 CDT

University of Wisconsin, Richland
Miller Memorial Library | On-Line Catalog

1200 U.S. Highway 14 West
Richland Center, Wisconsin 53581
Phone 608-647-6186 x220
Fax 608-647-6225

Title	Name	Phone	Email
Director	Todd Roll	608-647-6186 x220	todd.roll@uwc.edu
Associate Academic Librarian	Lisa Killips	608-647-6186 x293	lisa.killips@uwc.edu
LSA/LTE-Library/Textbooks	Patricia Brooks	608-647-6186 x281	patricia.brooks@uwc.edu

Voyager UB Reports

AllenWenzel — Fri, 16 Oct 2009 12:10:15 CDT

March 2009 UB Reports

April 2009 UB Reports

May 2009 UB Reports

June 2009 UB Reports

July 2009 UB Reports

August 2009 UB Reports

2009 October 15 - Pandemic Planning

mcclemen — Thu, 15 Oct 2009 13:27:31 CDT

CUWL Forum--Pandemic Planning
October 15, 2009, 12-1pm
Conference Call: Dial 1-517-417-5000 Participant access code: 125661
Facilitated by Myrna McCallister, Nancy McClements, Vanaja Menon

Agenda:
Welcome - Jill Markgraf, Chair of the User Services Coordinating Committee
Introductions
Overview of Madison, Whitewater & Parkside pandemic plans
Discussion questions (all)

Poster Copyright 2009 Board of Regents of the University of Wisconsin System

Discussion Questions:

Does your library have a pandemic plan?
What are the key features of your plan?
How have you notified staff of the plan?
What are you doing to educate patrons about your plan?
How will you keep your plan updated and useful for non-flu emergencies?
What extra precautions are you taking (i.e. cleaning keyboards) ?
What issues are still unresolved?

UW-Madison Resources:
NOTE: Library sites & documents are still in draft

UW-Parkside Resources:

Student Health & Counseling Center

UW-Whitewater Resources:

Influenza Information and Prevention

Collections & Resource Sharing

mrieder — Wed, 14 Oct 2009 12:40:37 CDT

Drafts and Other Documents (Password Needed) -- Access for CRS and CDC members to budgetary and Shared Electronic Collection information, and meeting documents.

2009-10 Meeting Dates

August 27, 2009 - Teleconference
September 25, 2009 - Joint Meeting with CDC, UW-Stevens Point
October 14, 2009 - Teleconference
November 11, 2009 - Teleconference
December 9, 2009 - Teleconference
January 13, 2010 - Teleconference
February 10, 2010 - Teleconference
March 10, 2010 - Teleconference
April 14, 2010 - Teleconference
May 12, 2010 - Teleconference
June 9, 2010 - Teleconference

2009-10 Meeting Minutes

August 27, 2009 - Teleconference

2009-10 Members

Name	Campus	E-Mail Address	Term Ends
Mary Rieder, Chair	UW Colleges	mary.rieder@uwc.edu	6/30/2010
Ewa Barczyk, CUWL Liaison	UW-Milwaukee	ewa@uwm.edu	6/30/2010
Janice Bogstad	UW-Eau Claire	bogstajm@uwec.edu	6/30/2012
Erin Czech	UW-Oshkosh	czeche@uwosh.edu	6/30/2012
Karen Jander	UW-Milwaukee	kj2@uwm.edu	6/30/2010
Lisa Jewell	UW System Administration	ljewell@uwsa.edu	Ex-officio
Lee Konrad	UW-Madison	lkonrad@library.wisc.edu	6/30/2010
Michelle McKnelly	UW-River Falls	michele.mcknelly@uwrf.edu	6/30/2012
Richard Reeb, Past Chair	UW-Madison	rreeb@library.wisc.edu	6/30/2010
Tom Reich	UW-Stevens Point	treich@uwsp.edu	6/30/2010
Joan Robb	UW-Green Bay	robbj@uwgb.edu	6/30/2012
Kathy Schneider	WiLS	schneid@wils.wisc.edu	Ex-officio
Judy Wurtzler, CDC Chair	UW-Platteville	wurtzler@uwplatt.edu	Ex-officio

This committee includes membership from the functional areas of collection development, access services, and user services. There shall be four ex-officio members, representing CUWL, UW System, the CDC Chair, and WiLS. Please see the CUWL Website for a complete description of the Collections & Resource Sharing Coordinating Committee and its goals.

To sign up for the CUWLCRS mailing list, please see the CUWL Coordinating Committees Website. This mailing list for UW System libraries staff is intended for the discussion of issues relating to print and electronic library collections and resource sharing including, but not limited to, cooperative collection development, the Shared Electronic Collection, Universal Borrowing, electronic document delivery and interlibrary loan.

Resource Discovery Experimentation Task Force

steve.frye — Fri, 02 Oct 2009 17:18:29 CDT

9/2009 to present

Charge
The task force should develop ways to communicate the vision, narrative, and recommendations of the Resource Discovery Exploratory Task Force final report with the larger UW System library community. The task force should assist in the development and beta implementation of UW Forward and assist individual campuses in piloting other products that align with the RDETF final report.

Key Expectations

Publicity & awareness: create materials & descriptions, coordinate demos, gather & analyze feedback
Cost/tradeoff analysis
Conduct deeper analysis of resource discovery tools (both vendor & open source)
Keep abreast of and report on related work at other universities
Draft a staged pushout / phased pilots for the Resource Discovery Tool(s) / Develop preliminary timeline that includes scope and functional requirements

Timeline
Progress report to the CUWL USCC by January 10, 2010 and a final report to the CUWL USCC by June 15, 2010.

Meetings
Task force meetings are scheduled on the 2nd and 4th Wednesday of each month from 12-1:30pm via teleconference.

Membership

Steve Frye - (Chair, UW-Madison), sfrye@library.wisc.edu
Sue Dentinger (UW-Madison), sdentinger@library.wisc.edu
Mitch Lundquist (UW-Madison), mlundquist@library.wisc.edu
Bill Doering (UW-La Crosse), doering.will@uwlax.edu
Lisa Jewel (UWSA), ljewell@uwsa.edu
Barb Bren (UW-Whitewater), brenb@uww.edu
Valerie Malzacher (CUWL Liaison, UW-River Falls), valerie.i.malzacher@uwrf.edu
Eric Jennings (UW-Eau Claire), jenninge@uwec.edu

Resource Discovery Exploratory Task Force

steve.frye — Fri, 02 Oct 2009 14:58:22 CDT

1/2009 to 8/2009

Charge
The task force should begin their work by reviewing the final report authored by the UW-Madison Resource Discovery Exploratory Task Force. see: http://uwlibdiscovery.blogspot.com/. The task force should develop a vision for information resource discovery in the UW System Libraries. The task force should also provide an updated environmental scan of current options, including the opportunities and challenges of each. The task force should investigate and report on related initiatives of other libraries and library systems, in the state, region and nationally. Finally, the task force should recommend resource discovery solutions that are desirable and appropriate for UW System libraries.

Key Expectations
Building on the UW-Madison report, develop a vision for resource discovery in the UW-System Libraries, which includes:

Scope of the tool(s)/service(s) and their relationship to each other
Features and characteristics of the resource discovery tool(s)/service(s)
Priority of features and characteristics
Relationship of UW-System resource discovery tool(s)/service(s) to others resource discovery tool(s)/service(s), especially those in the UW System.

Environmental scan of current options or directions, including opportunities and challenges associated with each.
Recommend a resource discovery solution that is desirable and appropriate for UW System libraries.

Timeline
Progress report to the CUWL USCC by March 15, 2009 and a final report to the CUWL USCC by June 15, 2009.

Membership

Steve Frye (UW-Madison), sfrye@library.wisc.edu
Sue Dentinger (UW-Madison), sdentinger@library.wisc.edu
Mitch Lundquist (UW-Madison), mlundquist@library.wisc.edu
Bill Doering (UW-La Crosse), doering.will@uwlax.edu
Lisa Jewel (UWSA), ljewell@uwsa.edu
Barb Bren (UW-Whitewater), brenb@uww.edu
Valerie Malzacher (CUWL Liaison, UW-River Falls), valerie.i.malzacher@uwrf.edu
Eric Jennings (UW-Eau Claire), jenninge@uwec.edu

---
Role of Members
Members set the agenda, goals and action plans required to accomplish the charge of the Work Group.

Responsibilities of Members

Accept and support the Resource Discovery Task Force charge
Review all relevant materials prior to meetings
Attend meetings (primarily via conference call)
Work toward fulfilling Task Force objectives
Carry out individual assignments in a timely fashion

---
Role of Chair/Co-chairs
The chair/co-chairs are responsible for the general leadership of the Resource Discovery Task Force and provide direction to members working in support of the charge.

Responsibilities of Chairs/Co-chairs

Accept and support the Resource Discovery Task Force charge
Plan meetings and agenda in collaboration with the other co-chair and other appropriate group members
Attend meetings and stay abreast of work between meetings
Maintain records of the Task Force
Facilitate active participation and decision-making
Assume responsibility for the completion of the Task Force charge
Report back to USCC on progress of Task Force.

RDETF Minutes

steve.frye — Fri, 02 Oct 2009 14:34:34 CDT

There is no abstract available for this page revision.

2009-9-30 Minutes

steve.frye — Fri, 02 Oct 2009 14:32:48 CDT

Present: ML, SD, SF, VM, EJ, BB,

Summon presentation was very positive. Mitch suggested that Summons is moving quickly and we might want to think about asking for money now and piloting summons in the spring. Maybe we stay a two silo shop with Forward on one side and Summons on the other. We need to follow-up with summons to better understand what it is we're purchasing and how. Does everyone get the same article/licensed data. Perhaps Wisconsin can beta system wide pricin? We decided to arrange a conference call with Summons to ask questions in the near future.

We discussed the idea that if we take the RDETF final report seriously, then there are products and possibilities that align with the report... and products and possibilities that do not align with our report. In other words, the report points us in a direction... taking some possibilities and products off the table.

What does our report... direct us to do and not to do. (a) Continue to develop Forward, and (b) Move away from federated searching and towards searching a single silo of harvested, pre-indexed A&I content.

We've been asked to:

Develop tool for needs assessment for resource discovery on each campus; perform analysis of needs assessment results. Sue felt that we have done some or most of this already in the form of focus groups and surveys that both Madison and other campuses have carried out.
Publicity & awareness: create materials & descriptions, coordinate demos, gather & analyze feedback - We'll want to open it up more broadly to the library community... including things such as vendor demos, etc. Ebsco, WorldCat, ExLibris, etc. - Archives presentations/webinars and articles.. Explain to folks what resource discovery is... how they relate to each other... etc. People have to be brought along. Put a package together and then recommend that their staff view and read and then hold a staff meeting that focusses on this material. Start at the chonicle article. Viewing the forward demo. LJ Summon webinar. Then the report.

We will be meeting (are scheduled to meet) twice a month... 2nd and 4th Wednesdays from 12-1:30pm.

Based on our discussion today, we see our group focusing on two actions:

One of our primary concerns is to communicate the vision, narrative, and recommendations of our report with the larger UW System library community.
The other major focus is the continued development and beta implementation of UW Forward in addition to piloting other products that align with the conclusions of our report. One major product that we would like to see piloted (purchased and implemented) on several campuses within the UW system is Summon. In fact, the Madison members of the CUWL task force, would love to see Madison purchase and implement Summon now (i.e. ready for public view by January 2010).

Minutes - RDETF

steve.frye — Fri, 02 Oct 2009 14:12:50 CDT

See menu on left.

Focus Groups - Faculty / Graduate Students

steve.frye — Fri, 02 Oct 2009 14:11:45 CDT

... from UW-Madison (Nola Walker)

The focus group or guided interviews should be recorded, including the overview of the session, guidelines and discussions. Ensure you have a note taker and facilitator to guide, redirect and ask clarifying questions as needed. Do not use the session to defend or criticize library services or processes, but rather focus upon obtaining the participant’s insight. Your primary role is to listen, seek understanding of alternate perspectives, and capture the participants ‘voice’.

Incentives: Be sure to check with campus administrative rules prior to offering and selecting monetary or gift’ incentives. Offering a light meal (vegetarian alternatives) is an acceptable and inexpensive incentive. (i.e. sub sandwiches, fruit, and drink).

Note to other UW-System Libraries: The UW System cannot reimburse the use of gift cards as incentives. The system can reimburse the purchase of pizza and soft drinks. Contact Lisa Jewel (608-890-2208 / ljewell@uwsa.edu) for limits and reimbursement instructions.

Faculty
Faculty / Instructional staff / researchers can be a bit of a challenge. They should be separate from graduate and professional student sessions. It can be difficult getting enough to commit for a true focus group, but often faculty are quite eager to share input one-on-one. Using a guided interview approach can be a most efficient means of gathering staff input. It is essential that you provide a clear scope of questions to ask (e.g. 3 core issues), allowing time for rich discussion. The facilitator or ‘interviewer’ will need to possess the skills to tactfully redirect participants as they meander in discussion towards ‘solving all the library’s problems’.

Graduate Students
Graduate students generally are such a rich resource for input. Since their schedules vary widely, flexibility is critical. Ensure to offer morning, afternoon and evening options for focus group sessions. Offering a light meal has been a very good and appreciated incentive for participants.

Recruitment: Recruit for participants well ahead of time, and prepare for cancellations. Creatively market your efforts to your intended audience through existing campus forums and spaces where they ‘live’. Such spaces include, unions/commons, department lounges, designated study areas, and vary your approach (i.e. online, in person) using targeted outreach methods. Use existing campus services that support and outreach to graduate audiences using such means as forums, listservs, mailings, and postings.

Upon reflection, student participants are very engaged in discussions and offer very insightful and creative input. Usually they are grateful for the opportunity to share their views and offer many quotable moments.

Follow-up: Be certain to follow-up with participants by thanking them for their participation and noting how their input will be used in your investigative process. Encourage participants to share their experiences with peers, this supports expanding participation in future efforts.

Questions? Please feel free to contact Nola Walker, UW-Madison Assessment Librarian at nwalker@library.wisc.edu or (608) 890-0768.

Focus Groups - Undergraduates

steve.frye — Fri, 02 Oct 2009 14:11:19 CDT

...from UW-Madison (Kelli Keclik)

RDETF Undergraduate Focus Groups

We recruited participants for our focus groups through our online user survey. We contacted students who indicated their interest and offered to give them pizza in exchange for their time. We didn’t hear back from a single undergraduate student after this initial message. We then rethought the use of pizza as an incentive and offered a $25 iTunes gift card instead. Following the second email, we heard back from 7-8 students. I wrote them back with three possible dates/times for focus groups. We ended up scheduling two focus groups with six students in total. All of the focus groups were held during the evening at College Library and lasted approximately one hour.

Note to other UW-System Libraries: The UW System cannot reimburse the use of gift cards as incentives. The system can reimburse the purchase of pizza and soft drinks. Contact Lisa Jewel (608-890-2208 / ljewell@uwsa.edu) for limits and reimbursement instructions.

The following questions were asked in all focus groups:

Try to imagine, if you could create or have your ideal research environment (on campus), equipped with any resources, facilities, technology, or human resource necessary to do your research, what characteristics would it have?
Describe the best web-based service you‘ve ever experienced. What made it excellent? What distinguished it from the crowd?
Where have you found difficulties/frustrations in the research process?
The majority of online survey respondents indicated that identifying relevant materials within search results is the most challenging part of doing research. If this is true for you, can you say in more detail what part of identifying materials causes you trouble and how you think we could make this easier for you?
Think of a wonderful, off-beat resource that you found that sparked a new idea, or perfectly matched your research topic. What was the path you took to get to the resource? (i.e. did they go from MadCat to Amazon to Google Scholar or MetaLib to citations to MadCat…)

These items were reserved for undergraduate focus groups:

Do you personalize and customize any sites on the Web, like Yahoo or Facebook?
Besides making phone calls, how else do you use your cell phone?
Demoed VuFind and asked them to react to look/feel and functionality. Todd Bruns posed the prepared questions and I took notes. We both asked follow-up questions and asked students to clarify responses or provide more detail at times. We used Nola’s “Focus Group Format” document as a general guide. The sessions with the undergraduate students were pretty informal and the students seemed comfortable talking with us and each other.

Focus Groups - Format Explained

steve.frye — Fri, 02 Oct 2009 14:10:44 CDT

Framework: In general, one to two hours, this includes set-up and clean-up. Room equipped with Internet/PC access and large screen, comfortable seating and refreshment of some type. Five + questions (open ended) or key issues will serve as the guide throughout the meeting. One facilitator, 1 supportive assistant to take notes and or clarify questions or issues.

Materials: sign-in log, recorder, pencils, markers, pens, sign-in sheet, easel paper/pad, tape for posting paper (if necessary). Order food, or incentives and gift certificates in advance.

Note to other UW-System Libraries: The UW System cannot reimburse the use of gift cards as incentives. The system can reimburse the purchase of pizza and soft drinks. Contact Lisa Jewel (608-890-2208 / ljewell@uwsa.edu) for limits and reimbursement instructions.

Role of facilitators:

Introduce staff and thank participants for volunteering, and provide an overview of the process.
Ask the questions, one at a time. Allow approximately 10-15 minutes discussion per question. The facilitator should remain neutral in expression and limit interruptions, ensuring to encourage elaboration or clarification by participants. Make sure all have an opportunity to speak and manage domineering speakers. It may be necessary to qualify the question(s) and context.
The facilitator, and assistant, should record answers using the electronic recorders, as well as take notes during the discussion, using the easel paper, or notepad, for post session transcription.
Distribute refreshment and/or incentives to participants.
Thank them again for participating.

Understand your objective (Sample): Through a facilitated dialogue, we seek to learn about user’s research experiences and views of library services, resources and desires. We also seek feedback to inform the development of library... services by identifying current issues, needs and trends of our users.

Resource Discovery Vision

steve.frye — Fri, 02 Oct 2009 14:10:19 CDT

Our library provided resource discovery product(s) will link to full text documents and snippet views (e.g. Google Books).
Our library provided resource discovery product(s) will allow natural language searching.
Our library provided resource discovery product(s) will be simple and intuitive in design and search functionality.
Our library provided resource discovery product(s) will allow patrons to find an array of resources and formats, including analog and digital items that we own or license through a single or reduced number of integrated search interface(s).
Our library provided resource discovery product(s) will allow patrons to quickly drill down within the results of a search.
Our library provided resource discovery product(s) will include 'did you mean' functionality.
Our library provided resource discovery product(s) will offer recommend resources based on a patrons search.
Our library provided resource discovery product(s) will distinguish between peer-reviewed and non-peer reviewed sources.
Our library provided resource discovery product(s) will distinguish between sources immediately available online and those that might take some time to access.
Our library provided resource discovery product(s) will distinguish between analog sources available immediately within campus libraries and those that would require time to access.
Our library provided resource discovery product(s)access to online help integrated into interface.
Our library provided resource discovery product(s) will allow results to be listed in relevancy ranked order.
Our library provided resource discovery product(s) will allow us to have control over the search interface and our data.
Our library provided resource discovery product(s) will integrate with citation management tools.
Our library provided resource discovery product(s) will work well with each other.
Our library provided resource discovery product(s) will allow for intuitive and efficient administration of resources.
Our library provided resource discovery product(s) will host or provide access to multiple types (formats) of data.

Resource Discovery links

steve.frye — Fri, 02 Oct 2009 14:09:41 CDT

Eric Lease Morgon's Blog re open source library software: (note comments on non-MARC content, federated searching)

http://infomotions.com/blog/tag/open-source-software/

Some Palinet links

Serials Solutions Summons: (note reference to APIs allowing various discovery platforms access to hosted content)
http://blog.palinet.org/dt/?tag=ala

Separating the Discovery Layer from the ILS
http://blog.palinet.org/dt/?p=32

Library Hi Tech (March 2009), v.27,n.1 Many interesting articles.

USMAI (University System of Maryland and Affilitated Institutions) Resources of General Interest, specifically the following sections:

Study group on the future of the USMAI web presence report Study group on the future of the USMAI web presence criteria for evaluation of discovery tools http://usmai.umd.edu/

Various Resource Discovery Systems

steve.frye — Fri, 02 Oct 2009 14:09:01 CDT

A List of Various Resource Discovery Systems and where they're being used

Open Source

Blacklight

University of Virginia Library
http://blacklight.betech.virginia.edu/

VuFind

Villanova University
http://library.villanova.edu/Find

National Library of Australia
http://catalogue.nla.gov.au/

Minnesota State Libraries
http://plus.mnpals.net/

Georgia Tech
http://finder.library.gatech.edu/

University of Michigan (beta)
http://mirlyn2-beta.lib.umich.edu/

Extensible

http://www.extensiblecatalog.org/

Commercial

WorldCat Local

Ohio State
http://library.osu.edu (select Search OSU and Beyond)

University of Washington
http://www.lib.washington.edu/ (select "UW Worldcat:..."

Endeca

North Carolina State
http://www.lib.ncsu.edu/

Primo

University of Iowa
http://smartsearch.uiowa.edu

University of Minnesota
http://www.lib.umn.edu/ (select MNCAT Plus)

Aquabrowser

University of Chicago Library
http://lens.lib.uchicago.edu/

Oklahoma State
http://boss.library.okstate.edu/default.ashx

Summon (Serials Solutions)

Dartmouth College
http://www.dartmouth.edu/~library/home/find/summon/

University of Liverpool
http://www.liv.ac.uk/library/summon.html

http://www.serialssolutions.com/summon/

Resource Discovery Product Matrix

steve.frye — Fri, 02 Oct 2009 14:08:31 CDT

General functional matrix of various Resource Discovery Systems The following matrix represents the functions of some of the more common resource discovery systems in use at academic libraries. Content is borrowed heavily from the UW-Madison Resource Discovery Task Force report: http://staff.library.wisc.edu/rdetf/RDETF-final-report.pdf and the following "future library" document: http://futurelib.pbwiki.com/Next+Gen+Catalog+Requirements The specific functions are defined below. Additional detailed matrices specific to each product are included also.

Metasearch - Search potential includes all resources available to the user (licensed, dig collections)
Relevance ranked output
Facets - general discipline, level (basic, academic), audience, genre, date of creation, topical time frame
Spell checking, stemming, etc.
Full Unicode character sets for search and display
Search inside book (where full text is available)
Display includes images - Covers, title pages, TOC
Brief display is topical - Reveals what resource is about
Personalization – personal/shared bibliographies, booklists with tagging, user profiles, defaults
Selective sort by variety of keys
Notification Services – email, rss of due dates, holds, etc.

	VuFind	Blacklight	WorldCat Local	Primo	Extensible
Metasearch	Yes	Yes	Yes	Yes	Yes (separate tabs)
Relevance ranked output	Yes	Yes	Yes	Yes	No
Facets	Yes	Yes	Yes	Yes	Yes
Spell-checking, stemming	Yes	Yes	Yes	Yes	No
Unicode search/display	Yes	Yes	Yes	Yes	No
Search inside book	No?	Yes	?	Yes	Yes
Display includes images	Yes	Yes	Yes	Yes	Yes
Brief display is topical	Yes	Yes	Yes	No	No
Personalization	Yes	No	Yes	?	No
Selective sort by keys	Yes	No	Yes	Yes	No
Notification services	Yes	No	No	Yes	No

Superior

EllaC — Tue, 22 Sep 2009 08:57:52 CDT

University of Wisconsin-Superior

Jim Dan Hill Library | On-Line Catalog

Belknap & Catlin, P.O. Box 2000
Superior, Wisconsin 54880
Phone 715-394-8343
Fax 715-394-8462

Title	Name	Phone	Email
Interim Library Director	Deb Nordgren	715-394-8233	dnordgre@uwsuper.edu
Reference/Government Documents	Ella Cross	715-394-8512	ecross@uwsuper.edu
Program Assistant, Library/Library Science	Julie Bracket	715-394-8347	jbracket@uwsuper.edu
Technical Services/Cataloging	Janet Baltes	715-394-8136	jbaltes@uwsuper.edu
Technical Services/Collection Development	Debra Nordgren	715-394-8233	dnordgre@uwsuper.edu
Acquisitions/Periodicals	Beverly Sturgis	715-394-8437	bsturgis@uwsuper.edu
Information Literacy Librarian/Archivist	Laura Jacobs	715-394-8359	ljacobs@uwsuper.edu
Information Services Librarian	vacant
Technical Services/Reserves	Jody Johnson	715-394-8194	jjohnso2@uwsuper.edu
Interlibrary Loan	Lori Hughes	715-394-8130	lhughes@uwsuper.edu
Reference Librarian	Paul Hlina	715-394-8342	phlina@uwsuper.edu
Government Documents Librarian/Reference	Ella Cross	715-394-8392	klindqui@uwsuper.edu
Public Services/Interlibrary Loan	Lori Hughes	715-394-8130	lhughes@uwsuper.edu