My List ♥ ()

Maps & Rules Content Analysis Fields

Source Type: Maps & Rules

A map is a set of from → to pairs that allow you to do things like check if a URL has "/blog/" in it (the "from") then it is a "Blog Post" (the "to"). Rules can be more sophisticated like "if it's a Blog Post and over ten years old then delete it". This is a way to categorize content very quickly and efficiently (and also allow you to reiterate often).

In Content Chimera

Chimera allows you to define, manage, and run maps and rules.

See Maps & Rules fields below. Or show fields for all field types.

Answer some questions to help select fields

If we take the traditional view of a content inventory or audit, we have rows representing each page (so each row has a unique URL) and then we have columns for things like the meta description or crawl depth. These columns are the different fields we have available to us in our content analysis.

①. Define what you are trying to accomplish.

Your content analysis needs to be grounded on your analyze goal.

Examples: Plan Digital Transformation, Test Content Hypothesis, Provide Better Bid.

②. Define your analysis approach.

Size and complexity of your digital presence

Size and complexity of your digital presence should drive your content analysis approach.

My digital presence is:

Use the calculator

Your approach

Content analysis does not necessarily mean opening up a spreadsheet. Before diving in, you should define your basic approach to the analysis.

Examples: Brute Force; Sample, Rules, Repeat; Quick Take.

③. Select fields toward your goal, grounded in your prioritized list of questions you want answered.

Although you can use this database however you like, in general we recommend that you build up a list of fields that will be useful for your analysis. To do so, just click on the heart next to any field name. After you have hearted some fields, you can see an analysis of your list at My List ♥ (at which point you can move to ④. Start iterating on your analysis, starting with the basics).

Bucket ♡

When planning a transformation, it can be useful to bucket similar content (often grouping content that will be treated similarly to explain the situation to stakeholders).

General Usefulness:

Ease of Automation:

Consider instead: Disposition

[Category] Revenue ♡

Particularly useful for product or property pages, this field represents the revenue generated by this product or property (regardless of whether it was directly generated by digital channels or not).

General Usefulness:

Ease of Automation:

Compare with other Org fields.

Content Type ♡

Content Type (semantic type of content, such as Product Page or Event) is usually an extremely effective way to group and look for patterns across a digital presence.

General Usefulness:

Ease of Automation:

Compare with other Category fields.

Disposition ♡

This is the treatment a piece of content will get during a transformation.

General Usefulness:

Ease of Automation:

Consider instead: Effort

Division ♡

The organizational division (or department, vice presidency, company, etc) that owns the page.

General Usefulness:

Ease of Automation:

Compare with other Org fields.

Effort ♡

Expected manual effort to transform the content item.

General Usefulness:

Ease of Automation:

Compare with other Decision fields.

File Group ♡

On particularly complex digital presences, there may be so many file formats that seeing all of them in charts or presentations is confusing. File Group groups the file formats, for instance "Data or Spreadsheet" to capture CSV and Excel files.

General Usefulness:

Ease of Automation:

Compare with other Basic fields.

Has [Problem] ♡

Yes or no, does this piece of content have this specific problem? The actual field name would depend on your situation, such as "Has Wall of Text".

General Usefulness:

Ease of Automation:

Compare with other Quality fields.

[Problem] Count ♡

How often does the problem happen on the page? This would be a specific issue, so something like "Left Nav Count".

General Usefulness:

Ease of Automation:

Compare with other Quality fields.

Site ♡

Within which site (as experienced by the site visitor) does this content appear?

General Usefulness:

Ease of Automation:

Consider instead: Site Type

Site Section ♡

The section of a site (for instance the news section, or a section for a particular program).

General Usefulness:

Ease of Automation:

Compare with other Category fields.

Site Type ♡

For large scale digital presences, grouping sites by type can be a highly effective way of managing and transforming.

General Usefulness:

Ease of Automation:

Compare with other Category fields.

Source System ♡

Where is the primary source of content for this URL? For instance, what CMS, document management system, or product information system does this content primarily come from?

General Usefulness:

Ease of Automation:

Compare with other Category fields.

[Target] Field ♡

What the *desired* field value would be. For instance, there may be an existing content type but in some cases it should be another content type (so you would have a Content Type field as well as a Target Content Type field).

General Usefulness:

Ease of Automation:

Compare with other Decision fields.

Legend