1 / 19

Linking Service to Open Access Repositories

Linking Service to Open Access Repositories. AIRway Project SUGITA Shigeki and SUZUKI Masako (Hokkaido University Library, JAPAN) 23-26 Oct. 2006 Leeds, Cranfield and Bath. AIRway Project. Launched 2006 Access Path to Institutional Resources via Link Resolvers

yardley-rosario
Download Presentation

Linking Service to Open Access Repositories

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. Linking Service toOpen Access Repositories AIRway Project SUGITA Shigeki and SUZUKI Masako (Hokkaido University Library, JAPAN) 23-26 Oct. 2006 Leeds, Cranfield and Bath

  2. AIRway Project • Launched 2006 • Access Path to Institutional Resources via Link Resolvers • Funded by NII (National Institute of Informatics, JAPAN • Partners • Hokkaido University • Openly, OCLC • And, • University of Tsukuba • Chiba University • Nagoya University • Kyushu Universtity • NII Leeds, Cranfield and Bath

  3. Roadmap • Phase 1 (May – Sep. 2006) • One IR and One Link Resolver • Phase 2 (Oct. 2006 -) • Many IRs and Many Link Resolvers Leeds, Cranfield and Bath

  4. AIRway Phase 1 • Hokkaido University and Openly, OCLC HUSCAP (Institutional Repository) 1CATE (Link Resolver) Leeds, Cranfield and Bath

  5. HUSCAP • Approximately 1,400 articles of Thomson-indexed journals • Many of them areauthors’ final drafts • DSpace 1.3.2 Leeds, Cranfield and Bath

  6. Users of HUSCAP • From university web site • From Google(and other search engines or directories) • From OAIster(and OAI-compliant service providers) Leeds, Cranfield and Bath

  7. And • We’d like to provide EJ non-licensed users author version in HUSCAP Leeds, Cranfield and Bath

  8. Present condition Web of Science SCOPUS PubMed SciFinder INSPEC Google Scholar : Link resolver’s navigation window Full Text at: 　・ Science Direct Science Direct Springer LINK Wiley Interscience : EJ licensed users EJ non-licensed users Link resolver’s navigation window Full Text at: 　・N/A Science Direct Springer LINK Wiley Interscience : Leeds, Cranfield and Bath

  9. To be Web of Science SCOPUS PubMed SciFinder INSPEC Google Scholar : Link resolver’s navigation window Full Text at: 　・ Science Direct 　・ Author version Science Direct Springer LINK Wiley Interscience : EJ licensed users EJ non-licensed users Link resolver’s navigation window Full Text at: 　・ Author version Institutional Repositories Including HUSCAP Leeds, Cranfield and Bath

  10. What is concerned here is NOT lucky-shot link Institutional Repositories *the median number of documents per site=290 Link resolvers If only the base target url is given… (e.g. http://the.ir.server/query?id=) http://the.ir.server/query?id=A Too many “Not Found” A http://the.ir.server/query?id=B http://the.ir.server/query?id=C D http://the.ir.server/query?id=D http://the.ir.server/query?id=E Leeds, Cranfield and Bath

  11. What is needed? • Rich metadata in IR • rich enough to be matched with publisher version • Z39.88 (OpenURL) compliant? • Or publisher version’s DOI? • How should the metadata be given to link-servers? • Preliminary harvesting into the knowledgebase? • Or on-the-fly transaction? • Super repository needed for IRs? (like CrossRef) Link resolvers’ navigation window Full Text at: 　・ Science Direct 　・ Author version Leeds, Cranfield and Bath

  12. HUSCAP metadata, again What is the advantage of HUSCAP? machine understandable metadata e.g. another IR Leeds, Cranfield and Bath

  13. What is needed? • Rich metadata in IR • rich enough to be matched with publisher version • Z39.88 (OpenURL) compliant? • Or publisher version’s DOI? • How should the metadata be given to link resolvers • Preliminary harvesting into the knowledgebase? • Or on-the-fly transaction? • Super metadata repository needed for IRs? (like CrossRef) Leeds, Cranfield and Bath

  14. Two Options Option 1 (preliminary harvesting) Option 2 (on-the-fly) OpenURL Request Creating navigation window OpenURL Request Creating navigation window Link resolver Link resolver HUSCAP metadata Preliminary harvesting HUSCAP HUSCAP 1CATE chose on-the-fly Leeds, Cranfield and Bath

  15. HUSCAP Implementation • OpenURL resolver at: http://eprints.lib.hokudai.ac.jp/dspace/openURL • reply to OpenURL0.1/1.0 requests, based on ir.xsd.ex. http://eprints.lib.hokudai.ac.jp/dspace/openURL?url_ver=Z39.88-2004&rft_id=info:doi/10.1016/j.foodchem.2005.03.008 • ir.xsd at:http://eprints.lib.hokudai.ac.jp/ir.xsd Leeds, Cranfield and Bath

  16. Response by HUSCAP Leeds, Cranfield and Bath

  17. 1CATE Implementation Leeds, Cranfield and Bath

  18. AIRway Phase 2 (Nov. 2006-) Option 1 (preliminary harvesting) Option 2 (on-the-fly) OpenURL Request Creating navigation window OpenURL Request Creating navigation window vendors’ choice Link resolver Link resolver IRs metadata Preliminary harvesting To be opened Nov. 2006 AIRway (like CrossRef) AIRway (like CrossRef) OAI-PMH OAI-PMH IR IR IR IR IR IR IR IR IR IR Leeds, Cranfield and Bath

  19. Conclusion • We, as a repository, need linking service to open access repositories for our researchers as authors • And we, as a library, need linking service to open access repositories for our researchers as readers • We’d like you to join us! Leeds, Cranfield and Bath

More Related