I just tried putting this:
<Filter id="defaultFilter">
<Definition>
<Or>
<LeftCondition>
<Custom ref="itemAccessCondition"/>
</LeftCondition>
<RightCondition>
<Custom ref="itemWithdrawnCondition"/>
</RightCondition>
</Or>
</Definition>
</Filter>
in xoai.xml
but when I do oai/request?verb=Identify
I get:
2016-01-19 15:14:05,433 ERROR org.dspace.xoai.app.BasicConfiguration @ Not
able to start XOAI normal cache service.
org.dspace.xoai.services.api.config.XOAIManagerResolverException:
com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: Unexpected
element LeftCondition
On Tue, Jan 19, 2016 at 4:04 AM, Claudia Jürgen <
claudia.juer...@tu-dortmund.de> wrote:
> Hello Jose,
>
> I think the harvest.includedrestricted.oai dspace.cfg parameter is no
> longer valid since the xoai is in use.
> You can achieve it with xoai.xml setting. The default filter applied to
> the default context:
>
> <!-- Default filter for records returned by OAI-PMH.
> By default, return an Item record:
> * If it is publicly accessible
> * OR it has been withdrawn (in order to display a
> tombstone record).
> This filter is used by the default context ([oai]/request).
> -->
> <Filter id="defaultFilter">
> <Definition>
> <Or>
> <LeftCondition>
> <Custom ref="itemAccessCondition"/>
> </LeftCondition>
> <RightCondition>
> <Custom ref="itemWithdrawnCondition"/>
> </RightCondition>
> </Or>
> </Definition>
> </Filter>
>
> already contains an itemAccessCondition, which is based afair on the
> DEFAULT_ITEM_READ and not on the acutal rights.
>
> If you are using 5.1 and running
> [dspace]/bin/dspace oai import -c
> you might just be stuck with this error
> https://jira.duraspace.org/browse/DS-2543
> which was resolved in 5.3.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
>
> Am 18.01.2016 um 18:40 schrieb Jose Blanco:
>
>> Going to re-post this question.
>>
>> -Jose
>>
>> On Wed, Jan 6, 2016 at 4:11 PM, Jose Blanco <blan...@umich.edu> wrote:
>>
>> I tried it on 5.1. I had an item that was completely restricted to a
>>> group that was not Anonymous and I did:
>>>
>>> ./dspace oai -c import
>>>
>>> And the restricted item showed up.
>>>
>>> Do I need to make any changes to this file:
>>>
>>>
>>>
>>> https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/oai/xoai.xml#L51
>>>
>>> Or should it just work by default.
>>>
>>> Thank you!
>>>
>>> On Thu, Dec 17, 2015 at 10:08 AM, helix84 <heli...@centrum.sk> wrote:
>>>
>>> On Tue, Dec 15, 2015 at 5:10 PM, Jose Blanco <blan...@umich.edu> wrote:
>>>>
>>>> harvest.includerestricted.oai = false
>>>>>
>>>>> I can't find where in the code it's used.
>>>>>
>>>>> I couldn't find any uses, either.
>>>> We'll probably have to do a review of configuration properties for
>>>> DSpace
>>>> 6, so I expect we'll deal with it there.
>>>>
>>>>
>>>> Is there any documentation on how to have oai not provide restricted
>>>>> items?
>>>>>
>>>>> Since DSpace 5.0, that should be the case by default (DS-1856). If it
>>>> isn't so, please, reopen that bug or file a new one.
>>>>
>>>> https://jira.duraspace.org/browse/DS-1856
>>>>
>>>> Slightly related:
>>>>
>>>> https://jira.duraspace.org/browse/DS-950
>>>>
>>>>
>>>> Regards,
>>>> ~~helix84
>>>>
>>>> Compulsory reading: DSpace Mailing List Etiquette
>>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups
>>>> "DSpace Technical Support" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an
>>>> email to dspace-tech+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to dspace-tech@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>>>
> --
> Claudia Juergen
> Eldorado
>
> Technische Universität Dortmund
> Universitätsbibliothek
> Vogelpothsweg 76
> 44227 Dortmund
>
> Tel.: +49 231-755 40 43
> Fax: +49 231-755 40 32
> claudia.juer...@tu-dortmund.de
> www.ub.tu-dortmund.de
>
> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
> und vernichten Sie diese Mail. Vielen Dank.
> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
> solchen Schriftstücks per Telefax erfolgen.
>
> Important note: The information included in this e-mail is confidential.
> It is solely intended for the recipient. If you are not the intended
> recipient of this e-mail please contact the sender and delete this message.
> Thank you. Without prejudice of e-mail correspondence, our statements are
> only legally binding when they are made in the conventional written form
> (with personal signature) or when such documents are sent by fax.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
