See F24 nightly composes. The productmd "compose ID" for a nightly compose is something like:

Fedora-24-20160321.n.0

the 'date(.type).respin' part of this is used in the names of, e.g., the anaconda ISOs:

Fedora-Server-netinst-x86_64-24-20160321.n.0.iso

however, it's not quite correct for livemedia-created live images:

Fedora-KDE-Live-x86_64-24-20160321.0.iso

note the type identifier - the ".n" - is missing.

the problem with this, aside from the lack of consistency, is that 'Fedora-24-20160321.0' would be a valid productmd compose ID, but for a *production* compose, not a nightly. There may even *be* a compose with the compose ID 'Fedora-24-20160321.0' (or whatever date / respin you like) which is not the same compose the image comes from.

We don't actually wind up with duplicated file names because the file names for production compose images appear to be based on the compose label rather than the compose ID (so we get Fedora-KDE-Live-x86_64-24_Alpha-5.iso or whatever). But it could still be confusing/misleading, particularly to tooling.

I would've tried to fix this, but I couldn't find the relevant Koji code for livemedia-creator, it doesn't appear to be in Koji git master. This does appear to be in Koji, not in pungi or pungi-fedora or livemedia-creator itself - the name is passed to livemedia-creator as "--iso-name", but it's not given to Koji by pungi, pungi only gives Koji the *first* part of the image name (Fedora-KDE-Live), Koji figures out the rest.