Content Analysis DB > Fields > Field Types > > Disposition My List ♥ ()

Disposition

This is the treatment a piece of content will get during a transformation.
General Usefulness: ★ ★ ★
Ease of Automation: ⚙⚙⚙
⚠ Gotchas ⚠

Organizations will be tempted to distribute the decision of what to do with content, and to manually decide per content item. This is a very dangerous approach at scale:

  • Instead of making institution-wide decisions, prioritizing what's important across the board, teams will make their own local decisions.
  • There is no clear ruleset for decisions to explain and discuss (or that can be used on an ongoing basis)
  • It is very difficult to iterate on decisions if it's done manually.
Source Types:
Maps & Rules, Formula

Other closely related fields you may consider

Note that lower level fields may sometimes be needed to compute more useful fields. Also, sometimes the higher level fields may be more difficult to compute, so they are not always worth it.

↑↑↑ Consider this higher level field ↑↑↑
Disposition (you are here)
In Content Chimera

Content Chimera deeply supports dispositions. You can either use default dispositions or define your own. Then you apply dispositions via rules, that you can iterate on over time.