SFTP Choreography and Directory Naming

Pandora requires that providers follow the DDEX ERN Choreography (ECHO) Standard, and in particular the Batch Profile, which dictates a separate directory for each release within the batch directory. The most recent version of the standard is 1.6.1. See DDEX.net for a visual example of the directory naming and structure decribed below. 

"A Batch is identified by the date and time of its creation in the form YYYYMMDDhhmmssnnn." This is the name of the batch directory. 

The specification also states, "Each Release within that Batch shall be placed into a separate folder using the ReleaseId of the Release as its name." This would be the UPC (or occasionally, GRid). 

Even if there is just one release per batch, you'll need to include one "BatchComplete" file per batch, at the batch directory level. This must be delivered last after all other files in the batch, as a signal to our system to beign ingesting the batch. It should be named following the form "BatchComplete_YYYYMMDDhhmmssnnn.xml" (as defined by DDEX).  

Pandora does not process priority indicators (P, M, or N) from batch names. It is acceptable to include them, but they are not yet honored. 

Please note that after directory structure changes you may need to adjust the TechnicalSoundRecordingDetails/File/FilePath values in your ERN xml to point to the new file location. 

You may place as many releases in each batch as you wish, or as few as one. Whatever allows you to execute the fastest delivery. Also, we have found that increasing the number of simultaneous sftp connections can massively increase delivery speed for a large catalog delivery. 40 simultaneous connections has worked well in the past. Your mileage may vary of course! 

For further details, see the official DDEX specification for the SFTP Batch Profile:

Setting Up to Deliver Content to Pandora