Within the archival, production, and
deliverable directories, the audio files for a given work are
grouped into multiple segments, each stored in a separate
sub-directory, segmentid. Each segment in turn may
be composed of multiple channels of audio. If a set of audio is not
segmented, it will only have one segment subdirectory. If audio
multiple segments (and sub-directories) are present, then an
aes31.adl file will be present in the parent directory.

The processing history files, digiprov.xml,
can occur:

Once at the level of the archival or production
directories, in which case it applies
against all segments

The digital audio for a particular segment can be multi-channel,
with each channel saved to a separate AIFF or Broadcast Wave file.
The AIFF filenames are of the form:

name.n

and Broadcase Wave are of the form:

name.n.wav

where name is an arbitary name assigned to all of the
audio channel files for a given audio segment, and n is
a numeric value, 1,2,..., identifying the channel.
Thus, a stereo pair of AIFFs would be named:

name.1
name.2

Each audio file is associated with a AES core audio metadata file:

name.n.xml

where the numeric value, n, indicates the channel.

Archival or production directories with only a single file can optionally have the same naming convention minus the numeric value, 1,2,....

name.aif
or name.wav

Regardless of the number of channels of audio stored for a
segment, there may be a single external waveform reduction file,
with a filename of
the form:

DRS batch metadata for submission may be overriden for each content
file with the DMart Batch Override File (dbof). One can add or change
metadata values for the generated batch.xml file on a per-audio-file
basis. Here's an example file which specifies a different DRS
ownerSuppliedName (local id) than the default, which is the the file
path and name: