Content Chimera was born out of migration and rollout planning.
Whereas migration planning concentrates on moving the content from one system to another, rollout planning is focused on sequencing site (or potentially site section) launches. For instance, if an organization is rolling out new sites across the globe, then rollout planning works out how these launches (and the work leading up to launches) should be sequenced.
Steps in Content Chimera¶
Organize your sites into site groups. You may have a natural grouping of sites, and this should be represented in how you create your sites.
Contact David Hobbs Consulting for help in creating the site groups. This is not yet exposed in the front end.
Ensure your client is ready for a large-scale crawl, since the crawl may seem like a denial of service attack when requesting so many URLs (see technical details).
Crawl all sites. If you are doing complex rollout planning then there is a high probability that these are on different systems, and the easiest way to rationalize across all of them is probably by crawling. That said, you could also import the URLs if that makes more sense.
Process the site group at the level that you will be doing the analysis (otherwise you will not be able to do charts and rules at that level).
Draw a treemap with level 1 = site, level 2 = folder1, and level 3 = folder3.
Convert the above chart to a bar chart to see if there is much consistency in folder1 (if the only difference is language translations, then contact us about creating language tokens to make rules generation easier).
In the case of rollout planning, the rules are also used to rationalize across the sites. So attempt to write rules that can group like-with-like (for instance, you may start by only filling out the “bucket” part of the decision, leaving the others as “TBD” for starters). Iterate on the rules (and running the ruleset) until you have a rationalized view across the sites.
Continue on the rules to decide what to do with the content.
As you decide on the order of sites, consider the total amount of work that would be required at each phase (don’t put all the sites that take the most work at once — otherwise there isn’t much advantage in sequencing the rollout at all).
Aside from the note above, some other rollout planning features are only available in the backend currently (at David Hobbs Consulting, we use these features for our client work). Let us know if you need further rollout planning capabilities and we will prioritize pushing these to the front end.