L&LR staff blog

Sharing information about our work at the University.

Archive for the ‘EBSCO’ tag

My Mashed Library lightning talk – atoz’n'rss

with 2 comments

Edit (8th July) – slideshare.net does not seem to like displaying these slides on-screen, so here they are to download in MS PowerPoint format.

Here are the slides (on slideshare.net) of the 5-minute lightning talk I just gave at Mashed Library 2009, on using ticTOCs data to display e-journal ToC feeds, and on creating a new-titles feed with Yahoo Pipes, etc.

Mashing up the A-to-Z: new titles feed

without comments

In February, I wrote about  how I’d added more than 5,000 ticTOCs RSS feeds to the A-to-Z, so that researchers can easily find and subscribe to Table-of-Contents (ToC) updates from journals in their field. I think this is an indispensable current awareness service, and I’m pleased it’s being promoted at the ‘Working Smarter With the Web‘ workshops.

(An aside: that ticTOCs data is overdue to be re-generated and reloaded onto the A-to-Z. This is next on the long list of e-journal packages for the “e team” to review.)

That’s all well and good, but there’s a clear need for a current awareness service ‘one level above’ the individual ToCs. That is, we could (and should) be providing an RSS feed of new e-journal titles.

feed-icon-28x28

At the moment, the EBSCO A-to-Z platform doesn’t provide this feature (I really do hope it’s something that EBSCO are considering developing themselves), and so in the past we’ve had to resort to emails, spreadsheets, etc.—all with varying degrees of success—just to keep people up to date with what new e-journals have become available.

~~~

So, I’ve created a rough-and-ready working demo of a ‘New e-journals at Lincoln RSS feed for the A-to-Z. It’s not supported by EBSCO, so it’ll require a bit of manual intervention to keep it running (it’ll be a nice five-minute daily task for the “e team” to take on!), but has the potential to be a really important enhancement to the e-journals service.

screenshot_atoz_rsstab

Next time you go to the A-to-Z site, you’ll see a new tab – next to the existing ‘Titles’ tab – which I’ve labelled ‘New Titles (RSS)‘. This new tab links to a page containing information about the RSS feed, with a prominent link to the feed itself, plus a display of the 10 most-recently-added titles in the feed.

screenshot_atoz_rsspage

The links in the ‘ten most recent…’ list should go directly to the A-to-Z record for that title. The feed link itself you can paste into your favourite feed reader (I use Google Reader). I’m working on enabling email subscription to the feed. We should also be able to take this feed and filter/manipulate it to create (for example) subject-specific lists in Blackboard.

I’ve also made the feed autodiscoverable (c.f. my earlier post), so it should display in the browser toolbar (this will vary between browsers).

This is how the feed is auto-discovered by Firefox browser.

This is how the feed is auto-discovered by Firefox browser.

I still need to do some work on creating better documentation for users of the feed, and for the process of adding new titles within L&LR.

I’ll also need to do a bit of testing to make sure everything’s working as it should be, and iron out my feed-validation bugs.

When the time is right, I’ll launch the service more publicly.

Paul

~~~

P.S. Here’s how I did it:

  1. The first stage is the most clunky – it involves getting information about the newly-added titles out of the closed box that is the Electronic Journals A-to-Z. EBSCO provide a daily report (available only to administrators) of “Titles added to Packages in my Collection“. This data can be exported on a daily basis in tab-delimited format.
    screenshot_atozadmin_report
  2. Next, I created a spreadsheet using Google Docs and published it to the Web. The tabbed data from the A-to-Z admin report is pasted in to the spreadsheet, so it becomes openly accessible. Using Google Docs also means that I can invite other people to act as editors of the spreadsheet, and create public web forms to add titles that don’t appear in EBSCO’s daily report (not all of our e-journal packages are managed by EBSCO, so the data will need supplementing when we add custom titles).
  3. The data output of the Google spreadsheet is then fed into Yahoo! Pipes, an excellent application for ‘mashing up’ and processing data. You can inspect the Yahoo! pipe for yourself, at: http://pipes.yahoo.com/lincoln/newejournals. If you create an account on Yahoo!, you can clone this (or any) pipe and modify it to create your own data mashup.
    screenshot_pipes_atoz
  4. The Yahoo! pipe takes the raw Google spreadsheet data, filters it according to various rules, and exports a valid * RSS feed of new items, in reverse order by date.
  5. * Well, it’s nearly valid. I need to do a bit of cleaning up of the pipe (I did say this was a working demo), mainly so I can pass the feed through Feedburner, which will allow email subscriptions. But it works well enough!
  6. Finally, I created the new tab on the A-to-Z public site, and added the details to the page (the ‘ten most recent’ list was created using feed2js). The code for the autodiscoverable feed was pasted into the top of our customised A-to-Z template.

~~~

Written by Paul Stainthorp

April 30th, 2009 at 4:44 pm

The Business of persistent links

with 4 comments

Academic librarians are unhappy that some of the UK’s largest university business schools are being asked to pay extra to be allowed to link to articles published in a key journal in their field.

Harvard Business Review (issn:0017-8012), published by HBP (Harvard Business Press), has long been available as part of the EBSCOhost Business Source suite of databases.

However, in an email to the chair of the BBSLG (British Business Schools Librarians Group), EBSCO outlined that, as a vendor of HBP’s content, they are obliged to disable persistent linking to Harvard Business Review, at the publisher’s request.

According to EBSCO, the terms & conditions of their supply of HBP content have always included a clause limiting use of the journal to individual, private study, and explicitly prohibiting linking from Virtual Learning Environments (VLEs) for teaching purposes.

Three libraries have already had their facility to create persistent links removed, according to the BBSLG, who have written a letter of complaint to EBSCO.

A flyer circulated by EBSCO ‘invites’ individual BBSLG member-libraries to upgrade their EBSCOhost Business Source subscriptions to a level which would “continue to allow [the institution] to persistent link to HBR articles for an additional annual fee“: each institution’s fee being calculated on past use of the journal and their business-school student numbers.

For one, Russell Group, UK university, EBSCO have demanded £15,000 in order that the institution be allowed to go on creating persistent links for use in teaching.

According to correspondence between EBSCO and the BBSLG, Harvard Business Press are concerned that unauthorised persistent-linking from VLEs to EBSCOhost has harmed HBP’s separate provision of course packs for HEIs on a commercial basis. They cite a “direct quantifiable link between the two which can be clearly demonstrated financially between the diminishing course pack use and persistent linking“.

Should institutions decline the opportunity to pay the additional EBSCOhost fee, EBSCO asks that they inform their users that persistent-linking from a VLE to the HBR is not permitted, and that EBSCO may disable the ability to create such links.

This will not only remove the ability of academic staff to create links from a VLE, but also break any persistent links to the e-journal created by individuals in the course of their own personal study or research.

~~~

This is a retrograde step for usability in online scholarly content. Storing, recalling, and broadcasting stable hyperlinks is fundamental to the Web. It is not an add-on or a luxury.

Private, subscription-only environment it may be, but users of EBSCOhost [remembering that this includes fee-paying students] have had the rug pulled from under a basic Web experience. It may currently affect only one journal title, in one database, but this is a dangerous precedent, and one that the library community has a right to question and challenge.

Paul