[GUI Plugin] FanFicFare

[texasnightowl]

Originally Posted by ownedbycats

From what I recall, JimmXinu's official advice for AO3 metadata is "just give up, it's a disaster."

lol. sounds about right. and true.

But if I remember right, removing freeformtags from this would leave you with just the fandom

Thanks, I will give it a try!

EDIT: Also, I should mention that AO3 semi-recently implemented a tag limit (thanks to that one author who thought it was funny to use literally thousands of tags). It's honestly a bit of a relief.

A limit on tags is way past overdue! I don't know what they set the limit to be, but anything over 20 for sure is too many imo and preferably less!

[ownedbycats]

I believe it was something about 75, which I found reasonable.

[texasnightowl]

Originally Posted by ownedbycats

[archiveofourown.org]
## AO3 doesn't have anything it calls 'genre'.  The adapter used to be
## hardcoded to include the site specific metadata freeformtags &
## ao3categories in the standard metadata field genre.  By making it
## configurable, users can change it.
include_in_genre: freeformtags, ao3categories

Just did one quick test. That definitely helped! I still have to deal with the overtagging of characters but at least I didn't have to sort through so much other crap!

[JimmXinu]

New Test Version Posted

2022-05-10
- fastnovel.net -> fastnovels.net - Rename adapter_fastnovelsnet - Fixes for site changes

Originally Posted by Ser4nb2LUY6e

I'm sorry, I understand how annoying it is to try and keep up with site changes... but fastnovel.net now redirects to fastnovels.net

Thanks for the heads up and figuring out the chapter POST.

UPDATE: I coded it to still accept fastnovel.net URLs and to still use [fastnovel.net] settings.

[JimmXinu]

Originally Posted by ownedbycats

Question: How (if possible) would I get custom_columns_settings to set an #omnibus boolean to 'yes' for anthologies and 'no' for all other fics?

I don't think there is a way to do that directly. FFF does set anthology=true in metadata, but I believe it's only useful in generate_cover_settings.

You can configure the title pattern (setting anthology_title_pattern) and configure tag(s) that are set for anthologies (setting anthology_tags).

If you truly see the need to also have a column for it, I suggest a composite column looking at the title or anthology tag(s).

Originally Posted by ownedbycats

From what I recall, JimmXinu's official advice for AO3 metadata is "just give up, it's a disaster."

I believe I expressed it as "I give up", but I stand by "it's a disaster."

[JimmXinu]

New Test Version Posted

2022-05-10
- fastnovel.net -> fastnovels.net - Rename adapter_fastnovelsnet - Fixes for site changes
- fix storiesonline login (again) - parameter name was changed back to "email" (#840) - Thanks mvlcek!

[JimmXinu]

Even Newer Test Version Posted

2022-05-10
- fastnovel.net -> fastnovels.net - Rename adapter_fastnovelsnet - Fixes for site changes
- fix storiesonline login (again) - parameter name was changed back to "email" (#840) - Thanks mvlcek!
- adapter_webnovelcom: Not all paragraphs starting with '<' are HTML. #841

[ownedbycats]

Originally Posted by JimmXinu

I don't think there is a way to do that directly. FFF does set anthology=true in metadata, but I believe it's only useful in generate_cover_settings.

You can configure the title pattern (setting anthology_title_pattern) and configure tag(s) that are set for anthologies (setting anthology_tags).

If you truly see the need to also have a column for it, I suggest a composite column looking at the title or anthology tag(s).

An action chains template to toggle the bool to 'yes' was my fallback plan, I was just hoping it was something that could be done from within FFF itself. Thanks.

[ownedbycats]

Question: Seems a bit unlikely, but aside from setting title/author to 'new only,' is there any way to have FFF indicate there was a metadata change in one of those fields so I can decide what to do about the potentially changed save path?

[JimmXinu]

Here are a few ideas:

• SmartEject missing/dup searches?
• Keep a second copy of each in another column that is New Only and compare?
• Use Audit Log plugin?
• Use FFF's logpage?
• Remove changeable metadata from save path?

SmartEject catches such things well enough for me.

[ownedbycats]

SmartEject's duplicate check is what I already use. Thing is, it only notices after the path has changed and the duplicate book's on device.

[riothamus]

I've been using FFDL with FFF's browser cache settings to download from ff.net. However, this sometimes leads to issues with longer stories with lots of chapters. Before cloudflare, FFF could just add the new chapters to the end of the existing story in calibre. Is there a way to get FFF to get just the new chapters and only download the missing chapters with FFDL? As it is now I have to redownload with FFDL all 75+ chapters just to get one updated chapters in FFF/calibre.

Hopefully this makes sense for what I'm asking. Thanks!

[JimmXinu]

If you are updating an existing epub from FanFicFare with 74 chapters, when chapter 75 comes out, FFF should only need to fetch chapter 1 (for metadata) and chapter 75 -- assuming you don't have check_next_chapter or meta_from_last_chapter set true and that it's been long enough that chapter 1 shows 75 chapters.

I would suspect that it's the chapter 1 lookup that's failing and you're assuming it needs all chapters.

If FFF really wants to download all chapters, that suggests that the epub has been changed or something else is going on.

[ownedbycats]

Originally Posted by JimmXinu

Here are a few ideas:

• SmartEject missing/dup searches?
• Keep a second copy of each in another column that is New Only and compare?
• Use Audit Log plugin?
• Use FFF's logpage?
• Remove changeable metadata from save path?

SmartEject catches such things well enough for me.

Actually, I think that last one might be doable. I already have #kobopath for part of my save template, so modifying that to also include the original author and title might work.

[JimmXinu]

Originally Posted by ownedbycats

Actually, I think that last one might be doable. I already have #kobopath for part of my save template, so modifying that to also include the original author and title might work.

Actually, I meant removing title/author altogether and using {id} instead.