Comment 5 for bug 677074

Just to add another perspective, I think the "fall through" idea is a definite improvement, and sorely needed, but I am still wondering about this dynamic weight idea. Not having giving it nearly as much thought as what is shown here, I am left thinking we might be better served by simply providing for ordering the rules in a more manual fashion. The logic would then be something like:

1. Process the rules for the context org_unit in the order as set.
2. If a rule matches, set whichever attributes (circulate, duration, etc.) it sets. These are now frozen.
3. Proceed to following rules, climbing the org_unit tree if needed.
4. When you have a complete set of attributes, stop.

It also seems to me there are cases where you might (ideally) want the columns weighted differently depending on the actual values of the rule. At that point the simplicity of manually ordering the rules seems to become more worth it.