[GUI Plugin] FanFicFare

[JimmXinu]

Unfortunately, the short answer is that FFF doesn't support Safari for the BrowserCache feature.

FFF supports two flavors of cache for Chromium browser and third for FireFox. I haven't found an implementation of reading Safari cache. I don't recall how hard I looked at the time, but I'm not finding anything now.

[booster-t]

OK thanks ... I expect Apple to fix this soon, but until then ..,. what a pain

[ownedbycats]

I have a custom column, #admin_tags. If an update comes up as 'story does not exist,' would it be possible to add a (site-specific) entry like 'removedfromsite:ao3' to this column? I don't think there's a metadata entry for errors.

[JimmXinu]

Errors are not included in story metadata as defined by FFF.

There's an option on the Custom Columns tab to save errors to a custom column.

If you set that, the combination of publisher:archiveofourown.org and #errorcol:"Story does not exist" will give you that and you can add it or create a custom column 'built from columns' as you like.

[ownedbycats]

Yes, I already have a #fanficerror column.

I did set the error column to #admin_tags to test, but it overwrote existing entries. Can FFF not differentiate between regular text columns and taglikes? I was expecting it to either add or just not be available in the dropdown.

EDIT: Checking up on Calibre's db structure again shows that both are type 'text,' though taglikes has 'is_multiple' enabled.

Perhaps an 'add' checkbox in the custom columns settings would work, but I can't think of many use cases for this to be worth adding.

[JimmXinu]

The custom_columns_settings has three modes, 'r' for replace(default), 'n' for new books only and 'a' for add to existing values.

[ownedbycats]

Originally Posted by JimmXinu

The custom_columns_settings has three modes, 'r' for replace(default), 'n' for new books only and 'a' for add to existing values.

Yes, but you can't use errors in custom_column_settings...

[JimmXinu]

Forgot we were talking about errors.

I honestly don't see the point. You have the site available, you have the error available. Data normalization recommends against making a new column for data that can derived from existing data.

[ownedbycats]

In that case, I can just use a template to populate #admin_tags - check for a 'story does not exist' in #fanficerror.

[ponpos]

If I want to store metadata in tags with a certain format without affecting the original metadata, how do I do that?

More specifically: Let's say "ships" has "A/B". In tags, I want "SHIP - A/B", but if I use replace_metadata, then the first page of the epub includes "Relationships: SHIP - A/B" which is not ideal. Is there a way to format the tag like I want without affecting how it shows in the epub?

[ownedbycats]

A copy category. Here's one I use, specifically to copy categories to tags:

replace_metadata: 

## tagcategory standardization
 tagscategory=>(Portal|Half-Life)=>Half-Life & Portal
 tagscategory=>(Mass Effect: Andromeda|Mass Effect Trilogy)=>Mass Effect

## Sorts anything other than a few selected categories into "Fanfiction.Other"
 tagscategory=>^(?!.*(Half-Life|Portal|Mass Effect|The Elder Scrolls|Crossover)).*$=>Other

## Adds Fanfiction. to the beginning of tagcategory
 tagscategory=>^(.*)$=>Fanfiction.\1

# 'add_to_' concats on to existing param, thus the leading comma
add_to_extra_valid_entries:,tagscategory

# tagscategory is a copy category for Fanfiction.category in tags
include_in_tagscategory:category
include_subject_tags: tagscategory

In your case, I think you'd want to copy ships to, e.g. shipscolumn, apply your transformation to shipscolumn, then use custom_column_ships to apply it to #yourshipcolumn.

[ponpos]

Thank you so much! Worked like a charm.

[ownedbycats]

Also I meant custom_columns_settings, not custom_columns_ships.

[criscros]

I just figured out why I shouldn't do that, never mind.

[LadyLight]

Originally Posted by ownedbycats

Question: Some AO3 authors include both "CharacterA/CharacterB" and "CharacterA & CharacterB."

Has anybody made a in/exclude_metadata regex + conditional that can strip out the later without making separate lines for every possible ship? (Is it even possible?)

I have the same question.

add_to_replace_metadata:
 ..
 ships=>(.*)[&](.*)=>\1 and \2

almost works. but then the output looks like:

<CharacterA> and amp; <CharacterB>