ilto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Kevin Ford
> Sent: Tuesday, March 29, 2016 10:45 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Deduping linked data in search - was RE:
> [CODE4LIB] Structured Data Markup on library web sites
>
> It's probably not s
] Deduping linked data in search - was RE: [CODE4LIB]
Structured Data Markup on library web sites
It's probably not safe to say that "all search is local" but there is most
certainly a strong local component considered for every search.
For me, every hit on the first page of Google&#
Hi Cindy,
Deduping can happen in any number of ways, but making use of shared
identifiers is the preferred way to address this issue. You could adopt
a shared identifier or you can an indicate that your Thing is the same
as a this other Thing. In schema.org's vocabulary, you'd use
schema:sa
It's probably not safe to say that "all search is local" but there is
most certainly a strong local component considered for every search.
For me, every hit on the first page of Google's results for a search for
"ice cream parlor" is related to Chicago, which is where I executed the
search. A
An off-the-cuff response: I've heard it suggested in talks about Bibframe
that just as Google tailors your results based on location (i.e. if I put
in "pizza," I'll get pizza places in South Bend, as well as pizza recipes
and whatnot), they'd tailor your library results based on location. So if I
w
Forgive me if I'm confusing schema.org and Bibframe, but I wonder how Google is
going to dedupe all the sources of a given document/material when many
libraries have their holdings in bibframe? These sample searches made me
wonder about that again. has this been discussed?
Cindy Harper
char..
