link resolver wording
Heintz, John P.
JPHEINTZ at STTHOMAS.EDU
Wed May 14 23:32:50 EDT 2014
Lise,
We went from Get It to Find It and back to Get It. We never should have taken journey. To me the key is you want people to click that link. To most students, once they've found an article in a database, it makes no sense to have to "Find It" again.
I didn't hear you say that those faculty who mentioned it were confused by the function of the icon/link, just that they disliked that it sometimes didn't produce the full-text. Mitigate that irritation by clear mapping and labeling to request via ILL on your results page, and by educating that handful of faculty (and staff, if that's an issue), that you can't actually afford all published content, and that your ILL is fast, convenient, and cost-effective. Don't chase the mirage of the "perfect" label.
John Heintz
University of St. Thomas
Sent from my Verizon Wireless 4G LTE DROID
WEB4LIB automatic digest system <LISTSERV at LISTSERV.ND.EDU> wrote:
There are 8 messages totaling 1658 lines in this issue.
Topics of the day:
1. Site Search Tool
2. Job Posting: Empire State Digital Network Technology Specialist
3. Link Resolver icon wording (5)
4. Netspeed 2014: Registration now open!
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
----------------------------------------------------------------------
Date: Wed, 14 May 2014 09:27:36 +0200
From: Christian Pietsch <chr.pietsch+web4lib at GOOGLEMAIL.COM>
Subject: Re: Site Search Tool
Dear Heather,
most search solutions are based on Apache Lucene. I agree with Mark
that Apache Nutch is an obvious choice for crawling, but you probably
do not need it given that all your files are local.
These days, most programmers do not use Lucene directly but use Solr
or Elasticsearch as an intermediate layer. Wikipedia and its sister
projects just switched from pure Lucene to Elasticsearch. Here is a
short summary of their reasons to prefer Elasticsearch over Solr:
https://www.mediawiki.org/wiki/Search#Solr_vs_Elasticsearch
I would add that replication and scaling is easier with Elasticsearch.
For your hand-coded website, this could all be overkill. Ease of
setup, integration, and maintainance might outweight scalability for
you. So in addition to Elasticsearch, I would recommend looking at
Omega, which is based on Xapian <http://xapian.org/docs/omega/>,
Sphider (if you can run PHP and MySQL), or Yacy (if you can run Java).
For really small websites there are client-side jQuery search plugins.
Web Content Management Systems such as Drupal come with a built-in
search facility. Whatever prevented you from using a CMS might also
prevent you from setting up your own site search service I'm afraid.
I hope this helps.
Christian
--
Christian Pietsch · http://purl.org/net/pietsch
LibTec · Library Technology and Knowledge Management
Bielefeld University Library, Bielefeld, Germany
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
------------------------------
Date: Wed, 14 May 2014 07:57:20 -0400
From: Jason Kucsma <jkucsma at METRO.ORG>
Subject: Job Posting: Empire State Digital Network Technology Specialist
Located in New York City, the Metropolitan New York Library Council (METRO)
is a nonprofit member services organization serving more than 260
libraries, archives, museums, and cultural heritage nonprofits in New York
City and Westchester County. METRO has an almost 50-year tradition of
providing a range of programs and services to its members, including
grants, consultative and digital services, collaborative initiatives, and
professional development and training. We are seeking an enthusiastic,
dedicated individual to manage Empire State Digital Network (ESDN), a
statewide initiative to deliver content from New York’s cultural heritage
institutions to the Digital Public Library of America (DPLA).
*POSITION OVERVIEW:*
The ESDN Technology Specialist is a full-time, newly created position for
one year with the possibility of extension. This position is open to
early-career and experienced information professionals. Candidates should
be enthusiastic about supporting expanded access to digital collections
from New York libraries, archives and cultural heritage institutions via
the DPLA.
In coordination with the ESDN Manager and Metadata Specialist, the
Technology Specialist will participate in the implementation of key
technologies to meet ESDN program objectives. This person will focus on
developing the technical processes necessary to accomplish required data
manipulation and transformations. The Technology Specialist will configure
open-source tools and will develop custom programming solutions to
streamline project workflows as needed. Creativity, flexibility and the
ability to experiment and invent will be essential.
*IF YOU FILL THIS POSITION, YOU WILL BE ASKED TO:*
- Work as a flexible member of a small, highly-collaborative team.
- Configure REPOX and other ingest, harvest, and data normalization
tools for ESDN project needs.
- Work closely with ESDN Manager and Metadata Specialist to write and
apply XSLT data transformations according to defined project specifications.
- Select, configure and manage technology solutions for data
normalization tasks as needed.
- Provide programming and technical support for all components of
multiple ESDN workflows.
- Envision, develop and implement custom programming solutions to
streamline data ingest, remediation, and transformation processes as needed.
- Work closely with METRO Digital Services Manager to provide technical
support for METRO administered collections in Fedora/Islandora as needed.
*THE IDEAL CANDIDATE WILL HAVE:*
- Master’s Degree in Library and Information Science or a related degree.
- Experience working in a library, archive or cultural heritage
organization, or affiliated educational, non-profit, or professional
organization.
- Experience with standard software and web application development
tools and programming languages and technologies including JavaScript,
Python, JSON, and Ruby.
- Strong working knowledge of XML, XPath/XQuery, and XSLT required.
- Knowledge of library practices and data formats including XML,
OAI-PMH, MODS, MARC, and Dublin Core.
- Experience installing and configuring open-source software tools
relevant to LAMs digital collections and specifically to databases and
repositories.
- Ability to administer PHP/MySQL applications.
- Experience working with version control systems.
- Excellent communication skills and the ability to work well in a
highly collaborative, team-oriented environment.
- Ability to work independently with minimal supervision.
*POSITION DETAILS:*
This position will remain open until filled. The ESDN Technology Specialist
works in collaboration with the ESDN Manager and Technology Specialist. The
salary range is $60,000-70,000, commensurate with skills and experience.
METRO provides excellent benefits, pension, and leave package. Position may
entail four-day, 35-hour workweek. METRO’s offices are located at 57 E.
11th Street in New York City. Remote employment within the mid-Atlantic
region will be considered.
*APPLICATION DETAILS:*
The application period ends May 30th, 2014. Please send a resume or cv and
a cover letter as a PDF attachment to info at metro.org with “ESDN Technology
Specialist” in the subject line. No phone calls please.
View the posting on our website:
http://metro.org/jobs/empire-state-digital-network-technology-specialist/
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
------------------------------
Date: Wed, 14 May 2014 14:21:49 -0300
From: Lise Brin <brinmobile at GMAIL.COM>
Subject: Link Resolver icon wording
Some of our faculty members have reported that they dislike the wording we
have on our Link Resolver icon: "Get it @ X" (X stands for Xavier, short
for our institutional name). To them, seeing "Get it" below an article
conveys that they *will* be able to access this article, not that they will
have to *check* the resolver to see whether we have a subscription that
includes it.
I am therefore looking at alternate wordings. I see that quite a few
institutions use "Find It" (which doesn't seem like much of an improvement)
while others are using "Check for full text" which seems better, but is
rather long, especially since most vendors only allow space for a *tiny*
icon.
Have any of you made changes along these lines? Did you do any user testing
to assess how different wordings were being understood, and if so, did you
learn anything useful?
All the best,
Lise Brin
Emerging Services & Outreach Librarian
St. Francis Xavier University
Antigonish, NS
CANADA
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
------------------------------
Date: Wed, 14 May 2014 11:52:51 -0600
From: "Sergy, Lauren" <lsergy at THEALBERTALIBRARY.AB.CA>
Subject: Netspeed 2014: Registration now open!
The Alberta Library invites you to register for
*Netspeed 2014: The Human Side of Technology*
*October 16 and 17 at the Edmonton Marriott at River Cree Resort*
*Netspeed* is a leading library technology conference that connects
librarians, library technicians, and information technology staff from
public, academic, government, and special libraries from Western Canada and
beyond. Technology is embedded in virtually every aspect of the library
experience and the Netspeed conference addresses this convergence of people
and technology.
We offer learning experiences that include lectures, discussion, technology
demonstrations, and forums for conversation. This year’s program is packed
with high-quality, timely sessions on topics that include makerspaces,
intellectual property, social media, digitization, and more. Presenters
are coming from across Canada to present ideas, research, technologies, and
innovative projects impacting public, post-secondary, and special
libraries.
We are excited to introduce *NExpo*, our new exhibitors’ showcase. NExpo
is a venue to meet with your current service providers and meet new
potential partners. Come learn about products, services, and innovations
and take the opportunity to have quality meetings with your library’s
vendors in one convenient location. The *NExpo Stage *provides an
additional learning stream, where exhibitors can educate delegates about
improvements, developments, and new offerings.
Netspeed delivers a high-impact experience for many levels of library
staff, from decision makers to front-line implementers. Register today!
Rates:
Early Bird (available until September 15): $252
Regular Rate (after September 15): $362
*Register forNetspeed online
<https://www.signup4.net/Public/ap.aspx?EID=NETS10E&TID=swAoRy4kWCEPkZwiBBH8VA%3d%3d>*
*Visit theNetspeed website
<http://www.thealbertalibrary.ab.ca/netspeed/>*to view additional
information, including the full program and
accommodation details.
*Book your room at the Edmonton Marriott at River Cree Resort
<http://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=Netspeed%202014%20Conference%5EYEGMC%60NETNETA%60165.00%60CAD%60true%6010/15/14%6010/17/14%6009/15/14&app=resvlink&stop_mobi=yes>*at
the special Netspeed Conference Rate.
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
------------------------------
Date: Wed, 14 May 2014 18:19:42 +0000
From: "Elish, Barbara" <BElish at WINTHROP.ORG>
Subject: Re: Link Resolver icon wording
We have only the name of our institution on our button. No one has complained.
Barbara
Barbara Elish, MSLS, AHIP
Director, Hollis Health Sciences Library
Winthrop-University Hospital
259 First Street
Mineola, NY 11501
P: 516-663-2783
F: 516-663-8171
www.winthrop.org/library<http://www.winthrop.org/library<http://www.winthrop.org/library<http://www.winthrop.org/library>>
From: Web technologies in libraries [mailto:WEB4LIB at LISTSERV.ND.EDU] On Behalf Of Lise Brin
Sent: Wednesday, May 14, 2014 1:22 PM
To: WEB4LIB at LISTSERV.ND.EDU
Subject: [WEB4LIB] Link Resolver icon wording
Some of our faculty members have reported that they dislike the wording we have on our Link Resolver icon: "Get it @ X" (X stands for Xavier, short for our institutional name). To them, seeing "Get it" below an article conveys that they *will* be able to access this article, not that they will have to *check* the resolver to see whether we have a subscription that includes it.
I am therefore looking at alternate wordings. I see that quite a few institutions use "Find It" (which doesn't seem like much of an improvement) while others are using "Check for full text" which seems better, but is rather long, especially since most vendors only allow space for a *tiny* icon.
Have any of you made changes along these lines? Did you do any user testing to assess how different wordings were being understood, and if so, did you learn anything useful?
All the best,
Lise Brin
Emerging Services & Outreach Librarian
St. Francis Xavier University
Antigonish, NS
CANADA
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
-----
The information contained in this e-mail is confidential, privileged, or
otherwise protected from disclosure. It is intended only for the use of
the authorized individual as indicated in the e-mail. Any unauthorized
disclosure, copying, distribution or taking of any action based on the
contents of this material is strictly prohibited.
If you have received this e-mail in error, please delete it immediately.
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: ht
------------------------------
Date: Wed, 14 May 2014 18:32:53 +0000
From: "Blakiston, Rebecca L - (blakisto)" <blakisto at EMAIL.ARIZONA.EDU>
Subject: Re: Link Resolver icon wording
I sympathize with this struggle and hope someone responds with a good answer and some usability testing studies! I have seen in observation of users that it is often unclear where to go to find the full text if there isn’t a direct link. In some cases, users will click on the “library catalog” link rather than the link resolver, usually because that’s the first link.
Here, we used to have an icon that said “Article Linker” and this didn’t resonate well. Then we changed it to say, “Get Article,” which is a bit better but still not that intuitive, especially since it doesn’t always get you the article, and because it’s not even always an article! (Ebooks, for example). In both cases we tried to make it look like a button – a clear call to action. This hasn’t seemed to help much.
What we’re going to try next is “Check for full text,” as mentioned below. From a usability standpoint, I’d venture to guess this is the best option – it’s much clearer what will actually happen when you select that link. Ideally, your link resolver page then matches the same language so the user knows they are in the right place (this is another usability problem I’ve seen – some link resolver pages are problematic & once you’re there it’s difficult to know what to do next).
Haven’t done any real testing of this, though. Sounds like it would be a great candidate for multivariate testing if someone could figure out how to run that sort of test and get meaningful results…
Rebecca
Rebecca Blakiston
Website Product Manager
User Experience and Engagement Librarian
University of Arizona Libraries
@blakistonr
From: Web technologies in libraries [mailto:WEB4LIB at LISTSERV.ND.EDU] On Behalf Of Lise Brin
Sent: Wednesday, May 14, 2014 10:22 AM
To: WEB4LIB at LISTSERV.ND.EDU
Subject: [WEB4LIB] Link Resolver icon wording
Some of our faculty members have reported that they dislike the wording we have on our Link Resolver icon: "Get it @ X" (X stands for Xavier, short for our institutional name). To them, seeing "Get it" below an article conveys that they *will* be able to access this article, not that they will have to *check* the resolver to see whether we have a subscription that includes it.
I am therefore looking at alternate wordings. I see that quite a few institutions use "Find It" (which doesn't seem like much of an improvement) while others are using "Check for full text" which seems better, but is rather long, especially since most vendors only allow space for a *tiny* icon.
Have any of you made changes along these lines? Did you do any user testing to assess how different wordings were being understood, and if so, did you learn anything useful?
All the best,
Lise Brin
Emerging Services & Outreach Librarian
St. Francis Xavier University
Antigonish, NS
CANADA
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Sit
------------------------------
Date: Wed, 14 May 2014 19:42:18 +0000
From: "Braun Hamilton, Michael R" <Michael.BraunHamilton at CCV.EDU>
Subject: Re: Link Resolver icon wording
We have a lot of EBSCO databases, and since the link resolver button displays where EBSCO otherwise displays links to Full Text, I recently replaced our old “Find it @...” link resolver button in these databases with one that says “Find Full Text” and is styled to look like EBSCO’s Full Text links.
Here’s a screenshot showing 2 results – one where EBSCO has the full text available and one that links out to the link resolver - https://dl.dropboxusercontent.com/u/772340/EBSCO_icons.png
With the caveat that I have neither done any usability testing nor gotten any feedback from anyone since I changed it, I hope that at least it looks more obvious to click on now. (Whether students can navigate the link resolver it links out to is another story, of course.)
-Michael
___
Michael Braun Hamilton
Web Services Librarian
Hartness Library
Community College of Vermont
(802) 828-0125
michael.braunhamilton at ccv.edu<mailto:michael.braunhamilton at ccv.edu>
****************************
PRIVACY & CONFIDENTIALITY NOTICE: This message is for the designated recipient only and may contain privileged, confidential, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of an email received in error is prohibited.
From: Web technologies in libraries [mailto:WEB4LIB at listserv.nd.edu] On Behalf Of Blakiston, Rebecca L - (blakisto)
Sent: Wednesday, May 14, 2014 2:33 PM
To: WEB4LIB at listserv.nd.edu
Subject: Re: [WEB4LIB] Link Resolver icon wording
I sympathize with this struggle and hope someone responds with a good answer and some usability testing studies! I have seen in observation of users that it is often unclear where to go to find the full text if there isn’t a direct link. In some cases, users will click on the “library catalog” link rather than the link resolver, usually because that’s the first link.
Here, we used to have an icon that said “Article Linker” and this didn’t resonate well. Then we changed it to say, “Get Article,” which is a bit better but still not that intuitive, especially since it doesn’t always get you the article, and because it’s not even always an article! (Ebooks, for example). In both cases we tried to make it look like a button – a clear call to action. This hasn’t seemed to help much.
What we’re going to try next is “Check for full text,” as mentioned below. From a usability standpoint, I’d venture to guess this is the best option – it’s much clearer what will actually happen when you select that link. Ideally, your link resolver page then matches the same language so the user knows they are in the right place (this is another usability problem I’ve seen – some link resolver pages are problematic & once you’re there it’s difficult to know what to do next).
Haven’t done any real testing of this, though. Sounds like it would be a great candidate for multivariate testing if someone could figure out how to run that sort of test and get meaningful results…
Rebecca
Rebecca Blakiston
Website Product Manager
User Experience and Engagement Librarian
University of Arizona Libraries
@blakistonr
From: Web technologies in libraries [mailto:WEB4LIB at LISTSERV.ND.EDU] On Behalf Of Lise Brin
Sent: Wednesday, May 14, 2014 10:22 AM
To: WEB4LIB at LISTSERV.ND.EDU<mailto:WEB4LIB at LISTSERV.ND.EDU>
Subject: [WEB4LIB] Link Resolver icon wording
Some of our faculty members have reported that they dislike the wording we have on our Link Resolver icon: "Get it @ X" (X stands for Xavier, short for our institutional name). To them, seeing "Get it" below an article conveys that they *will* be able to access this article, not that they will have to *check* the resolver to see whether we have a subscription that includes it.
I am therefore looking at alternate wordings. I see that quite a few institutions use "Find It" (which doesn't seem like much of an improvement) while others are using "Check for full text" which seems better, but is rather long, especially since most vendors only allow space for a *tiny* icon.
Have any of you made changes along these lines? Did you do any user testing to assess how different wordings were being understood, and if so, did you learn anything useful?
All the best,
Lise Brin
Emerging Services & Outreach Librarian
St. Francis Xavier University
Antigonish, NS
CANADA
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-0
------------------------------
Date: Wed, 14 May 2014 20:47:38 +0000
From: "Salazar, Christina" <christina.salazar at CSUCI.EDU>
Subject: Re: Link Resolver icon wording
I think there’s two problems here really: one is a usability problem and the other is that link resolver/open URL is a somewhat problematic technology – it’s definitely better than nothing, but it still has lots of hiccups and not a lot of transparency.
I was thinking (because I know how tiny that icon is): “Check for it” – slightly shorter than “Check for full text” but probably less clear about what’s going on. Again, this is only based on my knowledge of how problematic labeling this service is, not on any research I’ve done around possible solutions.
Christina Salazar
Systems Librarian
John Spoor Broome Library
California State University, Channel Islands
805/437-3198
[Description: Description: CI Formal Logo_1B grad_em signature]
From: Web technologies in libraries [mailto:WEB4LIB at LISTSERV.ND.EDU] On Behalf Of Blakiston, Rebecca L - (blakisto)
Sent: Wednesday, May 14, 2014 11:33 AM
To: WEB4LIB at LISTSERV.ND.EDU
Subject: Re: [WEB4LIB] Link Resolver icon wording
I sympathize with this struggle and hope someone responds with a good answer and some usability testing studies! I have seen in observation of users that it is often unclear where to go to find the full text if there isn’t a direct link. In some cases, users will click on the “library catalog” link rather than the link resolver, usually because that’s the first link.
Here, we used to have an icon that said “Article Linker” and this didn’t resonate well. Then we changed it to say, “Get Article,” which is a bit better but still not that intuitive, especially since it doesn’t always get you the article, and because it’s not even always an article! (Ebooks, for example). In both cases we tried to make it look like a button – a clear call to action. This hasn’t seemed to help much.
What we’re going to try next is “Check for full text,” as mentioned below. From a usability standpoint, I’d venture to guess this is the best option – it’s much clearer what will actually happen when you select that link. Ideally, your link resolver page then matches the same language so the user knows they are in the right place (this is another usability problem I’ve seen – some link resolver pages are problematic & once you’re there it’s difficult to know what to do next).
Haven’t done any real testing of this, though. Sounds like it would be a great candidate for multivariate testing if someone could figure out how to run that sort of test and get meaningful results…
Rebecca
Rebecca Blakiston
Website Product Manager
User Experience and Engagement Librarian
University of Arizona Libraries
@blakistonr
From: Web technologies in libraries [mailto:WEB4LIB at LISTSERV.ND.EDU]<mailto:[mailto:WEB4LIB at LISTSERV.ND.EDU]> On Behalf Of Lise Brin
Sent: Wednesday, May 14, 2014 10:22 AM
To: WEB4LIB at LISTSERV.ND.EDU<mailto:WEB4LIB at LISTSERV.ND.EDU>
Subject: [WEB4LIB] Link Resolver icon wording
Some of our faculty members have reported that they dislike the wording we have on our Link Resolver icon: "Get it @ X" (X stands for Xavier, short for our institutional name). To them, seeing "Get it" below an article conveys that they *will* be able to access this article, not that they will have to *check* the resolver to see whether we have a subscription that includes it.
I am therefore looking at alternate wordings. I see that quite a few institutions use "Find It" (which doesn't seem like much of an improvement) while others are using "Check for full text" which seems better, but is rather long, especially since most vendors only allow space for a *tiny* icon.
Have any of you made changes along these lines? Did you do any user testing to assess how different wordings were being understood, and if so, did you learn anything useful?
All the best,
Lise Brin
Emerging Services & Outreach Librarian
St. Francis Xavier University
Antigonish, NS
CANADA
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-1
------------------------------
End of WEB4LIB Digest - 13 May 2014 to 14 May 2014 (#2014-109)
**************************************************************
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2014-05-14
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.nd.edu/pipermail/web4lib/attachments/20140515/9fc951ee/attachment.htm>
More information about the Web4lib
mailing list