Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Bibliosight at Leeds Met

869 views

Published on

jiscri project at Leeds Metropolitan University looking at the Web of Science API to auto-populate Institutional Repositories with bibliographic records and retrieve/display citation data

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Bibliosight at Leeds Met

  1. 1. Nick Sheppard <ul><li>Repository Development Officer </li></ul><ul><li>The Headingley Library, James Graham Building </li></ul><ul><li>Leeds Metropolitan University, Beckett Park </li></ul><ul><li>Leeds, LS6 3QS </li></ul><ul><li>Tel: 0113 812 4731 </li></ul><ul><li>[email_address] </li></ul><ul><li>Project blog: http://bibliosightnews.wordpress.com/ </li></ul><ul><li>Twitter tags: #bibliosight, #jiscri </li></ul><ul><li>Twitter: http://twitter.com/mrnick </li></ul>
  2. 2. Bibliosight <ul><li>JISC Rapid Innovation project (#jiscri) </li></ul><ul><li>Web of Science API </li></ul><ul><li>Thomson Reuters research analytics </li></ul><ul><ul><li>InCites/Journal Citation Reports/Essential Science Indicators </li></ul></ul><ul><ul><li>Web Services </li></ul></ul><ul><ul><ul><li>ResearcherID </li></ul></ul></ul><ul><ul><ul><li>Article Match Retrieval </li></ul></ul></ul><ul><ul><ul><li>API </li></ul></ul></ul><ul><li>http://researchanalytics.thomsonreuters.com/ </li></ul>
  3. 3. Use cases <ul><li>Automatically retrieve records from WoS to auto-populate our repository </li></ul><ul><ul><li>Desktop client - “Bib App” </li></ul></ul><ul><li>Targeted communication to researchers to encourage deposit of author produced version of recently published/cited paper </li></ul><ul><li>Citation linking – number of citations </li></ul><ul><ul><li>Display alongside search results? </li></ul></ul><ul><ul><li>Potential use cases for research admin (including REF) </li></ul></ul>
  4. 5. Web of Science web services <ul><li>API can query WoS using fields: </li></ul><ul><li>Address (Street, City, Province, Zip Code, Country) </li></ul><ul><li>Author </li></ul><ul><li>Conference (including title, location, data, and sponsor) </li></ul><ul><li>Group Author </li></ul><ul><li>Organization or Sub-organization </li></ul><ul><li>Source Publication (journal, book or conference) </li></ul><ul><li>Title </li></ul><ul><li>Topic </li></ul><ul><li>Year Published </li></ul><ul><li>Article Match Retrieval </li></ul><ul><li>Uses unique identifier to return Times Cited information </li></ul>
  5. 6. WoS API <ul><li>Returns five fields to the requesting system: </li></ul><ul><li>Article Title </li></ul><ul><li>Authors — All authors, book authors, and corporate authors </li></ul><ul><li>Source — Includes the source title, subtitle, book series and subtitle, volume, issue, special issue, pages, article number, supplement number, and publication date </li></ul><ul><li>Keywords — all author supplied keywords </li></ul><ul><li>UT — A unique article identified provided by Thomson Reuters </li></ul><ul><li>(UT used for Article Match Retrieval to retrieve Times cited information) </li></ul>
  6. 7. Example query <ul><li>SearchResults results = </li></ul><ul><li>client.searchRetrieve(databaseID, </li></ul><ul><li>query, </li></ul><ul><li>depth, </li></ul><ul><li>editions, </li></ul><ul><li>sort, </li></ul><ul><li>firstRec, </li></ul><ul><li>numRecs, </li></ul><ul><li>fields); </li></ul><ul><li>SearchResults results = </li></ul><ul><li>client.searchRetrieve(&quot;WOS&quot;, </li></ul><ul><li>&quot;AD=(leeds met* univ*)&quot;, </li></ul><ul><li>&quot;2006&quot;, </li></ul><ul><li>&quot;&quot;, </li></ul><ul><li>&quot;Date&quot;, </li></ul><ul><li>1, </li></ul><ul><li>10, </li></ul><ul><li>&quot;bib_date bib_issue bib_pagecount bib_pages bib_id bib_vol item_title source_title authors ut&quot;); </li></ul>
  7. 9. XML records from WoS <ul><li>intraLibrary – UK LOM (with bibliographic extensions) </li></ul><ul><li>Map fields from WoS API => LOM using XSLT </li></ul><ul><li>Comprehensive records </li></ul><ul><li>Consistent format </li></ul><ul><ul><li>bib_id - Volume, issue, special, pages, year data </li></ul></ul><ul><ul><li>bib_issue - Volume and year data </li></ul></ul><ul><ul><li>bib_vol - Issue and volume (not returned?) </li></ul></ul>
  8. 10. Desktop Client <ul><li>Three discrete functional requirements of “Bib App” </li></ul><ul><ul><li>Retrieve records from WoS as XML </li></ul></ul><ul><ul><li>Perform appropriate XSLT transformation </li></ul></ul><ul><ul><li>Deposit LOM records into intralibrary via SWORD </li></ul></ul><ul><li>Other XSLT transformations? </li></ul><ul><ul><li>EndNote </li></ul></ul><ul><ul><li>EPrints </li></ul></ul>
  9. 11. Getting records into the repository <ul><li>SWORD allows for metadata records to </li></ul><ul><li>be deposited into a repository from outside </li></ul><ul><li>of that repository </li></ul><ul><li>Aim to incorporate functionality into “Bib App” </li></ul><ul><li>Implications for UC_2 </li></ul><ul><ul><li>Copyright (SHERPA/RoMEO API?) </li></ul></ul><ul><ul><li>Conditions/restrictions for OA e.g. embargo </li></ul></ul>

×