6.3.2 File-by-File Delivery
If Metadata Provider and Release Distributor agree on a file-by-file delivery (akin to the "Release-by-Release Profile" defined in the ERN Choreography Standard for SFTP), each file containing a
MeadRequestMessage shall be named as
Identifierbeing the identifier used in the
MeadMessageto identify the entity about which the
MeadMessageprovides additional information. Should the
MeadMessagecontain more than one entity, the identifier shall be the one identifying the main entity as determined by the sender of the
YYYYMMDDhhmmssnnnbeing the date and time that the Release is placed on the SFTP server.
MEAD_0000000114819103_20190504102412000.xml is a file containing auxiliary information sent on 4th May 2019 at 10:24:12.000 for the band Marillion (who have been allocated an ISNI of 0000 0001 1481 9103).
Any additional documents referenced from the
MeadMessage shall be placed into the same folder as the
MeadMessage. It must be uploaded to the SFTP server before the
MeadMessage is uploaded.
The recipient of such a
MeadMessage may acknowledge the receipt by placing a file containing an
FtpAcknowledgementMessage in the same folder as the acknowledged message. The
FtpAcknowledgementMessage shall be named as
ACK_Identifier_YYYYMMDDhhmmssnnn.xml with the same naming convention as above.