I have run a consolidation job and it's completed successfully. So what am I supposed to do next?
Background:
I ran a consolidation on 2 classification sets that were migrated over from the old classifications. These 2 sets are for:
- eVar13, dev report suite
- eVar13, prod report suite
The legacy classifications had the same set of classification fields. These legacy classifications are classified with both Importer and Rule Builder.
The consolidation validated successfully and compared successfully. Since it turned out well, I approved it. But approval removes the original classification sets.
Here's why removing the original classification sets is a problem to me:
- The consolidated classification set is a "Lookup" type. So it doesn't show the report suite subscriptions. This is unlike "Primary" classification sets, where the report suite subscriptions have to be selected and are clearly displayed. How is future me or other Analytics users supposed to know that eVar13 is subscribed to this "Lookup" classification set?
- My experience with "Lookup" classification sets is that they're like a 1-to-many mapping from one classification to another. For example, if eVarX has a classification "foo", and I add a "Lookup" classification set to that "foo" with 2 classifications "foo1" and "foo2", then I can see the relationships eVarX --> foo --> foo1 and eVarX --> foo --> foo2. But consolidated "Lookup" classification sets look like they have a a many-to-many relationship, i.e. eVarX -- (via consolidated set) --> foo, eVarX -- (via consolidated set) --> bar, eVarX -- (via consolidated set) --> baz, etc. To me, that looks like what a "Primary" classification set should do. Or am I wrong in my thinking about the classification flow?
The lack of showing the report suite subscriptions is the bigger problem for me. Right now, I can only be aware that eVar13 has an appropriate classification set because (a) I still remember it, and (b) when I try to create a new "Primary" classification set that subscribes to eVar13, AA shows an error that a classification set already exists for it and links to the consolidated "Lookup" classification set, which does not show any subscriptions (!!!).
Hopefully, someone can explain/describe the "correct" way to use and understand classifications consolidations. Meanwhile, my process is going to be: when a consolidation job has compared successfully and prompts me to approve it, I am not going to approve it. The resulting removal of the original classification sets -- causing the lack of any visibility on the report suite subscriptions -- is just too scary for me.
