Quote:
Originally Posted by JimmXinu
I would also comment that rather than deleting the book, you could probably clear the tags field. Since you didn't give any example story URLs, I assume you're happy with your solution.
FFF does a filter to make sure it doesn't try to add the same tag with different letter case, but only when 'Keep existing tags' is checked.
Calibre, on the other hand, keeps a database table of tag values for the whole library; and it only wants you to have one 'case' version. If you manually change it, Calibre appears to change the case for that tag on all books. But if you do it through FFF, calibre will map it to the same case as it's existing tag.
|
Yes, I am happy with figuring out the solution for this issue - I still don't entirely understand why needing to clear out the existing tags is necessary and how updating vs initial import handles tags differently, but I can read through the scripts and documentation in more detail and perhaps find more info there if I really want to know - the explanation regarding how FFF vs Calibre handles tag helps with understanding the 'case' issue, thank you
Quote:
You can only set extra_valid_entries to custom columns using the personal.ini custom_columns_settings setting.
From (plugin-)defaults.ini:
Spoiler:
Code:
## (Plugin Only) - You can also populate calibre custom columns with
## the site specific metadata using custom_columns_settings (but only
## if 'Allow custom_columns_settings from personal.ini' is checked in
## the plugin GUI config.) There are three parts, the entry name,
## then the label of the calibre custom column, then (optionally) a
## 'mode'. 'r' to Replace any existing values, 'a' to Add to existing
## value (use with tag-like columns), and 'n' for setting on New books
## only. (Default is 'r'.)
## Literal strings can be set into custom columns using double quotes.
## Each metadata=>column mapping must be on a separate line and each
## needs to have one space at the start of each line.
## 'r_anthaver' and 'n_anthaver' can be used to indicate the same as
## 'r' and 'n' for normal downloads, but to average the metadata for
## the differents story in an anthology before setting in integer and
## float type custom columns. This can be useful for a averrating
## column, for example. Default is to sum the values of all stories,
## and numChapters and numWords are always summed.
#custom_columns_settings:
# cliches=>#acolumn
# themes=>#bcolumn,a
# timeline=>#ccolumn,n
# "FanFiction"=>#collection
# averrating=>#averrating,r_anthaver
|
Ok, so custom_columns_settings essentially initiates the column 'variable' that I can then apply filtering to - got it to work now, thank you
Quote:
Set sort_ships:true
From (plugin-)defaults.ini:
|
Got it, didn't realize that was buried in the default, and it works on & as well, thanks for pointing it out!
Quote:
I only support the latest version of FanFicFare. There is usually a more recent test version available, too; see link in my sig.
I will make some effort to support the last minor of each major calibre version back to v2 (so v2.85.1, v3.48 and v4.23).
However, I don't make it a habit of testing against older versions (or OS's other than Win10) unless I have reason to do so, like a specific complaint.
Unless a user tells me otherwise, I assume everyone is using the latest FFF on the latest Calibre.
Yes, there is a github repo with all the past releases:
From the first post of the thread:
|
Yes, I know about the repo with past releases - I was asking about an updated page that mentioned major changes that may affect version compatibility, or any other major announcements regarding updates, it doesn't sound like that exists so I will just reference the repo and revert to a previous version if I come across any issues that may be related to an update
Thank you for creating and providing this tool, I appreciate the quick responses