[GUI Plugin] FanFicFare

[texasnightowl]

Originally Posted by bigwoof

To "solve" this exact problem, I ended up writing a whole set of custom action chain scripts all tied together in an action chain module mapped to a hotkey. so for any new AO3 book, instead of whatever the authors thinks I need to know about, I just press the hotkey and the module changes all the tags to things I care about (by extracting and processing keywords from all the fields present in the metadata).

yes, it means I will never get any new tags but it also means my tags are capped at 115 (what calibre tells me) which makes my mobile book reader (moon+) happy when I search :-)

oh, do you have this summarized anywhere? I know there is a chain actions plugin but I have not installed it or used it. I wouldn't really know where to start but I know there is a thread for that chain actions plugin.

I'm starting a new library because of the tags issue. In my new one, right now, I exclude "genre" aka AO3categories and freeformtags from subject tags so new books coming in only get relationship and character tags. But, all the freeform tags are in the saved metadata column.

Then my plan is to either add my own tags as I go OR search on a phrase such as "time travel" or "alternate universe" and add just a simple straightforward tag to those.

Do your chain actions do something similar? ie. look for a phrase and then set a tag based on that phrase?

[texasnightowl]

Originally Posted by JimmXinu

...
FFF saved metadata using column type Long Text, 'interpreted as text'...

Can I ask why "interpreted as text" instead of html?

I didn't realize that text was recommended so in my new test library (And still testing...only about 10 books in it right now.) I had html.

With it as interpreted as html, obviously it's nicely readable in the box on the custom column tab of the book record. Whereas when I just switched the column to interpret as text, it's not as easily readable since now all the html code is shown. p span div, etc.

Is the text version more readable by FFF when doing metadata updates?

I'm planning on using the saved metadata info to search for terms/keywords to set some basic tags. So as long as html vs text doesn't impact that, I guess I don't care?

(reminder: I have excluded genre (aka ao3categories and freeformtags) because of crazy stupid tagging on ao3 and because I didn't want thousands of stupid tags. So the plan is to do basic searches like "time travel" and then assign a tag of my choosing to those results. So instead of stories having 10 different variations of "time travel", they will only have 1, when I add it.)

[JimmXinu]

Originally Posted by texasnightowl

Can I ask why "interpreted as text" instead of html?
...
Is the text version more readable by FFF when doing metadata updates?

If interpreted as HTML, Calibre rewrites the HTML in such a way it breaks FFF's ability to read it back again if you ever edit it. And as I recall, it could happen sometimes even if you didn't think you'd edited it.

Originally Posted by JimmXinu

I still recommend leaving the Saved Meta column interpreted as Text to be a little bit safer.

Calibre changing the HTML in long texts automagically came along after the FFF Saved Metadata Column feature. I would not have used an HTML format when the feature was implemented if I had known that was coming.

[texasnightowl]

Originally Posted by JimmXinu

If interpreted as HTML, Calibre rewrites the HTML in such a way it breaks FFF's ability to read it back again if you ever edit it. And as I recall, it could happen sometimes even if you didn't think you'd edited it.

ah. ok. I consider the saved meta column to be one I would never even think of editing. but accidents do happen. so I did go ahead and change the column type to interpreted as text.