[GUI Plugin] FanFicFare

[JimmXinu]

New Test Version Posted

2023-07-19
- adapter_storiesofardacom: Fix for detecting adult question on indiv chapters.

Originally Posted by halcyon6116

Yes! Here is the log for three other stories that got the same error (attached file + text of log):
http://www.storiesofarda.com/chapter...w.asp?SID=6637
http://www.storiesofarda.com/chapter...w.asp?SID=6188
http://www.storiesofarda.com/chapter...w.asp?SID=5817

You need to add is_adult:true either under [defaults] or [www.storiesofarda.com].

storiesofarda.com 'adult' walls individual chapters and the site has changed slightly so that the detect for that wasn't firing.

Assuming you are an adult, of course.

[halcyon6116]

Originally Posted by JimmXinu

New Test Version Posted

2023-07-19
- adapter_storiesofardacom: Fix for detecting adult question on indiv chapters.


You need to add is_adult:true either under [defaults] or [www.storiesofarda.com].

storiesofarda.com 'adult' walls individual chapters and the site has changed slightly so that the detect for that wasn't firing.

Assuming you are an adult, of course.

That worked perfectly - thank you!

[chicleeblair]

The prefix code didn’t work for me, copied directly. What I want is to have category/fandom prefixed with f. characters with c. and ships with s. If someone could get that to work, I’d very much appreciate it!

Also, what would I use to have only “/“ ships appear in tags (specifically on AO3)?

[ownedbycats]

For the second one, a regexed include_metadata checking for '/' or an exclude with '&' should do it.

[cryosaur]

Is there a way to override the Configure > Standard Columns settings on a per-adapter basis? I know this is available for custom columns with the custom_columns_settings field, but there does not seem to be any equivalent for the standard columns.

For example: I have the Standard Columns > Comment set to New Only to preserve my edits to fic description, but want to turn it off to allow fic updates to overwrite the field on a specific site. Is that possible to do via personal.ini?

[cryosaur]

Is there a way to override Standard Columns, New Only settings in personal.ini? Like, an limited equivalent of custom_columns_settings for the standard columns?

[culytera]

Originally Posted by chicleeblair

The prefix code didn’t work for me, copied directly. What I want is to have category/fandom prefixed with f. characters with c. and ships with s. If someone could get that to work, I’d very much appreciate it!

Also, what would I use to have only “/“ ships appear in tags (specifically on AO3)?

Like this? (The titlepage entries one isn't necessary, I just wanted to put it there)

add_to_extra_valid_entries:,prefix_characters,prefix_fandom,prefix_ships

include_in_prefix_characters:characters
include_in_prefix_ships:ships
include_in_prefix_fandom:category

exclude_metadata_pre:
 prefix_ships=~(.*) & (.*)

replace_metadata:
 prefix_ships=>^(.*)=>s. \1
 prefix_fandom=>^(.*)=>f. \1
 prefix_characters=>^(.*)=>c. \1

keep_in_order_ships:true
keep_in_order_characters:true
keep_in_order_prefix_characters:true
keep_in_order_prefix_ships:true
keep_in_order_prefix_fandom:true

prefix_ships_label:Prefix Ships
prefix_fandom_label:Prefix Category
prefix_characters_label:Prefix Characters

include_subject_tags:prefix_characters,prefix_ships,prefix_fandom
add_to_titlepage_entries:,prefix_characters,prefix_ships,prefix_fandom

Result when I tested this:

Spoiler:

Moderator Notice
Please put spoiler around large images or don't include in post text.

[JimmXinu]

Originally Posted by cryosaur

Is there a way to override the Configure > Standard Columns settings on a per-adapter basis? I know this is available for custom columns with the custom_columns_settings field, but there does not seem to be any equivalent for the standard columns.

For example: I have the Standard Columns > Comment set to New Only to preserve my edits to fic description, but want to turn it off to allow fic updates to overwrite the field on a specific site. Is that possible to do via personal.ini?

No. Standard columns are standard.

The only reason custom_columns_settings exists in personal.ini is because different sites can have different site specific metadata that would be too hard to create a config GUI for.

You can create custom columns for your comments, or put the original story description in a custom column.

[chicleeblair]

okay, one, y’all, the reason the first extra_valid_entries solution didn’t work for me was a missing comma. ugh. but secondly, I figured out something cool.

First, with the heading, I did have to take out the space after the . to make Calibre use it as a hierarchal tag. So the code looks like this:

add_to_extra_valid_entries:,prefix_characters,pref ix_fandom,prefix_ships

include_in_prefix_characters:characters
include_in_prefix_ships:ships
include_in_prefix_fandom:category

exclude_metadata_pre:
prefix_ships=~(.*) & (.*)

replace_metadata:
prefix_ships=>^(.*)=>s.\1
prefix_fandom=>^(.*)=>f.\1
prefix_characters=>^(.*)=>c.\1

keep_in_order_ships:true
keep_in_order_characters:true
keep_in_order_prefix_characters:true
keep_in_order_prefix_ships:true
keep_in_order_prefix_fandom:true

prefix_ships_label:Prefix Ships
prefix_fandom_label:Prefix Category
prefix_characters_label:Prefix Characters

include_subject_tagsrefix_characters,prefix_ship s,prefix_fandom
add_to_titlepage_entries:,prefix_characters,prefix _ships,prefix_fandom

One thing I regret losing parsing through tags is the fandom-specific but often fun tags as universal as BAMF to those far more niche. But then, I had lists of names used to keep them out of my edited tags. Why not put it to use?

so, I created a Name Tags column and then in
include_metadata_pre:
names=~(.*\scharacter name\s.*)$

it’s almost exactly the same as the freeformtags(.*\scharacter name\s.*)$ code I put in exclude_metadata_post The trailing spaces ensure that a name like Eve doesn’t also cut out/keep any tags that include the word “believe” or “An” doesn’t eliminate…I don’t know, “cabana.” I still take out names that turn up in other words, JIC


I may expand it or add a second with more canon-specific things, e.g. “South Downs” for Good Omens and such. we’ll see.


if you care about capturing all the upper- and lowercase tags you can find/replace each letter to [Xx], but be sure you only do it to the names, not your trailing spaces. (I have the names on a spreadsheet, put the code in column on either side, and then copy and paste it into a txt file to clean up the spaces that adds. there might be a better way, but it works for me.)


I’m trying to make everything as automated as possible before I even add my ASOIAF tags into this mess...

[chicleeblair]

I feel like I’m going crazy. I’ve figured out so much, but then my trial and error fails me on something that is simple.

I want to have the character name Anya appear as Anya Jenkins in any fandom with the name “Buffy” in it. Every combination I try fails. even trying category!=The 100 fails, but I don’t want to do that, because there are multiple categories of Buffy (comics, etc.), and that wasn’t working anyway.

what I come up with is

characters, ships=>^([Aa]nya.*)$&&category=~^([Bb]uffy.*)$=>Anya Jenkins

without the category section, this works, and I tried ending that without the $ before the && because I’m pretty sure that’s correct, but no variation on anything I can think of works.

[chicleeblair]

Ugh. I hate that I keep solving my issues before my post even shows up. (I think I solved it.) It’s the order, correct? it should’ve been:

character=~^(Anya.*)=>Anya Jenkins&&category=~^([Bb]uffy.*)$

That worksd, anyway, and didn’t turn the 100’s Anya into Anya Jenkins.

[JimmXinu]

New Test Version Posted

2023-07-21
- Fix for #979, AO3 Get URLs from Page

https://github.com/JimmXinu/FanFicFare/issues/979

[w4tchdoge]

Hello there.
I'm sorry if I'm about to ask an obvious question which has already been answered (apologies if it has been answered, but I haven't been able to find it) but I'm currently trying to append "Web Fiction" as a default tag to the tags the FanFicFare plugin writes to the metadata of the file it outputs.

e.g. Under normal operations, using FFF on the following title from Scribble Hub results in the following tags. The result I'm looking for is for FFF to append a tag to the tag list like so.

So far I've attempted this by putting the following code into the defaults section of my personal.ini file:

add_to_extra_valid_entries:,web_fic_tag
include_in_web_fic_tag:status
replace_metadata:
 web_fic_tag=>^(.*)=>Web Fiction
include_subject_tags:,web_fic_tag

But the above code replaces all the tags for a work with the single tag "Web Fiction", which is not the result I'm looking for.

I may have used Scribble Hub in the example, but I would like to implement this behaviour on any work that FanFicFare processes.

Any information/assistance on how to achieve this or whether this is possible in the first place would be greatly appreciated.

[culytera]

You forgot to retrieve the group that matched your regex. It should be:

 web_fic_tag=>^(.*)=>Web Fiction \1

[w4tchdoge]

Originally Posted by culytera

You forgot to retrieve the group that matched your regex. It should be:

 web_fic_tag=>^(.*)=>Web Fiction \1

Replacing

web_fic_tag=>^(.*)=>Web Fiction

with

web_fic_tag=>^(.*)=>Web Fiction \1

results in the following, which is not the result I am looking for.

Regarding the code in my initial message.
Said code comes from me not knowing how to define a tag(?)/variable(?) which is always a fixed text (in this case it would be defining web_fic_tag to always be "Web Fiction").
Hence I have copied what I have seen others do with replace_metadata and assigned the status of whatever work I am using FFF on to web_fic_tag. But I don't actually want web_fic_tag to be the status of the work, I want it to always be "Web Fiction". Hence the regex I have used replaces the whatever the retrieved status was with "Web Fiction".
I understand that this is a roundabout way of going about this but it is the only one I could think of.

If anyone has any more suggestions I will be more than happy to test them and see if it works.