Hi Jodi / Keith,
However this request returns error code=badArgument.
http://dspace.udel.edu:8080/dspace-oai/request?verb=ListIdentifiers
The 'badArgument' occurs because you need to specify which format you want
the metadata in.
So the following works:
Not really. The badArgument is valid when you don't specify a
metadataPrefix, and the noRecordsMatch error is valid when there are no
records that match the date range specified.
If you simply include a from timestamp, eg:
If there is no date range specified, all records with the specified
metadataPrefix must be returned by protocol section 2.7.1:
http://www.openarchives.org/OAI/openarchivesprotocol.html#SelectiveHarvestingandDatestamps
Harvesting is restricted to the range specified by the from and
untilarguments,
Thanks for the additional input. I turned on debug and here is what
output I am getting in the log file.
2007-06-06 14:47:48,393 INFO org.dspace.app.oai.DSpaceOAICatalog @
anonymous:no
_context:oai_request:verb=listIdentifiers,from=0001-01-01T00:00:00Z,until=-1
Hi Graham,
I in agreement that the code is working as specified. My problem occured
when I tried to register my Dspace instance with the official Open
Archives registry. The registry send a listIdentifiers request with no
from date specified. As such my dspace instance has failed to pass
On Wed, 6 Jun 2007, Jodi Schneider wrote:
PS-Keith, what happens if you change granularity?
i.e. in oaicat.properties change
AbstractCatalog.granularity=-MM-DDThh:mm:ssZ
to
AbstractCatalog.granularity=-MM-DD
Hi Jodi,
I did make the change suggested above, but the result was
Hi Keith,
Any chance you could install this patch, and try again:
http://sourceforge.net/tracker/index.php?func=detailaid=1659868group_id=19
984atid=319984
The patch gives better database debugging, as it replaces the '?' in the log
file with the actual values given. We can then see the actual
7 matches
Mail list logo
