I did look at this, both applying one of the existing rule sets and re-using the infrastructure (aka tag_mapper) to create additional rule sets. These are my observations:
- Applying the existing add book or download metadata rule sets is problematic. Which? When? FFF configures everything by library, those rules do not.
- Creating new rule sets using tag_mapper/author_mapper are possible per library. But for just tags/authors? For custom columns? For each custom column?
- Pro: The tag_mapper a nice GUI solution for filtering and modification of tags.
- Con: It's not as flexible and capable as FFF's ini text solution. For example, conditionals have no equivalent.
- Pro: Aside from GUI-ness, the biggest advantage I see to the tag_mapper is that it uses the Tag Editor, which knows what tags are already in the library, making it easy to limit incoming tags to those already in the library.
- Con: When I created a rule containing all my tags (1867), I wasn't able to edit that rule again reliably. Double clicking it only occasionally worked.
- Con: Redundancy of features: I couldn't remove replace_metadata from FFF even if I wanted to because CLI and web service still need it. Troubleshooting complex setups with both is daunting.
And finally, only Tanjamuse and (maybe?) ilovejedd showed any interest.
So I'm shelving this proposed change for the time being. A more general tool, like
CALM may be useful.