[OAI-implementers] error reporting
Sun, 23 Jun 2002 11:44:53 +0200
>What error condition do you wish to report that is not covered
>by the existing error codes? I did not find any when writing
For example: One record in my database is wrong and I can not obtain
datestamp information for this record.
I could say "cannotDisseminateFormat" but in truth I can disseminate format,
I just cannot get datestamp.
From: Simeon Warner [mailto:firstname.lastname@example.org]
Sent: Thursday, June 20, 2002 11:16 PM
To: Irina Dijour
Subject: Re: [OAI-implementers] error reporting
What error condition do you wish to report that is not covered
by the existing error codes? I did not find any when writing
My feeling is that 503 is not to be used for errors in the
same sense as <error> replies. 503 is for cases when the
service is unavailable -- it may be used for flow control
or perhaps temporary outages such as might occur with large
On Thu, 20 Jun 2002, Irina Dijour wrote:
> I have a small suggestion concerning error reporting.
> We have several error codes in OAI 2.0 protocol ("badArgument",
> "badResumptionToke" etc).
> If I understand correctly, if none of these error codes fits for an error
> that should be reported,
> the OAI data provider should return HTTP Error code "503 Service
> 1. If the OAI data provider uses HTTP Error code 503 it cannot specify
> exactly has happened.
> And sometimes it's useful.
> 2. There are situations when the OAI Data provider wants to report a
> specific error for a specific record.
> I think that sending HTTP Error code 503 in this case is too general.
> Therefore I propose to add additional error "unspecifiedError" (as it's
> in Z39.50 protocol).
> In the "error" element content OAI data provider may specify the error.
> Irina Dijour
> Software Development
> Ex Libris ltd.
> Malha Technology Park
> Jerusalem 91481, Israel
> Tel: +972-(0)2-6798-222 ext. 142
> Fax: +972-(0)2-6798-634
> OAI-implementers mailing list