Quote:
Originally Posted by Shadewing
First, I love this plug-in  . I've been using it and its predecessor for a while and they are great! |
Glad you like it.
Quote:
Originally Posted by Shadewing
I don't know if anyone else would find this useful but I'd like to see a 'previously updated' metadata value. It would basically be whatever was in the 'Updated' field before the new update.
|
You can, by checking the "Pass Calibre Columns into FanFicFare on Update/Overwrite" checkbox on the personal.ini tab and adding the special metadata name for your updated field to
titlepage_entries or
custom_columns_settings (etc). Note that this only works with actual EPUB updates or overwrites, not update metadata only settings.
But have you looked at the logpage settings? Only works with EPUB, but I like having a record of all the past updates, when they happened, how many words, did they change the title?, etc, etc. I've attached an epub (trimmed for size and content) with a logpage from my library as an example.
This was a feature I added for my own use that I've always been a bit surprised isn't more popular.
Code:
## Default settings, logpage is OFF by default:
## include a Update Log page before the story text. If 'true', the
## log will be updated each time the epub is and all the metadata
## fields that have changed since the last update (typically
## dateUpdated,numChapters,numWords at a minimum) will be shown.
## Great for tracking when chapters came out and when the description,
## etc changed.
## Plugin will now preserve the log page when the epub is overwritten,
## too.
include_logpage: false
## If set to 'smart', logpage will only be included if the story is
## status:In-Progress or already had a logpage. That way you don't
## end up with Completed stories that have just one logpage entry.
#include_logpage: smart
## items to include in the log page Empty metadata entries, or those
## that haven't changed since the last update, will *not* appear, even
## if in the list. You can include extra text or HTML that will be
## included as-is in each log entry. Eg: logpage_entries: ...,<br />,
## summary,<br />,...
logpage_entries: dateCreated,datePublished,dateUpdated,numChapters,numWords,status,series,title,author,description,category,genre,rating,warnings
## Here's what I personally use:
[epub]
include_logpage: smart
logpage_entries: fulldownload,dateCreated,datePublished,dateUpdated,numChapters,numWords,status,version,title,storyUrl,series,author,category,genre,rating,warnings,description
# so overwrite downloads have some marker.
add_to_extra_valid_entries:,fulldownload
include_in_fulldownload:title
fulldownload_label:New Download
add_to_replace_metadata:
fulldownload=>^.*$=>Yes