Candidate Standard

Skip to end of metadata
Go to start of metadata

7.6.1 Purpose

This command can be used by a Release Distributor to signal to the Metadata Provider, that the Release Distributor has ingested, but not necessarily processed a specific metadata item, including all referenced documents.

It therefore signals to the Metadata Provider, that the Release Distributor no longer needs to receive web service calls with respect to the said metadata item from the Metadata Provider. After receiving this call, a Metadata Provider is free to remove the associated entry from its Atom feed.

If, after removing the item from the queue and removing the associated entry from its Atom feed, the Metadata Provider is updating the information about the item again, the metadata should – subject to its bilateral agreement with the Release Distributor – create a new Atom feed/entry for the same entity.

The syntax for this call is not prescribed except.

7.6.2 Syntax of Reply

The web server shall return one of the following standard HTTP status codes with their standard HTTP response code semantics:

  • 204 (The server successfully processed the request but is not returning any content);
  • 208 (Already reported);
  • 400 (Bad Request) – which in this case means that the URL does not lead to a valid metadata message (any more);
  • 401 (Unauthorised);
  • 404 (Not found);
  • 500 (Internal server error); and
  • 503 (Service unavailable due to a temporary overloading or maintenance of the server).

Other standard HTTP status codes may be used on bilateral agreement between the Metadata Provider and the Release Distributor.

 

  • No labels