1. River Campus Libraries GUF: Getting Users to Full-Text ( With Voyager®, ENCompass™, OpenURL, etc.) Jeff Suszczynski Senior Web Developer jeffs@library.rochester.edu

2. Library IT Environment Digital Initiatives Unit - Software Developers (3) - Systems Analyst - Computer Scientist - Anthropologist - Art Director / Designer - Digital Librarian for Public Services - Usability Team - Content Groups

3. Library IT Environment Usability Testing Lab

4. Metasearch - Major Issues Our users fail when they must:  Deal with Link Resolver menu choices  Follow long click-paths  Get stuck at dead-ends  Resubmit their searches mid-session

5. Major Issues - Examples

30. Major Issues - Resolved GUF (Getting Users to Full-text)  Title links on results screen lead to either:  Full-text (best)  Print holdings information with map (2 nd best)  Pre-filled interlibrary loan request form (worst)  Issues Addressed:  Deal with Link Resolver menus  Follow long click-paths  Get stuck at dead-ends  Resubmit search mid-session

31. Library Web Server GUF Library website user interface List of results Subscription Database Full text ILL login w/ request Map to journal Search GUF

42. Major Issues - Resolved In each case, the user only had to click once to get to full-text or the next best option.

43. Major Issues - Resolved To resolve user issues:  Link Resolver menu choices  Long click-paths  Dead-ends  Resubmitting searches GUF must do the following:  Improve metadata transfer  Eliminate/handle errors  Eliminate clicks  Check local holdings  Handle multiple editions

44. Improved Metadata Transfer Problem: Metasearch (ERA) ==> Link Resolver (SFX, LinkFinderPlus)  metadata hand-offs are extremely important… …and are generally inadequate  inability to handle different sets of metadata for different databases  inability to handle multiple items types from each database

45. Improved Metadata Transfer Example for Database X: if type (072 $a) = ‘Journal Article’ or ‘Periodical’ then: ISSN will be in the 022 $a or 773 $x or in a section of the 024 $a (parsable SICI) BUT if type (072 $a) = ‘Collected Volume Article’ (series) then: ISSN might be in the 490 $x Metasearch products generally don’t allow for this granularity.

46. Improved Metadata Transfer  GUF succeeds where Metasearch => Link Resolver often fails:  advanced metadata parsing  tailored for each database’s quirks

47. Improved Metadata Transfer How does GUF do this? results.xsl => objectGUF.xsl Title link on results.xsl sends metadata to objectGUF.xsl

48. Improved Metadata Transfer How? objectGUF.xsl => parserxxxdb.js  objectGUF.xsl grabs and massages metadata received  objectGUF.xsl sends cleaned and selected metadata to database-specific JavaScript file

49. fa2_articlefirst(" ", " ", " ", " ", " ", " ", " ", " ", " ", " ")

50. Improved Metadata Transfer How? parserxxxdb.js  JavaScript file, tailored for particular database, receives the metadata from objectGUF.xsl  It further massages the metadata using regular expressions

51. Improved Metadata Transfer The New Republic$bNew Repub$c233$d4$fJuly$gJuly$h07$i25$j2005$k6 var regvolume = /\$c/; if (regvolume.test(journalinfo)) { var volume = journalinfo.replace(/.*\$c/, ''); var volume = volume.replace(/\$.*/, ''); } else { var volume = ''; } var regissue = /\$d/; if (regissue.test(journalinfo)) { var issue = journalinfo.replace(/.*\$d/, ''); var issue = issue.replace(/\$.*/, ''); var issue = issue.replace(/[a-zA-Z]/g, ''); } else { var issue = ''; }

52. Improved Metadata Transfer How? parserxxxdb.js  JavaScript file forms robust OpenURL using regular expressions and advanced parsing  JavaScript file ships the OpenURL off to GUF All of this creates a better OpenURL than a typical Metasearch => Link Resolver hand-off, allowing for more and better links to full-text.

53. Articles – Eliminating Errors Problem: Full-text link on Link Resolver menu yields error page fairly often.

56. Articles – Eliminating Errors GUF eliminates these dead-ends by  pre-fetching pages  trying other sources on error

57. Articles – Eliminating Errors 1. GUF receives OpenURL from ERA server (JavaScript file) 2.GUF formats OpenURL into XML Example: http://chico.lib.rochester.edu:8080/SFX_API/sfx_local?XML= article 00084360 43 181 149 Canadian Literature A+glimpse+of+something 2004-08 Beauregard Guy getFullTxt

58. Articles – Eliminating Errors 3. GUF sends XML OpenURL via HTTP Post to SFX API 4.SFX API returns a list of full-text URLs Example…

59. Articles – Eliminating Errors Beauregard 2004 A glimpse of something 149 00084360 getFullTxt 181 Canadian Literature Guy http://gateway.proquest.com/openurl?ctx_ver=Z39.88- 2003&res_id=xri:pqd&rft_val_fmt=ori:fmt:kev:mtx:journal&genre=article&is sn=0008- 4360&date=2004&atitle=A+glimpse+of+something&req_dat=xri:pqil:pq_clntid=1 7941 available via ProQuest Research Library getFullTxt

60. Articles – Eliminating Errors 5. GUF executes HTTP calls (screen scraping) to the full-text URLs 6. If any error occurs, skip to the next full-text URL until all are exhausted

62. Articles – Eliminating Clicks Problem: Full-text links in Link Resolver menus often lead the user to a journal- or abstract-level page. This forces the user to scan the page and click one or more times to actually see the article.

65. Articles – Eliminating Clicks GUF:  drills down to article level for most databases  screen scrapes for embedded links to PDF or HTML fulltext

66. .*Table of Contents\ ", "")#>.*", "")#>.*", "")#> ", cfhttp.filecontent) EQ 0>

67. Articles – Check local holdings Problem: Link resolvers do not compare citation info against actual holdings info.

71. Articles – Check Local Holdings GUF is able to check your citation against local print holdings How?  Extract of entire print journal holdings from Voyager into homegrown SQL table  Print holdings are parsed using a set of regular expressions on our non-standard holdings info  Thus, the user only sees the ‘Library Holdings’ page when the library actually owns the volume/issue/date for a metasearch result.

72. Books – Multiple editions Problem:  Metasearch can yield book results for particular editions  Currently no way that link resolvers can determine whether local holdings include alternate editions  Dead end result for users

73. Books – Multiple Editions GUF uses OCLC’s xISBN service to find all editions and their ISBNs. Example: http://labs.oclc.org/xisbn/#url.isbn# Yields: 0441172717 0801950775 0399128964 044100590x 1556909330 0425027066 0425036987 0425046877 042507160x 042505313x 0441172660 0736692401 …

74. Books – Check local holdings  GUF searches catalog for complete list of ISBNs to find ‘good enough’ copy How?  ColdFusion custom tag that allows multiple, concurrent HTTP requests against Voyager OPAC  This allows for reasonable performance over large numbers of ISBN searches

75. Miscellaneous Features  ISSN lookup  Homemade DOI resolver  Date formatting  findarticles.com

76. Future Enhancements  Item records for print journals  Journal abbreviation lookup table  Google spellchecking  CrossRef DOI help  Flash-based maps

77. Other Ideas? Any ideas you may have are welcome…

78. River Campus Libraries GUF: Getting Users to Full-Text ( With Voyager®, ENCompass™, OpenURL, etc.) Jeff Suszczynski Senior Web Developer jeffs@library.rochester.edu