The DEN of core components must be uniquely identifiable in each release. After we applied fixes #1040 (ACC.OBJECT_CLASS_TERM) and #1536 (BCCP.BASEDBDT), this rule could be broken. For example, consider an ACC called "Event Base. Details" and a BCCP called "Duration. Open Duration Measure Duration." If the ACC has an association with the BCCP, then the association BCC's DEN will be "Event Base. Duration. Open Duration Measure Duration." In this case, if we change the BDT of the BCCP from "Open Duration Measure Duration" to "Open Duration," the BCCP's DEN will be changed to "Duration. Open Duration." But, the BCCP's DEN should also be "Event Base. Duration. Open_ Duration." The current database and logics does not reflect this type of cascading change. Therefore, we are moving all DEN fields from the CC tables to the CC_manifest tables (e.g., acc.den -> acc_manifest.den).
The DEN of core components must be uniquely identifiable in each release. After we applied fixes #1040 (ACC.OBJECT_CLASS_TERM) and #1536 (BCCP.BASEDBDT), this rule could be broken. For example, consider an ACC called "Event Base. Details" and a BCCP called "Duration. Open Duration Measure Duration." If the ACC has an association with the BCCP, then the association BCC's DEN will be "Event Base. Duration. Open Duration Measure Duration." In this case, if we change the BDT of the BCCP from "Open Duration Measure Duration" to "Open Duration," the BCCP's DEN will be changed to "Duration. Open Duration." But, the BCCP's DEN should also be "Event Base. Duration. Open_ Duration." The current database and logics does not reflect this type of cascading change. Therefore, we are moving all DEN fields from the CC tables to the CC_manifest tables (e.g.,
acc.den->acc_manifest.den).