On Thu, Feb 20, 2014 at 11:57 PM, Carlos Walter Blandon Alvarez
wrote:
> I applied this patch in Dspace 4.0 and updated with
In my environment, the patch worked with DSpace 4.0. I did some wider
testing here [1].
> Is necessary to do fresh install?
No, but it is necessary to call "[dspace]/bin/
.
Para: esa
CC: dspace-tech
Asunto: Re: [Dspace-tech] OAI validation for Dspace 3.0 failure
Hello everyone who has been affected by this OAI timezone issue. There is now a
patch that fixes this:
https://github.com/DSpace/DSpace/pull/408
In order to help get the fix into DSpace 4.0, we'd li
Hello everyone who has been affected by this OAI timezone issue. There
is now a patch that fixes this:
https://github.com/DSpace/DSpace/pull/408
In order to help get the fix into DSpace 4.0, we'd like to ask you to
verify that it fixes your problem. The sooner you report back the
better as 4.0 wi
Hi,
I have same problem and you're right João, the problem i think is timezone.
when i validate my oai server :
http://repository.widyatama.ac.id:8080/oai/request?verb=ListRecords&from=2013-05-29T15:20:48Z&until=2013-05-29T15:20:48Z&metadataPrefix=oai_dc
i got error, its say 'no record match'. T
Hi Christos,
could you please provide the server timezone? Is it GMT+4?
Seems like it is a date parsing (timezone related) issue.
On 8 January 2013 19:23, Christos Rodosthenous <
christos.rodosthen...@ouc.ac.cy> wrote:
> Hi everyone,
>
> ** **
>
> I upgraded my Dspace 1.7.2 to 1.8 and fina
Hi everyone,
I upgraded my Dspace 1.7.2 to 1.8 and finally to 3.0.
I tried to validate Dspace repository through :
1) http://www.openarchives.org/Register/ValidateSite and
2) http://validator.oaipmh.com/
The first validator returns an error for:
Checking ListRecords response
Request:
6 matches
Mail list logo