[GUI Plugin] FanFicFare

[supergg]

Hello.
I have a little problem, i'm trying to download numerous .epub from an author (like 250+ epub files), but calibre only download 70 of them.

I think i know the "problem" : on the website, the author page show the first 70 stories, but if i want to have all of them listed, i need to click on a "Show More" button. (4 times in total.)

The problem is that, clicking on that button does'nt change the web adress, so when i download the stories using this same web adress, it only downloads the "first" page (the 70 first stories), not knowing that there is more page available.

Any ideas/solutions to that? Or am i facing a limit do the website?

Worst case scenario, i can download them manually, but that would take quite a bit of time ^^

Thank you for your time.

[JimmXinu]

That's more than I recommend downloading at one time anyway. Doing lots of downloads at once is a good way to get blocked by the site. For most sites, I recommend doing batches of 20-30 with an hour or two in between batches.

Instead of using the 'Get Story URLs from Web Page' feature, you can highlight then drag (or copy/paste) each page onto/into FFF's Story URLs dialog, or even onto the FFF button in Calibre.

Without knowing what site you're talking about, I cannot tell you anything more.

[supergg]

Thank you JimmXinu, i will follow your recommandation and download them one by one.

[Far_Pen_6884]

I've been a bit indecisive about how to set up Calibre before I started using the FanFicFare plugin to import fanfics. However, I recently discovered the "Saved Metadata" column, which I plan to use initially to start getting the fics I read. I’ll worry about organizing the library more thoroughly later.

I want to get all available metadata from AO3 when importing a fic and save it into the Saved Metadata column. So far, I've assigned these Calibre columns (or custom columns) to capture metadata fields from AO3 fics:

- FanFicFare column (Calibre column or #custom_column)
- Category (what? is this fandom?)
- Genre (what?)
- Language (languages)
- Series (series)
- Characters (#characters)
- Relationships (#relationships)
- Status (#writing_status)
- Published (published)
- Updated (#updated)
- Created (Date)
- Rating (#content_rating)
- Warnings (#archive_warnings)
- Chapters (#chapter_count)
- Words (#word_count)
- Site (what? isn't this publisher?)
- Publisher (publisher)
- Story ID (#story_id)
- Author ID (#author_id)
- Extra Tags (#extra_tags)
- Title (#title)
- Story URL (#story_url)
- Description (#description)
- Author (authors)
- Author URL (#author_url)
- File Format (formats)
- FanFicFare Version (#fff_version)
- Update/Overwrite Error (#fff_update_overwrite_error)
- Saved Metadata (#fff_saved_metadata)
- Last Checked (#fff_last_checked)

I've heard it’s possible to also capture additional AO3-specific stats like kudos, bookmarks, and such, but I'm not sure how to configure FanFicFare or Calibre to fetch and save these fields automatically.

Could anyone share advice or examples on how to configure FanFicFare and Calibre to extract all available metadata from AO3 fics—including kudos and other stats—and save it to the "Saved Metadata" column for archival?

Moderator Notice
Moved here as it was an FFF question. Please post specific PI questions in their forum.

[Clem2605]

Originally Posted by Far_Pen_6884

I've been a bit indecisive about how to set up Calibre before I started using the FanFicFare plugin to import fanfics. However, I recently discovered the "Saved Metadata" column, which I plan to use initially to start getting the fics I read. I’ll worry about organizing the library more thoroughly later.


Could anyone share advice or examples on how to configure FanFicFare and Calibre to extract all available metadata from AO3 fics—including kudos and other stats—and save it to the "Saved Metadata" column for archival?

So, the Saved Metadata Column is a column where FFF automatically save ALL of the work's metadata's that FFF is able to obtain in one place. The only setting up it needs is for you to create a long-text column in calibre, go to FFF's options in 'Custom Columns' and select this column next to 'Saved Metadata Column'.

There is no need to create a column for every metadata out there for them to be saved in the saved metadata column. So unless you need them in calibre for handling purpose, do not create a column for every metadata out there.

However, if you do want to create a column with your works' kudos for exemple, those will have to be set up in your personal.ini. You can seach in 'defaults.ini' for kudos, in order to find all the extra valid entries available for ao3 and their correct name.
Then, you can seach for 'customn_columns_settings', where it will explain how to set up those extra columns.

If you plan to really personnalise your FFF settings, don't hesitate to carefully read the default.ini file, at least the relevant sections for you, because it has most of the answers you will need.

[iakrus]

hey! i'm just starting to add stories to calibre again after months off- computer issues and such. during that time, instead of downloading the fanfiction, loading it on my reader and THEN reading it, i've generally been reading on the site.
i want to add the fics i have read- my history. and that has a date of when you last opened the fic which is often when it was finished. is there a way to add that metadata to calibre- probably its own column, that i could then transfer to my "finished reading" metadata column.
because the problem is, fanficfare opens the fics to load them, so the last read date changes to right now. but then i cant edit in the finished reading column what the date is, because its gone. i could do it manually by copy and pasting it into a doc before downloading the fics, but when im doing batches that would be a pain in the ass.
any solutions? or am i just gonna have to suck it up and screenshot my ao3 history or something before adding fics

[JimmXinu]

Originally Posted by iakrus

...

Are you talking about history and 'last read' timestamp in AO3?

In that case, what comes to mind is to do the downloads without logging in via FFF (ie, remove always_login:true). That won't work with stories that require login, of course.

Otherwise, yes. The only answer I see is to save your dates off somewhere else.

[AzureSuperuser]

Hi, just noticed that the links from novelfull.com are not able to download.
Gets the error 403 message

[JimmXinu]

novelfull needs flaresolverr. I also needed to bump up timeouts recently when testing a similar report.

[novelfull.com]
use_flaresolverr_proxy:true
slow_down_sleep_time:7
## flaresolverr_proxy_timeout is in integer milliseconds.
## Keep flaresolverr_proxy_timeout set smaller than connect_timeout
## otherwise the connection *to* flaresolverr will timeout first.
flaresolverr_proxy_timeout:59000

[AzureSuperuser]

Originally Posted by JimmXinu

novelfull needs flaresolverr. I also needed to bump up timeouts recently when testing a similar report.

[novelfull.com]
use_flaresolverr_proxy:true
slow_down_sleep_time:7
## flaresolverr_proxy_timeout is in integer milliseconds.
## Keep flaresolverr_proxy_timeout set smaller than connect_timeout
## otherwise the connection *to* flaresolverr will timeout first.
flaresolverr_proxy_timeout:59000

Sorry quite new to this.
Is there somewhere I am supposed to put this code?

[ownedbycats]

personal.ini. Access from config, or menu option.

[MidnightRose]

Originally Posted by JimmXinu

The images are displayed smaller due to height / width attributes on the <img> tags. Those attrs are discarded by FFF. You could keep them using keep_html_attrs (search for keep_html_attrs and add_to_keep_html_attrs), but that would apply to all tags.

Oh thank you so much for this. This was actually exactly what I needed for some of the formatting to show up in one of the stories I'm following.
As shown here
And the image size tags plus

nook_img_fix:false

fixed the images issues quite nicely.

[JimmXinu]

Originally Posted by MidnightRose

Oh thank you so much for this. This was actually exactly what I needed for some of the formatting to show up in one of the stories I'm following.
As shown here
And the image size tags plus

nook_img_fix:false

fixed the images issues quite nicely.

Anyone have a Nook they can test with and see if nook_img_fix is needed anymore?

That option is for a Nook only limitation like 10 years ago.