> But we do encourage (promote) an interface that forces
> off-campus authentication to our Summon instance.
With an explanation that it's because of pirates! :-)
https://auth.lib.unc.edu/ezproxy_auth.php?url=http://unc.summon.serialssolutions.com/search?s.q=
> And one we would need to revisit i
At MIchigan, we direct users to an interface within our library site. Over
the last week, a bit more than 28% of searches against the Summon service
were from on-campus (hardwired) computers. An additional 25% of searches
were conducted from authenticated campus wireless networks. So slightly
more
We at GALILEO have thought about this. We authenticate everyone. If
they're on campus it's by IP, if not, by password. So everyone sees
everything. This also lets us define which EDS profile to direct the
user to.
--
Brad
On 10/24/12, Jonathan Rochkind wrote:
> On 10/24/2012 2:52 PM, Joe H
On Oct 25, 2012, at 6:46 AM, Gary McGath wrote:
> On 10/24/12 8:58 PM, Ross Singer wrote:
>> On Oct 24, 2012, at 6:06 PM, Gary McGath wrote:
>>> On 10/24/12 4:00 PM, Ross Singer wrote:
On Oct 24, 2012, at 3:48 PM, Gary McGath wrote:
Also, why wouldn't your AJAX-enabled app be prepared
On 10/24/12 8:58 PM, Ross Singer wrote:
> On Oct 24, 2012, at 6:06 PM, Gary McGath wrote:
>
>> On 10/24/12 4:00 PM, Ross Singer wrote:
>>> On Oct 24, 2012, at 3:48 PM, Gary McGath wrote:
>>>
With AJAX, a resource can be brought up by refreshing part of an
existing page rather than as a
Hi Jonathan,
My library colleagues consider this to be an very important issue. For Primo, users must be authenticated by login or IP address for Web of Science results to be included from Primo Central, and they must be logged in for EBSCO results to be included (i.e. even on campus.) The Web of
_
>From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of David
>Friggens [frigg...@waikato.ac.nz]
>Sent: Wednesday, October 24, 2012 9:15 PM
>To: CODE4LIB@LISTSERV.ND.EDU
>Subject: Re: [CODE4LIB] Q: "Discovery" products and authentication (esp
>Summon)
U] on behalf of David Friggens
[frigg...@waikato.ac.nz]
Sent: Wednesday, October 24, 2012 9:15 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Q: "Discovery" products and authentication (esp Summon)
>> a) most queries come from on-campus
> Really? Are people just assum
>> a) most queries come from on-campus
> Really? Are people just assuming this, or do they actually have data? That
> would surprise me for most contemporary american places of higher education.
For the last two months, 25.4% of our Summon traffic has come from the
IP addresses we've given as "on
On Oct 24, 2012, at 6:06 PM, Gary McGath wrote:
> On 10/24/12 4:00 PM, Ross Singer wrote:
>> On Oct 24, 2012, at 3:48 PM, Gary McGath wrote:
>>
>>> With AJAX, a resource can be brought up by refreshing part of an
>>> existing page rather than as a whole new page. If the page is expecting,
>>> f
On 10/24/12 4:00 PM, Ross Singer wrote:
> On Oct 24, 2012, at 3:48 PM, Gary McGath wrote:
>
>> With AJAX, a resource can be brought up by refreshing part of an
>> existing page rather than as a whole new page. If the page is expecting,
>> for example, a JPEG image, and the request for the image i
Andrew Nagy tried to explain to me off-list what content in Summon is
'restricted', but I honestly couldn't understand his explanation, but it
didn't seem to be as simple as "A list of A&I databases", it for some
reason had something to do with full text licensing your institution had
(I know,
On 10/24/2012 5:37 PM, Godmar Back wrote:
a) most queries come from on-campus
Really? Are people just assuming this, or do they actually have data?
That would surprise me for most contemporary american places of higher
education.
But it may very well be the extra "restricted" content is no
On Wed, Oct 24, 2012 at 1:54 PM, Mark Mounts wrote:
> We have Summon at Dartmouth College. Authentication is IP based so with a
> Dartmouth IP address the user will see all our licensed content.
>
> There is also the option to see all the content Summon has beyond what we
> license by selecting th
On Wed, Oct 24, 2012 at 12:16 PM, Jonathan Rochkind wrote:
> Looking at the major 'discovery' products, Summon, Primo, EDS
>
> ...all three will provide some results to un-authenticated users (the
> general public), but have some portions of the corpus that are restricted
> and won't show up i
aries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Gary
>> McGath
>> Sent: Wednesday, October 24, 2012 2:16 PM
>> To: CODE4LIB@LISTSERV.ND.EDU
>> Subject: Re: [CODE4LIB] Q: "Discovery" products and authentication (esp
>> Summon)
>>
>> On 10
> But I think my conclusion is that few implementers have thought about
> this, and most off-campus users probably don't get restricted content.
> :) Which may be just fine -- the amount of restricted content in a given
> product is also unclear (hard to compare between products, hard to even
> kno
, October 24, 2012 2:16 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Q: "Discovery" products and authentication (esp
> Summon)
>
> On 10/24/12 2:40 PM, Jonathan Rochkind wrote:
>
>> Primo, by default, will suppress some content from end-users unless
>>
] Q: "Discovery" products and authentication (esp Summon)
On 10/24/12 2:40 PM, Jonathan Rochkind wrote:
> Primo, by default, will suppress some content from end-users unless
> they are authenticated, no? Maybe that's what "restricted search scopes"
> are? I'm
On 10/24/12 2:40 PM, Jonathan Rochkind wrote:
> Primo, by default, will suppress some content from end-users unless they
> are authenticated, no? Maybe that's what "restricted search scopes"
> are? I'm not talking about your locally indexed content, but about the
> "PrimoCentral" index of scholar
On 10/24/2012 2:52 PM, Joe Hourcle wrote:
Do they even get a message that they've been restricted?
I would think that having a message such as :
74 records not shown because you weren't authenticated
As far as I know, none of the products have the ability to tell them
_how many_ reco
On Oct 24, 2012, at 2:40 PM, Jonathan Rochkind wrote:
> On 10/24/2012 2:04 PM, Ben Florin wrote:
>> We use Primo, but we've never bothered with their restricted search scopes.
>
> Apparently the answer to my question is that nobody has thought about this
> before, heh.
>
> Primo, by default, wi
Sent: Wednesday, October 24, 2012 2:38 PM
To: Code for Libraries
Cc: Mark Mounts
Subject: Re: [CODE4LIB] Q: "Discovery" products and authentication (esp Summon)
Right, thanks, but you're missing my point/question.
A significant portion of all of our libraries use these days is by p
On 10/24/2012 2:04 PM, Ben Florin wrote:
We use Primo, but we've never bothered with their restricted search scopes.
Apparently the answer to my question is that nobody has thought about
this before, heh.
Primo, by default, will suppress some content from end-users unless they
are authentic
RV.ND.EDU] On Behalf Of Jonathan Rochkind
Sent: Wednesday, October 24, 2012 12:16 PM To:
CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Q: "Discovery" products
and authentication (esp Summon)
Looking at the major 'discovery' products, Summon, Primo, EDS
...all three will
We use Primo, but we've never bothered with their restricted search scopes.
What are the use cases for putting discovery behind authentication? We often
require users to authenticate for access, but we don't mind outsiders seeing
what we've got.
I imagine that if we did have something whose exi
collection"
Mark
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Jonathan Rochkind
Sent: Wednesday, October 24, 2012 12:16 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Q: "Discovery" products and authentication (esp Summ
Looking at the major 'discovery' products, Summon, Primo, EDS
...all three will provide some results to un-authenticated users (the
general public), but have some portions of the corpus that are
restricted and won't show up in your results unless you have an
authenticated user affiliated w
28 matches
Mail list logo
