6.4 GET ERN Resource
6.4.1 Purpose
This command can be used by a DSP to request a download of resource file(s). The web service address for this call is the URL for the specific instance of the resource file(s) as previously provided in the NewReleaseMessage
.
The GET ERN Resource
call should only be used if the record company or distributor has specified an HTTP link identifying the location of the resource file(s) in the previously provided NewReleaseMessage
. Therefore, if the URI in the NewReleaseMessage
uses a scheme other than http://, https:// or another protocol as determined in the bilateral agreement between the record company or distributor and the DSP, the DSP may not be able to use the record company or distributor’s web service to obtain the relevant resource file(s) and an alternative approach will be required.
One such solution is that the record company or distributor and the DSP can use web service delivery for the communication of metadata about releases and resources as defined in this part of the ERN standard combined with communication of the resource files using cloud-based file delivery as defined in Part 3 of the ERN standard.
6.4.2 Syntax of reply
The web service shall return one of the following standard HTTP status codes with their standard HTTP response code semantics:
200 (OK);
301 (Moved permanently);
400 (Bad request);
401 (Unauthorised);
404 (Not found); and
500 (Internal server error); or
503 (Service unavailable due to a temporary overloading or maintenance of the server).
Other standard HTTP status codes may be used as determined by the bilateral agreement between the record company or distributor and the DSP.
If the status code is 200, the web service shall, as well as the status code, also return to the calling web service client a download of the relevant resource file(s).
If the status code is 301, the web service shall also return the updated URL of the location of the relevant resource file(s). If the resource file(s) as well as its URL has changed, the record company or distributor is required to add a new NewReleaseMessage
into its feed and, as a consequence, the DSP shall regard the entirety of the original NewReleaseMessage
as invalid.