The ASIN Portal Project

1
The ASIN Portal Project

• APLA
• May 26, 2006Slavko ManojlovichMemorial
  University of Newfoundland
• and
• Stephen SloanUniversity of New Brunswick

2
Goals of the Project

• To provide enhanced services to our users new
  products for some, better products for others
• To better place information in context
• To leverage technical and bibliographic expertise
  in the region encourage collaboration among
  librarians and staff
• Share costs

3
The need for this project

• Library surveys and anecdotal evidence from
  librarians and staff strongly suggested many
  students were having trouble using our libraries
  effectively
• CAUL Directors created this project to try and
  better meet the needs of students

4
Multiple interfaces to databases
5
Multiple display formats
6
Dead ends
7
Institutional Partners

• Early implementers
• Acadia University
• Mount Allison University
• Memorial University of Newfoundland
• St. Francis Xavier University
• (St. Thomas University)
• University of New Brunswick (F SJ)
• University of Prince Edward Island
• New Implementers as of December, 2005
• Nova Scotia Agricultural College (December, 2005)
• Dalhousie University (January, 2006)
• Mount Saint Vincent University (March, 2006)
• Saint Marys University (March, 2006)
• Cape Breton University (May, 2006)

Remaining universities joining in 2006.
8
ASIN Portal Live at MSVU
9
ASIN Portal Live at MSVU
10
ASIN Portal Live at MSVU
11
The parts that were needed

• Authentication
• Proxying
• openURL Resolver
• Federated search engine
• ILL Software
• Bibliographic software manager
• Content Management System

12
What we have

• Local authentication scripts
• eZproxy
• Openly Informatics Resolver
• MuseGlobal SingleSearch
• Relais ILL
• RefWorks
• Sirsi Enterprise Portal Solution (Rooms)

13
The challenge

• To make all of these parts work together
• Each one has a place in meeting our goals.
• Lets examine each in turn

14
Authentication and proxying
15
Searching a new way

• Federated searching allows a user to search
  multiple, disparate resources simultaneously
• A resource discovery mechanism that may answer
  many information needs on its own

16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
What is a Resolver?????

• Our Featured Software Component of the
  Day!!!!!!!!!!!!!!!!!!!
• By special request, this means we will go into
  incredible, tedious detail on this component

27
What is a Resolver???

• A Resolver is an internet equivalent of a serials
  list in the (paper-based) library
• Present it with bibliographic data or a query
• It helps you locate the best information in the
  library
• Standards-based - many product options
• 1Cate, SFX, LinkFinderPlus, ArticleLinker,
  LinkSource, LinkSolver
• now widely deployed gt1,000 libraries
• Each of our Resolvers (one per institution) has a
  knowledge base of information about the librarys
  subscriptions

28
An internet library is built by librarians
usingelectronic resources from many vendors
ISI
PubMed
Journal Publishers
Full text DBs
EBSCO
OPAC
AI service
Google Scholar
29
Some services offer links to a few resources
ISI
PubMed
Journal Publishers
Full text DBs
EBSCO
OPAC
AI service
Google Scholar
User
30
Other services offer links to different resources
ISI
PubMed
Journal Publishers
Full text DBs
EBSCO
User
OPAC
AI service
Google Scholar
31
Linking is inconsistent and hard to manage
ISI
PubMed
Journal Publishers
EBSCO
Full text DBs
OPAC
AI service
Google Scholar
32
A resolver introduces consistent
andcomprehensive linking throughout the library
ISI
PubMed
Journal Publisher
resolver
Full text DBs
EBSCO
OPAC
AI service
Google Scholar
33
Checked the knowledge base and found UNB had
rights to the article.
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
Remember when I said A resolver introduces
consistent andcomprehensive linking throughout
the library
ISI
PubMed
Journal Publisher
resolver
Full text DBs
EBSCO
OPAC
AI service
Google Scholar
Well, our Resolvers dont just work from our
Federated Search.
40
They work from databases we already use
41
(No Transcript)
42
You can also link to a Resolver from an openURL
you may create

• http//unbf-resolver.asin-risa.ca8080/?genrearti
  clevolume17issue2spage219epage36
  issn0735-0198date1999aulastConnorsRobertJ.
  titleRhetoricReviewatitleTheRhetoricofCita
  tionSystemssidASIN

43
Or, you may link to an article, through the
Resolver, using a DOI

• http//unbf-resolver.asin-risa.ca8080/?doi10.111
  1/j.1365-2982.2006.00779.x

44
And Resolver does even more!
ltA-Z list
45
(No Transcript)
46
Subject listings
47
(No Transcript)
48
This ends our feature presentation on Resolver.

• We hope you have enjoyed this special portion of
  this session.
• We now return to our scheduled presentation.

49
Our Content Management System

• The critical last piece in the puzzle
• Still in development by SirsiDynix
• Today we are pleased to announce the delivery of
  Enterprise Portal Solution 2.2 (pre-release
  version) to our library community
• This allows each library to build its own
  hierarchy of subject Rooms but also allows the
  sharing of content across institutions.

50
(No Transcript)
51
What Have We Learned?

• The technology works.
• Collaboration works.
• Communication, trust, and a passion for success
  are critical.
• OpenURL is the driver.
• OpenURL allows you to provide your users with
  alternatives to pay-per-view for many new
  resources.
• Most problems are related to the lack of
  standards on the content side.
• Metasearch will not cure all of the problems
  associated with dysfunctional native user
  interfaces.
• The NISO Metasearch Initiative will only makes
  things better.
• This is a new experience for both users and
  librarians.

52
Portal launch

• Dr. Angelo Belcastro, Vice-President, Academic,
  University of New Brunswick
• Rooms website