1 / 33

WebBridge: Beyond the Basics

WebBridge: Beyond the Basics. Terry Reese Cataloger for Networked Resources Digital Production Unit Head Oregon State University terry.reese@oregonstate.edu. Mapping It Out. Extending WebBridge into the Catalog How’s it different? Why would you do it? Maintenance concerns

umay
Download Presentation

WebBridge: Beyond the Basics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WebBridge: Beyond the Basics Terry Reese Cataloger for Networked Resources Digital Production Unit Head Oregon State University terry.reese@oregonstate.edu

  2. Mapping It Out • Extending WebBridge into the Catalog • How’s it different? • Why would you do it? • Maintenance concerns • Extending WebBridge’s Functionality • Extending DOI/CrossRef Support • What is CrossRef? • How does this work? • What does III support? • Working with OpenURL 1.0 or non-SID passing resources • ILL Friendly OpenURL Linking

  3. WebBridge – Bridging the Catalog and Electronic Resources In addition to aggregator linking, WebBridge allows III libraries to: • Create dynamic relationships between a user’s queries and the WebBridge coverage data. • Create dynamic relationships between bibliographic data and the WebBridge coverage data. • i.e., associate a set of resources with a particular subject, call number, author or collection.

  4. WebBridge – Bridging the Catalog and Electronic Resources The ability to create dynamic relationships within one’s catalog to the WebBridge holdings data IS the primary functionality difference between WebBridge and other vendor or home grown products.

  5. WebBridge – Bridging the Catalog and Electronic Resources • How is linking out of the Catalog different from linking in from aggregators? • Primarily it’s the dynamic relationships that WebBridge allows libraries to build with their content. • Allows the ability to limit resources by resource location, scope or, if you’re using the Millennium modules, by staff view.

  6. WebBridge – Bridging the Catalog and Electronic Resources • How is this helpful? • The traditional SFX link simply provides OpenURL resolution against the coverage data. This tells the user: • If the institution has the resource electronically • And where they can get it. • Dynamic Linking allows librarians to create rules based on bibliographic conditions to group electronic resources, web links, etc.

  7. WebBridge – Bridging the Catalog and Electronic Resources • How do you set it up? • Setup requires: • Institution to agree on what groups should be utilized. • Creation of applicable Field Selectors (here) and Data Tests (here) • Setup of the Resource Definition (here – manual page: # 105383)

  8. WebBridge – Bridging the Catalog and Electronic Resources • Once set up, patrons will see the following:

  9. WebBridge – Bridging the Catalog and Electronic Resources • Which, when clicked, applies the dynamic queries.

  10. WebBridge – Bridging the Catalog and Electronic Resources • Example: • http://oasis.oregonstate.edu

  11. WebBridge – Bridging the Catalog and Electronic Resources • Long-term maintenance • Can make maintenance more difficult for a couple of reasons: • Duplicate resource definitions would need to exist if an institution wanted to maintain the traditional WebBridge functionlity within the catalog (i.e., OpenURL resolution) and generate the dynamic relationships. Why? • WebBridge doesn’t allow the creation of data tests that test for the absence of values. • A resource can only have one behavior associated with it.

  12. WebBridge – Bridging the Catalog and Electronic Resources • Long-term maintenance • Can make maintenance more difficult for a couple of reasons: • Means that new resources must be identified during coverage loads and added to their dynamic groups.

  13. WebBridge – Building New Bridges • While WebBridge itself is a closed system, making feature modification nearly impossible, we can make use of custom scripts to augment, enhance or simply provide new functionality. • Examples: • Extending WebBridge to work directly with CrossRef and DOIs for article resolution. • Working with OpenURL 1.0/non-SID friendly resources. • Working to make WebBridge ILL friendly.

  14. WebBridge – Building New BridgesWorking with CrossRef/DOIs • What is CrossRef? • In order to understand CrossRef, we must first understand DOIs…so…what is a DOI? • “Digital Object Identifier (DOI) is a system for identifying and exchanging intellectual property in the digital environment.” (http://www.doi.org) • It’s a publisher supported method for generating unique and permanent identifiers for online content at the article level.

  15. WebBridge – Building New BridgesWorking with CrossRef/DOIs • What is CrossRef? • So where does CrossRef come in? • CrossRef (http://www.crossref.org) is a free (for libraries) DOI resolution system. • CrossRef takes an OpenURL query and attempts to locate the DOI associated with a particular article. • It allows interroperability between systems that support OpenURL with journal publishers that only support DOI linking.

  16. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Why CrossRef/DOI? • While OpenURL affords a handy method for resource discovery against coverage data – DOIs actually offer a better method of linking directly to an article (and at providing a permanent link). • Many publishers make their information available via two methods: • HTTP Query (i.e., search page) • DOI (for external linking)

  17. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Why CrossRef/DOI? • Ease of use – • Using CrossRef to link to article level data allow institutions to utilize a single query syntax for multiple Resource Definitions. • i.e. – The resource definition for Hawthorne Press journals would be identical to the resource definition for Science Direct. • Using CrossRef/DOIs simplifies long-term resource maintenance. At OSU, approximately 65% of our resources can be accessed via CrossRef and 6 of our 12 external data sources that we link out from provide the ability to link directly via DOI.

  18. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Current WebBridge support for CrossRef and DOIs • Confusing: • Currently, WebBridge supports the use of DOIs to do coverage linking. However, WebBridge currently ignores using DOIs for direct article linking. • Pros: If only a DOI is passed, then it can be resolved against the Coverage data to determine if the library has access. • Cons: More likely use of the DOI is as an additional identifier that can be passed through the OpenURL. In this case, coverage has been resolved and DOI should be used for direct article resolution – but currently is not. • WAM difficulties: Originally, we had difficulties with a number of resources dropping the WAM authorization between the CrossRef/DOI/Resource redirection.

  19. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Current WebBridge support for CrossRef and DOIs • Inability to properly test for the presence of a DOI identifier within an OpenURL query without needing to create duplicate resource definition. • Difficulty dealing with variations in how DOI’s are passed via the OpenURL. • Example: • Proper construction: id=doi:[######] • Some aggregator implementations: id=[######] • Some aggregator implementations: <id>doi:[#######]</id>

  20. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Adding CrossRef/DOI support • Because so many of OSU’s resources can be queried either via CrossRef or directly via DOI – having the ability to do so represented an easy method of simplifying our day to day maintenance since every resource that utilized a DOI or CrossRef would share the same Resource URL. • i.e. – all resources that utilize CrossRef or DOIs use the following URL: http://osulibrary.oregonstate.edu/oasis/webbridge/doi.php?debug_title=#@TITLE#&id=#@ID#&url=doi.crossref.org/resolve?pid=osul:osul1211%26aulast=#@AULAST#%26issn=#@ISSN#%26volume=#@VOLUME#%26issue=#@ISSUE#%26spage=#@SPAGE#%26date=#@YEAR#

  21. WebBridge – Building New BridgesWorking with CrossRef/DOIs • Adding CrossRef/DOI support • DOI/CrossRef support was created using a PHP script. • PHP script navigates the CrossRef and DOI resolvers to retrieve a link to a requested article. • PHP script then re-writes the URL so that it forces users through our proxy. • PHP script allows OSU to handle failed CrossRef queries gracefully.

  22. WebBridge – Building New BridgesWorking with OpenURL 1.0 • Had difficulty working with resources that didn’t pass a SID or wanted to send data in OpenURL 1.0 format. • Alternative gateway script – translates OpenURL 1.0 data to OpenURL 0.1 or vise versa. Also, adds generic SID if one is not present in the OpenURL 0.1 output.

  23. WebBridge – Building New BridgesWorking with OpenURL 1.0 • Example OpenURL 1.0 Query: http://osulibrary.oregonstate.edu/oasis/webbridge/alt_oai.php?url_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rfe_id=http%3A%2F%2Fscholar.google.com%2Fscholar%3Fq%3Dfish%2Bruns%26ie%3DUTF-8%26oe%3DUTF-8%26hl%3Den%26btnG%3DSearch&rft_id=info:pmid/10580499&rfr_id=info:sid/openly.com:openurlref&rft.genre=article&rft.jtitle=Nature&rft.date=1999&rft.atitle=Use%20of%20behavioural%20stochastic%20resonance%20by%20paddle%20fish%20for%20feeding&rft.aulast=Russell&rft.auinit=DF&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx • Converted to OpenURL 0.1: http://oasis.oregonstate.edu:4550/resserv?sid=GEN:USER&atitle=Use%20of%20behavioural%20stochastic%20resonance%20by%20paddle%20fish%20for%20feeding&aulast=Russell&date=1999&genre=article&id=info:pmid/10580499&title=Nature

  24. WebBridge – Building New BridgesILL Friendly Links • ILL OpenURL implementation at OSU • Implementation was low-key, with no real official announcement to the public. • OpenURL interface to ILLiad was purposely disabled to test WebBridge usage.

  25. WebBridge – Building new bridgesILL friendly links • ILL OpenURL implementation at OSU • While usage has been modest since implementation, it has remained steady • Feb. 2004: 5400 total hits: 298 ILL requests (1:18) • May 2004: 6100 total hits: 450 ILL requests (1:13) • July 2004: 3500 total hits: 288 ILL requests (1:12) • Note that as time has passed as users start using the system, more ILL requests are resulting per OpenURL request.

  26. WebBridge – Building new bridgesILL friendly links • While the OpenURL interface simplifies making an ILL request and generally cuts down on errors within the request, OpenURL: • Makes submitting ILL requests too easy (students may have a tendency to use ILL staff to perform their research for them). • Generally not all library materials can be found by one’s OpenURL software. Patrons may not take the time to check other information sources.

  27. WebBridge – Building new bridgesILL friendly links • Potential solutions: • Before submitting materials to ILL, the request passes through a script that searches the Library’s Catalog, Summit (INNReach system) and the OSU E-Journals List (which includes all 17,000 available titles). • If no items are returned – the ILL request is allowed to proceed. If materials are returned, the ILL request is interrupted to display the intermediate results.

  28. WebBridge – Building new bridgesILL friendly links

  29. WebBridge – Building new bridgesILL friendly links

  30. Resources/Links: • Presentation Links: • Presentation can be downloaded from: http://hdl.handle.net/1957/72 • ILL Resource Share presentation can be downloaded from: http://oregonstate.edu/~reeset/presentations/ill_2004_09_17.ppt • DOI/CrossRef PHP scripts: http://hdl.handle.net/1957/72 • ILL Linking demo script: http://hdl.handle.net/1957/72 • Alternative Linking Script: http://hdl.handle.net/1957/72

  31. Field Selectors – Manual page: #105497

  32. Data Tests: Manual Page: #105382

  33. Resource Definitions – Manual Page: #105383

More Related