[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] Re: eprints DRIVER compliance



Il 12/03/2012 17:49, Tim Brody ha scritto:
> On Mon, 2012-03-12 at 17:26 +0100, Yuri wrote:
>> Il 12/03/2012 14:31, Tim Brody ha scritto:
>>> Hi,
>>>
>>> DRIVER compliance will depend on your local configuration.
>>    is there any guide/info about this?
> Perhaps this, http://files.eprints.org/649/.
> http://www.openaire.eu/en/about-openaire/publications-presentations/presentations/doc_details/342-how-to-make-your-repository-openaire-compliant-eprints
>
> (OpenAIRE is the successor to DRIVER?)
>
> The DRIVER set was added 3 years ago:
> http://trac.eprints.org/eprints/ticket/3271
> (But is a config option, so you may need to copy from the defaultcfg)

http://trac.eprints.org/eprints/attachment/ticket/3271/driver_set_patch.diff

I've found this in oai2 part of the patch:

my( $info ) = grep { $_->{spec} = $args->{set} } @{$custom_sets||[]};

Obviously it should be:

my( $info ) = grep { $_->{spec} eq $args->{set} } @{$custom_sets||[]};

:))

This because maybe someone has read this email to add Driver support. 
The code has been fixed later in Eprints code. The bug hit when you've 
more than 1 custom_sets.