Edit raw tag mapper rules?

[sweth]

Is there any way to edit raw tag mapper rules, e.g. a tweak that would expose saved rulesets as plaintext so that I could edit them and then reload them?

Related: part of the motivation behind this is that the UI appears to truncate the rule summary in the main Edit Tag Mapper Rules window regardless of how wide the window is, so the only way to see the details of a long rule appears to be to open the rule. Is that something that can be configured? Similarly, at least w/ 3.4 on recent versions of OSX, the Edit Tag Mapper Rules window has a *lot* of unnecessary whitespace padding around each of the rule summaries finding the right rule (I have a lot of them) requires a lot of scrolling, and which also makes the workaround for the "long rules get truncated in UI" issue of just splitting rules up less palatable. (See attached)

[theducks]

Originally Posted by sweth

Is there any way to edit raw tag mapper rules, e.g. a tweak that would expose saved rulesets as plaintext so that I could edit them and then reload them?

Related: part of the motivation behind this is that the UI appears to truncate the rule summary in the main Edit Tag Mapper Rules window regardless of how wide the window is, so the only way to see the details of a long rule appears to be to open the rule. Is that something that can be configured? Similarly, at least w/ 3.4 on recent versions of OSX, the Edit Tag Mapper Rules window has a *lot* of unnecessary whitespace padding around each of the rule summaries finding the right rule (I have a lot of them) requires a lot of scrolling, and which also makes the workaround for the "long rules get truncated in UI" issue of just splitting rules up less palatable. (See attached)

It is GUI.JSON in your configuration folder.
(mine)

 "tag_map_on_add_rules": [
    {
      "replace": "", 
      "match_type": "one_of", 
      "action": "remove", 
      "query": "General,Fiction,Literature"
    }
  ],

As always: Calibre must be not running, MAKE A file BACKUP, use extreme care

[sweth]

Hmm... it isn't in gui.json for me, but that led me to do some digging and I did find the above config in metadata_sources/global.json . Not sure why it would be in a different location, but I'll play with that file and hopefully it functions the same. Thanks!