Integrating Library Technologies and Sakai
Session 055
Jon Dunn jwd@indiana.edu
, Indiana University
Susan Hollar shollar@umich.edu, University of Michigan
Thursday
8:30 am-9:45 am
Room: Rm402
Session Abstract
This session will provide background on existing and emerging library technologies to support improved access to licensed information sources, such as OpenURL link resolvers and metasearch tools. Participants will discuss technologies used at their home institutions and how these technologies might be used to help provide access to licensed digital content within Sakai.
Presentation Materials
- Session leaders are encouraged to post their presentation materials as Attachments to this Page. (See Attachments tab above.)
Session Notes
Introductions and interest in integration around the room
A lot of money is spent on electronic resources
Too many steps and places to search
Library now looking at federated search methods using MetaSearch
Open URL – create a single, database indepent URL for a library object (can point to specific place within content)
Most interfaces use a screen scraping-like technologies. More recently meta-search community looking at more scalable ways (SRW or SRU)which are more web-services based.
NISO – Meta search gateway protocal (MXG) based on SRU
Grant Proposal:
Focus on Twin Peaks Navigator – integration of licensed content into Sakai
Description of Twin Peaks – will be demoed at Tech session tonight
Plans:
- connect to metasearch (don't reinvent, use what already there)
- Integrate with Sakai Resources tool (makes sense to be able to manage all types of resources together)
- Subject research guides (prototype a tool for student access to subject-appropriate library resources)
Example, subject appropriate metasearch box for students. Access to
User centered design process
- Spring 2006 start work
- Fall 2006 Pilot testing
- Spring 2007 next iteration
Try to get basic proof that this CAN be done. Good start in right direction. Be available to Sakai community
Searching is an iterative, intuitive process. How well this works in a metasearch environment remains to be seen.
Questions and Answers:
Q: Looking at anything that would create a recommender or something like Amazon?
A: No. Some research in this area
Q: Build stable URL
A: Two ways to create persistant – from vendor, or open URL resolvers. Example Lexus Nexus.
Q: Any effort to make URL problem change at source rather than patch with resolvers?
A: Not much incentive for Vendors. Yale library uses RFP as opportunity to let Vendor's know that this is a criteria for choice.
Q: What is DOI?
A: Digital Object Identifier
Q: Integrating with Roles? Profiles frame searches and persistent collections.
A: Defined by course and context of course
Q: Should there be a librarian role in Sakai?
A: In prototype hope to try this out. Give instructor ability to have list of subject librarians that could add.
Q: Rough use case where instructor wants to do a search, find materials, move into course. Can take a list of citations, get URLs, get citations and add? More common use case...
A: Yes, more common. Not part of scope of proposal, but will want to look at this.
Q: How manage relationship between Sakai developers and Library?
A: Collaborated with Sakai developers on this. Bulk of programming effort on library side, but also Sakai developer support. Librarians need to do a better job stepping up to take part. Important.
Q: How does this tie into the existing Twin Peaks tool? Iteration?
A: Hopefully, yes.
Q: Expanding to include images? Open Archives Initiave for metadata (OAI) (Yale looking at this. Indiana doing)
A: Yes, on agenda of digital library folks. IU doing.
Additional Information
The grant from Mellon for the project discussed in this session was received. The project will run from 1/1/2006-6/30/2007. More information is available on the project site: http://www.dlib.indiana.edu/projects/sakai/