5.3 Folder and File Naming Convention for Bulk Data Feed
The arrival of the files of a Feed on the SFTP server shall be signified by placing a
Manifest file at the appropriate location. The
Manifest file shall refer to all files that are part of the Feed. The
Manifest file may only be placed on the SFTP server, once all other files have been completely uploaded.
A Feed is identified by the date and time of its creation in the form
DataFeedProviderbeing the DDEX Party ID of the organisation providing the Feed;
DataFeedRecipientbeing, optionally, the DDEX Party ID of the organisation for whom the Feed folder is created. For “broadcast feeds”, this element shall be left empty;
YYYYbeing the year of Feed creation;
MMbeing the month of Feed creation;
DDbeing the day of Feed creation;
hhbeing the hour of Feed creation;
mmbeing the minute of Feed creation;
ssbeing the second of Feed creation;
nnnbeing the millisecond of Feed creation; and
.extbeing a file extension if the Feed is provided in an archived and/or compressed format (such as .zip for a zip archive or .gtar for a GNU tar ball). If the Feed is provided as an uncompressed set of files in a folder, no extension shall be used.
The files inside a Feed folder shall be named in accordance with Clause 6.
Manifest file is identifiedby the data and time of its creation in the form
BWARM_Manifest_DataFeedProvider_[DataFeedRecipient]_YYYYMMDDhhmmssnnn.tsv where the various element follow the syntax set out above the the Feed name.