Tag: DC

ER&L 2013: Truth or Dare — Discovery Systems Secrets Unveiled

“Space Shuttle Discovery Landing At Washington DC” by Glyn Lowe

Moderator: Dan Tonkery
Panel: Roger Schonfeld (ITHAKA S + R), Jon Law (ProQuest), Amira Aaron (Northeastern University), Brian Duncan (EBSCO), & Susan Stearns (Ex Libris)

What features of discovery services do students prefer? What ones do they dislike?

Law: The search box is intuitive and familiar, and their expectations of speed are set by web search engines. Being able to quickly scan the abstract to see if it is relevant, and then quickly retrieve the content when they want it.

Stearns: Needs to be flexible and reflective of different user types and the environment they are in. Contextual searching based on who they are and how they look for information. Students also expect to access related content about their relationship with libraries (i.e. materials checked out, notices).

Duncan: Finding the results on the first page, and at least the second page. Metadata and relevancy are important.

What impact is open access having on discovery?

Aaron: Depends on the model of OA. Not really sure if it has an impact on discovery systems yet. It has and will have an impact on discovery in general, but not sure if it’s impacting library discovery systems any more or less than open web searches.

Law: Our customers are turning OA links on in the discovery service.

Stearns: It’s easy to make the OA content available, but are you managing it? How does this impact back-office workflows?

Will discovery services replace the online catalog?

Stearns: It’s been painful for some libraries, but yes. There is no OPAC in next generation library systems, it’s all about discovery. And we need to get over it. Discovery services need to have the functionality of the OPAC (things librarians like). This is an opportunity to rethink workflows and what you do with metadata in a discovery environment.

What are the advantages of selling both a family of databases and a discovery service?

Duncan: Users have automatic full-text because it’s built into the system and doesn’t need to go through OpenURL. Thinking a lot about how to make this simpler for students and integrating high-quality metadata from A&I sources along with the full-text.

Aaron: That’s fine for the vendor, but it takes away the choice for the librarian as to where to send the user. It’s taking away choice.

Law: We want our discovery service to be content-provider neutral.

What impact can libraries reasonably expect discovery services to have on traffic patterns?

Schonfeld: We see the majority of traffic coming from Google and Google Scholar, at least for JSTOR. If the objective is to change where users are starting their research, then we need different ways of measuring that and determining success.

Stearns: Our customers are thinking about not only having the one search box on the web page, but also where else can you embed linking and making sure the connections work, particularly when users come in from different sources.

Aaron: Success is not measured by how many people come to your website and start there, it’s how they get to the content from wherever they go.

What metrics do librarians expect from discovery services?

Aaron: Search statistics aren’t very meaningful in the context of discovery services. Click-through, content sources — those are the important metrics.

Schonfeld: This is not just a new product – it replaces old products, so we need to think about it differently. Libraries might want to know what share of their users is coming from what sources (i.e. discovery services, Wikipedia, Google, etc.). It’s still early days to be able to come to any strong conclusions.

Duncan: Need to measure searches that don’t result in any click-throughs as well.

Does your discovery product provide title-level information to the user community and how often is it updated?

Law: How do you measure your collection? We need some definition around this in order to know how to tell libraries how much of it is indexed in our discovery service. We are starting to do more collection analysis for libraries.

Duncan: The title list doesn’t equate to the deep metadata of an A&I database. If we don’t have the deep metadata, we don’t say we have the same coverage as that database. Full text searching is not a replacement for controlled vocabulary and metadata, it’s just a component of it.

Stearns: We also want to make sure the collections we expose are actually the ones the users access, by looking at historical usage information.

Aaron: It’s important to have the deep metadata, and it’s troubling that the content providers aren’t playing well together. I should be able to display content we purchase to our users in whatever interface I want. If I can’t, I may not continue to purchase or lease that content. It’s the same problem we had with link resolvers years ago. If you really care about the user and libraries, then start playing together.

[Missed the last question because I was still flying high from Aaron’s call-out, but it was something dull about how much customization is available in the discovery system, or something like that. Couldn’t tell from the responses. Go read product information for the answers.]

conference tweeting etiquette

“Tiny birds in my hand..” by ~Ilse

Conference season, or at least the part of it that appeals to my area of librarianship, is starting soon.

Up first for me is Computers in Libraries in DC, where I won’t be attending, but instead vacationing nearby (since it is so close) and visiting with colleagues and friends who will be attending. I’d go, but I already have funding this year for three conferences, and it didn’t seem fair to ask for another.

Next,  I fly to Austin for the Electronic Resources & Libraries conference. From the venue to the content, this is becoming my favorite conference. I’ve had to actively introduce more diversity to the sessions I choose to attend, otherwise I would spend the whole conference geeking out about use data and spreadsheets and such.

Finally, I head to Buffalo for the conference that shaped me into the librarian I became: NASIG (North American Serials Interest Group). I like this one because I’ve known many of the attendees for the entirety of my relatively short career, and because it works very hard to not be just a librarian conference, but rather an industry-wide discussion of all things serial in libraryland.

It was in the context of thinking about these upcoming conferences that I read the latest Prof Hacker blog post from The Chronicle of Higher Education. Ryan Cordell writes about his experiences with conference tweeting and the recent revelations he has had regarding the impact this can have on the presenters, whether they are active participants on Twitter or not. Many things he wrote resonated with me, and reminded me that Twitter — as well as other popular social media platforms — is no longer the private back-channel of a few techie friends, but is a global platform that can have a broader impact than any of us may know.

I suggest reading the whole article, but I would like to quote here the Principles of Conference Tweeting that Cordell offers, as something for us all to keep in mind:

  1. I will post praise generously, sharing what I find interesting about presentations.
  2. Likewise, I will share pertinent links to people and projects, in order to bring attention to my colleagues’ work.
  3. When posting questions or critiques, I will include the panelist’s username (an @ mention) whenever possible.
  4. If the panelist does not have a username—or if I cannot find it—I will do my best to alert them when I post questions or critiques, rather than leaving them to discover those engagements independently.
  5. I will not post questions to Twitter that I would not ask in the panel Q&A.
  6. I will not use a tone on Twitter that I would not use when speaking to the scholar in person.
  7. I will avoid “crosstalk”—joking exchanges only tangentially related to the talk—unless the presenter is explicitly involved in the chatter.
  8. I will refuse to post or engage with posts that comment on the presenter’s person, rather than the presenter’s ideas.

Serials Solutions DC Users Group Meeting 2012

Meeting Table by Mo Elnadi
“Meeting Table” by Mo Elnadi

Updates from Serials Solutions – mostly Resource Manager (Ashley Bass):

  • Keep up to date with ongoing enhancements for management tools (quarterly releases) by following answer #422 in the Support Center, and via training/overview webinars.
  • Populating and maintaining the ERM can be challenging, so they focused a lot of work this year on that process: license template library, license upload tool, data population service, SUSHI, offline date and status editor enhancements (new data elements for sort & filter, new logic, new selection elements, notes), and expanded and additional fields.
  • Workflow, communication, and decision support enhancements: in context help linking, contact tool filters, navigation, new Counter reports, more information about vendors, Counter summary page, etc. Her most favorite new feature is “deep linking” functionality (aka persistent links to records in SerSol). [I didn’t realize that wasn’t there before — been doing this for my own purposes for a while.]
  • Next up (in two weeks, 4th quarter release): new alerts, resource renewals feature (reports! and checklist!, will inherit from Admin data), Client Center navigation improvements (i.e. keyword searching for databases, system performance optimization), new license fields (images, public performance rights, training materials rights) & a few more, Counter updates, SUSHI updates (making customizations to deal with vendors who aren’t strictly following the standard), gathering stats for Springer (YTD won’t be available after Nov 30 — up to Sept avail now), and online DRS form enhancements.
  • In the future: license API (could allow libraries to create a different user interface), contact tools improvements, interoperability documentation, new BI tools and reporting functionality, and improving the Client Center.
  • Also, building a new KB (2014 release) and a web-scale management solution (Intota, also coming 2014). They are looking to have more internal efficiencies by rebuilding the KB, and it will include information from Ulrich’s, new content types metadata (e.g. A/V), metadata standardization, industry data, etc.

Summon Updates (Andrew Nagy):

  • I know very little about Summon functionality, so just listened to this one and didn’t take notes. Take-away: if you haven’t looked at Summon in a while, it would be worth giving it another go.

360 Link Customization via JavaScript and CSS (Liz Jacobson & Terry Brady, Georgetown University):

Goal #1: Allow users to easily link to full-text resources. Solution: Go beyond the out-of-the box 360 Link display.
Goal #2: Allow users to report problems or contact library staff at the point of failure. Solution: eresources problem report form

They created the eresources problem report form using Drupal. The fields include contact information, description of the resource, description of the problem, and the ability to attach a screenshot.

When they evaluated the slightly customized out of the box 360 Link page, they determined that it was confusing to users, with too many options and confusing links. So, they took some inspiration from other libraries (Matthew Reidsma’s GVUS jQuery code available on Github) and developed a prototype that uses custom JavaScript and CSS to walk the user through the process.

Some enhancements included: making the links for full-text (article & journal) butttons, hiding additional help information and giving some hover-over information, parsing the citation into the problem report page, and moving the citation below the links to full-text. For journal citations with no full-text, they made the links to the catalog search large buttons with more text detail in them.

Some of the challenges of implementing these changes is the lack of a test environment because of the limited preview capablities in 360 Link. Any changes actually made required an overnight refresh and they would be live, opening the risk of 24 hour windows of broken resource links. So, they created their own test environment by modifying test scenarios into static HTML files and wrapping them in their own custom PHP to mimic the live pages without having to work with the live pages.

[At this point, it got really techy and lost me. Contact the presenters for details if you’re interested. They’re looking to go live with this as soon as they figure out a low-use time that will have minimal impact on their users.]

Customizing 360 Link menu with jQuery (Laura Wrubel, George Washington University)

They wanted to give better visual clues for users, emphasize the full-text, have more local control over linkns, and visual integration with other library tools so it’s more seamless for users.

They started with Reidsma’s code, then then forked off from it. They added a problem link to a Google form, fixed ebook chapter links and citation formatting, created conditional links to the catalog, and linked to their other library’s link resolver.

They hope to continue to tweak the language on the page, particularly for ILL suggestion. The coverage date is currently hidden behind the details link, which is fine most of the time, but sometimes that needs to be displayed. They also plan to load the print holdings coverage dates to eliminate confusion about what the library actually has.

In the future, they would rather use the API and blend the link resolver functionality with catalog tools.

Custom document delivery services using 360 Link API (Kathy Kilduff, WRLC)

They facilitate inter-consortial loans (Consortium Loan Service), and originally requests were only done through the catalog. When they started using SFX, they added a link there, too. Now that they have 360 Link, they still have a link there, but now the request form is prepopulated with all of the citation information. In the background, they are using the API to gather the citation information, as well as checking to see if there are terms of use, and then checking to see if there are ILL permissions listed. They provide a link to the full-text in the staff client developed for the CLS if the terms of use allow for ILL of the electronic copy. If there isn’t a copy available in WRLC, they forward the citation information to the user’s library’s ILL form.

License information for course reserves for faculty (Shanyun Zhang, Catholic University)

Included course reserve in the license information, but then it became an issue to convey that information to the faculty who were used to negotiating it with publishers directly. Most faculty prefer to use Blackboard for course readings, and handle it themselves. But, they need to figure out how to incorporate the library in the workflow. Looking for suggestions from the group.

Advanced Usage Tracking in Summon with Google Anaytics (Kun Lin, Catholic University)

In order to tweak user experience, you need to know who, what, when, how, and most important, what were they thinking. Google Anayltics can help figure those things out in Summon. Parameters are easy ways to track facets, and you can use the data from Google Analytics to figure out the story based on that. Tracking things the “hard way,” you can use the conversion/goal function of Google Analytics. But, you’ll need to know a little about coding to make it work, because you have to add some javascripts to your Summon pages.

Use of ERM/KB for collection analysis (Mitzi Cole, NASA Goddard Library)

Used the overlap analysis to compare print holdings with electronic and downloaded the report. The partial overlap can actually be a full overlap if the coverage dates aren’t formatted the same, but otherwise it’s a decent report. She incorporated license data from Resource Manager and print collection usage pulled from her ILS. This allowed her to create a decision tool (spreadsheet), and denoted the print usage in 5 year increments, eliminating previous 5 years use with each increment (this showed a drop in use over time for titles of concern).

Discussion of KnowledgeWorks Management/Metadata (Ben Johnson, Lead Metadata Librarian, SerialsSolutions)

After they get the data from the provider or it is made available to them, they have a system to automatically process the data so it fits their specifications, and then it is integrated into the KB.

They deal with a lot of bad data. 90% of databases change every month. Publishers have their own editorial policies that display the data in certain ways (e.g., title lists) and deliver inconsistent, and often erroneous, metadata. The KB team tries to catch everything, but some things still slip through. Throught the data ingestion process, they apply rules based on past experience with the data source. After that, the data is normalized so that various title/ISSN/ISBN combinations can be associated with the authority record. Finally, the data is incorporated into the KB.

Authority rules are used to correct errors and inconsistencies. Rule automatically and consistently correct holdings, and they are often used to correct vendor reporting problems. Rules are condified for provider and database, with 76,000+ applied to thousands of databases, and 200+ new rules are added each month.

Why does it take two months for KB data to be corrected when I report it? Usually it’s because they are working with the data providers, and some respond more quickly than others. They are hoping that being involved with various initiatives like KBART will help fix data from the provider so they don’t have to worry about correcting it for us, but also making it easier to make those corrections by using standards.

Client Center ISSN/ISBN doesn’t always work in 360 Links, which may have something to do with the authority record, but it’s unclear. It’s possible that there are some data in the Client Center that haven’t been normalized, and could cause this disconnect. And sometimes the provider doesn’t send both print and electronic ISSN/ISBN.

What is the source for authority records for ISSN/ISBN? LC, Bowker, ISSN.org, but he’s not clear. Clarification: Which field in the MARC record is the source for the ISBN? It could be the source of the normalization problem, according to the questioner. Johnson isn’t clear on where it comes from.

IL 2012: Discovery Systems

Space Shuttle Discovery Landing At Washington DC
“Space Shuttle Discovery Landing At Washington DC” by Glyn Lowe

Speaker: Bob Fernekes

The Gang of Four: Google, Apple, Amazon, & Facebook

Google tends to acquire companies to grow the capabilities of it. We all know about Apple. Amazon sells more ebooks than print books now. Facebook is… yeah. That.

And then we jump to selecting a discovery service. You would do that in order to make the best use of the licensed content. This guy’s library did a soft launch in the past year of the discovery service they chose, and it’s had an impact on the instruction and tools (i.e. search boxes) he uses.

And I kind of lost track of what he was talking about, in part because he jumped from one thing to the next, without much of a transition or connection. I think there was something about usability studies after they implemented it, although they seemed to focus on more than just the discovery service.

Speaker: Alison Steinberg Gurganus

Why choose a discovery system? You probably already know. Students lack search skills, but they know how to search, so we need to give them something that will help them navigate the proprietary stuff we offer out on the web.

The problem with the discovery systems is that they are very proprietary. They don’t quite play fairly or nicely with competitor’s content yet.

Our users need to be able to evaluate, but they also need to find the stuff in the first place. A great discovery service should be self-explanatory, but we don’t have that yet.

We have students who understand Google, which connects them to all the information and media they want. We need something like that for our library resources.

When they were implementing the discovery tool, they wanted to make incremental changes to the website to direct users to it. They went from two columns, with the left column being text links to categories of library resources and services, to three columns, with the discover search box in the middle column.

When they were customizing the look of the discovery search results, they changed the titles of items to red (from blue). She notes that users tend to ignore the outside columns because that’s where Google puts advertisements, so they are looking at ways to make that information more visible.

I also get the impression that she doesn’t really understand how a discovery service works or what it’s supposed to do.

Speaker: Athena Hoeppner

Hypothesis: discovery includes sufficient content of high enough quality, with full text, and …. (didn’t type fast enough).

Looked at final papers from a PhD level course (34), specifically the methodology section and bibliography. Searched for each item in the discovery search as well as one general aggregator database and two subject-specific databases. The works cited were predominately articles, with a significant number of web sources that were not available through library resources. She was able to find more citations in the discovery search than in Google Scholar or any of the other library databases.

Clearly the discovery search was sufficient for finding the content they needed. Then they used a satisfaction survey of the same students that covered familiarity and frequency of use for the subject indexes, discovery search, and Google Scholar. Ultimately, it came down that the students were satisfied and happy with the subject indexes, and too few respondents to get a sense of satisfaction with the discovery search or Google Scholar.

Conclusions: Students are unfamiliar with the discovery system, but it could support their research needs. However, we don’t know if they can find the things they are looking for in it (search skills), nor do we know if they will ultimately be happy with it.

Kindle 2 is kind of cool, actually

I’m not going to gush about how I fell in love with the device, because I didn’t.

My library (as in, the library where I work) has the good fortune of being blessed with both funds and leadership that allow us to experiment with some emerging technologies. When Amazon released the first version of the Kindle, we purchased one to experiment with. It was simply the latest in a long history of ebook readers that we had hoped to be able to incorporate into the library’s function on campus.

I took a turn at using the Kindle, and I was mightily unimpressed. The interface seemed very clunky, to the point of preventing me from getting into the book I tried to read. When the Kindle 2 was released and we received permission to purchase one, I was skeptical that it would be any better, but I still signed up for my turn at using it.

Last week, I was given the Kindle 2, and since it already had a book on it that I was half-way through reading, I figured I would start there. However, I was not highly motivated to make the time for it. Yesterday afternoon, I took the train up to DC, returning this morning. Four hours round trip, plus the extra time spent waiting at each station, gave me plenty of time to finish my book, so I brought the Kindle 2 with me.

I’m not going to gush about how I fell in love with the device, because I didn’t. However, I finished the book with ease before I arrived in DC, and out of shear boredom I pulled down a copy of another book that was already purchased on our library account. I was pleasantly surprised by how easy it was to go from one book to another without having to lug along several selections from my library “just in case” I ran out of something to read.

Right now, I’m at least a third of the way in on the second book, and I plan to finish reading it on the Kindle 2.

I don’t think I’ll end up buying one anytime soon, particularly since I’ve put a stop to buying new books until I’ve read more of the ones I own. However, I have a better understanding of those Kindle enthusiasts who rave about having their entire library (and more) at their fingertips. It’s pretty handy if you’re someone who often has time to kill away from your library.

css.php