I’m working with the DCMTK version 3.68. The previous version I had a bug that allowed more transfer syntaxes than they should have for AP_GeneralPurposeDVD instead of splitting them into AP_GeneralPurposeDVDJPEG and AP_GeneralPurposeDVDJPEG2000.

I now have a dilemma because I would like to support creating a DICOMDIR that can support all the transfer syntaxes I used before.

Is it possible to update the DICOMDIR’s Application Profile when receiving files to store that don’t fit the current Application Profile?
What happens to the previously added files. Are the transfer syntaxes convert to on of those supported by the new Application profile?

Some background for the questions above.
DCMTK 3.5.4 for Application Profile
allowed the following transfer syntax.
found = compare(transferSyntax, UID_LittleEndianExplicitTransferSyntax) ||
compare(transferSyntax, UID_JPEGProcess14SV1TransferSyntax) ||
compare(transferSyntax, UID_JPEGProcess1TransferSyntax) ||
compare(transferSyntax, UID_JPEGProcess2_4TransferSyntax) ||
compare(transferSyntax, UID_JPEG2000LosslessOnlyTransferSyntax) ||
compare(transferSyntax, UID_JPEG2000TransferSyntax);

/// General Purpose DVD with Compression Interchange (STD-GEN-DVD)
AP_GeneralPurposeDVD,

Version 3.6.8 of DCMTK has removed AP_GeneralPurposeDVD and provided two new options
/// General Purpose Interchange on CD-R or DVD-RAM Media (STD-GEN-CD/DVD-RAM)
/// General Purpose DVD Interchange with JPEG (STD-GEN-DVD-JPEG)
AP_GeneralPurposeDVDJPEG,
/// General Purpose DVD Interchange with JPEG 2000 (STD-GEN-DVD-J2K)
AP_GeneralPurposeDVDJPEG2000,

How can I support both Application Profiles in the same DICOMDIR? If that’s even possible?

Thank you.

I read the DICOM standard but didn’t see what I was looking for.
Looked at the DCMTK code for version 3.5.4 and 3.6.8.