LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2012

CODE4LIB February 2012

Subject:

"How to get from what you've found to access":

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 23 Feb 2012 15:44:25 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (192 lines)

Changing the subject line, cause this is an interesting topic on it's own.

On 2/23/2012 2:45 PM, Karen Coyle wrote:
> This links to thoughts I've had about linked data and finding a way to 
> use library holdings over the Web. Obviously, bibliographic data alone 
> is a full service: people want to get the stuff once they've found out 
> that such stuff exists. So how do we get users from the retrieval of a 
> bibliographic record to a place where they have access to the stuff?

I think this is exactly right as a problem libraries (which provide 
various methods of access to items people may find out about elsewhere) 
should be focusing on more than they do.

I mentioned in a previous reply that this is in fact exactly the mission 
of Umlaut. A better direct link for people interested in Umlaut than the 
one I pasted before:

https://github.com/team-umlaut/umlaut/wiki

It's definitely a work in progress, like I said, I'm not saying Umlaut 
"solves" this problem.  But the thinking behind Umlaut is that you've 
got to have software which can take a machine-described "thing someone 
is interested in" and tell them everything that your institution (which 
they presumably are affiliated with) can do for them for that item. 
That's exactly what Umlaut tries to do, providing a platform that you 
can use to piece together information from your various silo'd knowledge 
bases and third party resources, etc.  And including ALL your stuff, 
monographs etc., not just journal articles like typical "link resolvers".

After that (and even that is hard), you've got to figure out how to 
_get_ people from "where they've found out about something" to your 
service for telling them what they can do with it via your institution. 
That's not an entirely solved problem. One reason Umlaut speaks 
"OpenURL" is there is already a substantial infrastructure of things in 
the academic market that can express a "thing someone knows about" in 
OpenURL and send it to your local software (including Google Scholar).  
But it's still not enough.

Ultimately some kind of LibX approach is probably required -- whether a 
browser plugin, or a javascript bookmarklet (same sort of thing, 
different technology), a way to get someone from a third party to your 
'list of services', even when that third party is completely 
uninterested in helping them get there (Amazon doesn't particularly want 
to help someone who starts at Amazon get somewhere _else_ to buy the 
book! Others may be less hostile, but just not all that interested in 
spending any energy on it).

Jonathan
> I see two options: the WorldCat model, where people get sent to a 
> central database where they input their zip code, or a URL-like model 
> where they get a link on retrievals that has knowledge about their 
> preferred institution and access.
>
> I have no idea if the latter is feasible on a true "web scale," but it 
> would be my ideal solution. We know that search engines keep track of 
> your location and tailor retrievals based on that. Could libraries get 
> into that loop?
>
> kc
>
> On 2/23/12 11:35 AM, Eoghan Ó Carragáin wrote:
>> That's true, but since Blacklight/Vufind often sit over
>> digital/institutional repositories as well as ILS systems&  subscription
>> resources, at least some public domain content gets found that otherwise
>> wouldn't be. As you said, even if the item isn't available digitally, 
>> for
>> Special Collections libraries unique materials are exposed to potential
>> researchers who'd never have known about them.
>> Eoghan
>>
>> On 23 February 2012 19:25, Sean Hannan<[log in to unmask]>  wrote:
>>
>>> It's hard to say. Going off of the numbers that I have, I'd say that 
>>> they
>>> do
>>> find what they are looking for, but they unless they are a JHU 
>>> affiliate,
>>> they are unable to access it.
>>>
>>> Our bounce rate for Google searches is 76%.  Which is not 
>>> necessarily bad,
>>> because we put a lot of information on our item record pages--we 
>>> don't make
>>> you dig for anything.
>>>
>>> On the other hand, 9% of visits coming to us through Google searches 
>>> are
>>> return visits. To me, that says that the other 91% are not JHU 
>>> affiliates,
>>> and that's 91% of Google searchers that won't have access to materials.
>>>
>>> I know from monitoring our feedback form, we have gotten in increase in
>>> requests from far flung places for access to things we have in special
>>> collections from non-affiliates.
>>>
>>> So, we get lots of exposure via searches, but due to the nature of how
>>> libraries work with subscriptions, licensing, membership and such, 
>>> we close
>>> lots of doors once they get there.
>>>
>>> -Sean
>>>
>>> On 2/23/12 1:55 PM, "Schneider, Wayne"<[log in to unmask]>  wrote:
>>>
>>>> This is really interesting. Do you have evidence (anecdotally or
>>>> otherwise) that the people coming to you via search engines found what
>>>> they were looking for? Sorry, I don't know exactly how to phrase this.
>>>> To put it another way - are your patrons finding you this way?
>>>>
>>>> wayne
>>>>
>>>> -----Original Message-----
>>>> From: Code for Libraries [mailto:[log in to unmask]] On 
>>>> Behalf Of
>>>> Sean Hannan
>>>> Sent: Thursday, February 23, 2012 12:37 PM
>>>> To: [log in to unmask]
>>>> Subject: Re: [CODE4LIB] Local catalog records and Google, Bing, Yahoo!
>>>>
>>>> Our Blacklight-powered catalog (https://catalyst.library.jhu.edu/) 
>>>> comes
>>>> up a lot in google search results (try gil scott heron circle of 
>>>> stone).
>>>>
>>>> Some numbers:
>>>>
>>>> 59% of our total catalog traffic comes from google searches 0.04% 
>>>> of our
>>>> total catalog traffic comes from yahoo searches 0.03% of our total
>>>> catalog traffic comes from bing searches
>>>>
>>>> For context, 32.96% of our total catalog traffic is direct traffic and
>>>> referrals from all of the library websites combined.
>>>>
>>>> Anecdotally, it would appear that bing (and bing-using yahoo) seem to
>>>> drastically play down catalog records in their results. We're not 
>>>> doing
>>>> anything to favor a particular search engine; we have a completely 
>>>> open
>>>> robots.txt file.
>>>>
>>>> Google regularly indexes our catalog. Every couple days or so. I 
>>>> haven't
>>>> checked in awhile.
>>>>
>>>> We're not doing any fancy SEO here (though, I'd like to implement some
>>>> of the microdata stuff).  It's just a function of how the site 
>>>> works. We
>>>> link a lot of our catalog results to further searches (clicking on an
>>>> author name takes you to an author search with that name, etc).  
>>>> Google
>>>> *loves* that type of intertextual website linking (see also: 
>>>> Wikipedia).
>>>> We also have stable URLs. Search URLs will always return searches with
>>>> those parameters, item URLs are based on an ID that does not change.
>>>>
>>>> All of that good stuff doesn't help us with bing, though. ...But 
>>>> I'm not
>>>> really concerned with remedying that, right this moment.
>>>>
>>>> -Sean
>>>>
>>>> On 2/23/12 12:37 PM, "[log in to unmask]"
>>>> <[log in to unmask]>
>>>> wrote:
>>>>
>>>>> First of all, I'm going to say I know little in this area. I've done
>>>>> some preliminary research about search indexing (Google's) and
>>>>> investigated a few OPAC robot.txt files. Now to my questions:
>>>>>
>>>>>     - Can someone explain to me or point me to research as to why 
>>>>> local
>>>>>     library catalog records do not show up in Google, Bing, or Yahoo!
>>>> search
>>>>>     results?
>>>>>     - Is there a general prohibition by libraries for search 
>>>>> engines to
>>>>>     crawl their public records?
>>>>>     - Do the search engines not index these records actively?
>>>>>     - Is it a matter of SEO/promoted results?
>>>>>     - Is it because some systems don't mint URLs for each record?
>>>>>
>>>>> I haven't seen a lot of discussion about this recently and I know
>>>>> Jason Ranallo has done a lot of work in this area and gave a great
>>>>> talk at code4lib Seattle on microdata/Schema.org, so I figured this
>>>>> could be part of that continuing conversation.
>>>>>
>>>>> I look forward to being educated by you all,
>>>>>
>>>>> Tod
>>>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

November 2024
October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager