@lists.sourceforge.net
Subject: Re: [Dspace-tech] Embargo and OAI interface
Tom,
I looked at this very closely and realized that the code as it stands would not
be easy to change to support this, and that an ugly hack would be needed if we
wanted it done. I am actually on travel for a week and would still really
On Fri, 6 May 2011, Richard Rodgers wrote:
The embargo system is designed to protect bitstreams, not metadata.
While it certainly would be possible to alter OAI or other code to check
for embargo dates, this has not been done to the best of my knowledge. I
am curious why, given that the
when browsing. Is that the
case? Could you share the code that does that?
Thank you!
Jose
From: Tom De Mulder [td...@cam.ac.uk]
Sent: Tuesday, May 10, 2011 5:38 AM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Embargo and OAI
On Tue, 10 May 2011, Blanco, Jose wrote:
I have been working lately on hiding items from search results that have
READ metadata restrictions for certain users. So for example, item1 is
restricted to only one particular user, if that user is logged-in and
searches for a string in that item,
of this. That was not so ugly.
-Jose
From: Tom De Mulder [td...@cam.ac.uk]
Sent: Tuesday, May 10, 2011 8:40 AM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Embargo and OAI interface
On Tue, 10 May 2011, Blanco, Jose wrote:
I have been working
of this. That was not so ugly.
-Jose
From: Tom De Mulder [td...@cam.ac.uk]
Sent: Tuesday, May 10, 2011 8:40 AM
To: dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Embargo and OAI interface
On Tue, 10 May 2011, Blanco, Jose wrote
On May 6, 2011, at 8:03 AM, Tonny Hjelmberg Laursen wrote:
We are in the middle of doing a implementation of Primo from Exlibris
(integrated search - http://www.exlibrisgroup.com/category/PrimoOverview).
Primo can harvest Dspace, but we don't want all the items where the full text
is
On May 10, 2011, at 2:38 AM, Tom De Mulder wrote:
On Fri, 6 May 2011, Richard Rodgers wrote:
I'd like to ask for a flag in the dspace config file to let dark items be
properly dark (including embargoed items). This applies to search results
as well as (possibly even more so) to
On May 10, 2011, at 5:28 AM, Blanco, Jose wrote:
Tom,
I have been working lately on hiding items from search results that have READ
metadata restrictions for certain users. So for example, item1 is restricted
to only one particular user, if that user is logged-in and searches for a
I sent the mail below a week ago to the tech-list but I didn't receive any
responds on it.
I really need some help on this, so if anyone knows a fix…..
Thanks,
Tonny
Fra: tt tt thl@cbs.dkmailto:thl@cbs.dk
Dato: Thu, 28 Apr 2011 08:12:45 +0200
Til:
Hi Tonny:
The embargo system is designed to protect bitstreams, not metadata. While it
certainly would be possible to alter OAI or other code to check for embargo
dates, this has not been done to the best of my knowledge. I am curious why,
given that the content will be inaccessible, is it
We are in the middle of doing a implementation of Primo from Exlibris
(integrated search - http://www.exlibrisgroup.com/category/PrimoOverview).
Primo can harvest Dspace, but we don't want all the items where the full text
is not public accessibly in Primo. We can't configure Primo not to
12 matches
Mail list logo
