[GUI Plugin] FanFicFare

[jesscat]

I have been using the Saved Metadata column for my experimenting, but couldn't figure out where bookmarkprivate (or bookmarkrecs for that matter) are. I don't see either of them, even though I have always_login set to true.

Assuming that part gets worked out, I think I need a little more help in figuring out how to use custom_column_settings to achieve what I want to do with a boolean field, because I think I'm missing something from your explanation. Where do the yes/1/true values fit in to custom_column_settings? Would I just do something like this [assuming #my_bookmarks is my yes/no column for whether a story is bookmarked]:

custom_columns_settings:
 bookmarkprivate=>#my_bookmarks

...though actually what I really want is for the #my_bookmarks custom column to be set to true if bookmarkprivate is true *or* false, and to be set to false if bookmarkprivate is undefined.

[JimmXinu]

New Test Version Posted

2018-04-13
- Fix for saved custom column metadata and boolean values.

Originally Posted by jesscat

I have been using the Saved Metadata column for my experimenting, but couldn't figure out where bookmarkprivate (or bookmarkrecs for that matter) are. I don't see either of them, even though I have always_login set to true.

They only appear in saved metadata if true for a story, so technically they never have a false value.

Originally Posted by jesscat

Assuming that part gets worked out, I think I need a little more help in figuring out how to use custom_column_settings to achieve what I want to do with a boolean field, because I think I'm missing something from your explanation. Where do the yes/1/true values fit in to custom_column_settings? Would I just do something like this [assuming #my_bookmarks is my yes/no column for whether a story is bookmarked]:

custom_columns_settings:
 bookmarkprivate=>#my_bookmarks

That should work, unless you have tri-state booleans on.

Originally Posted by jesscat

...though actually what I really want is for the #my_bookmarks custom column to be set to true if bookmarkprivate is true *or* false, and to be set to false if bookmarkprivate is undefined.

All you really get from bookmarkprivate is True or undefined. I'll consider if it could be changed to be true/false/undefined(no bookmark).

[jesscat]

Okay I misunderstood. What I want to do won’t work - since none of my bookmarks are private (or recs), bookmarkprivate will always be undefined for me on all stories, whether or not I have them bookmarked. Does AO3 provide a field indicating simply whether a story is bookmarked by the logged in user? Is there another way I’m missing to separate out my bookmarked stories from non-bookmarked ones (so I could create a custom column that would mark the bookmarked ones)?

Thanks!

[JimmXinu]

New Test Version Posted

2018-04-13
- Fix for saved custom column metadata and boolean values.
- Add bookmarked site specific metadata for adapter_archiveofourownorg.

Originally Posted by jesscat

Okay I misunderstood. What I want to do won’t work - since none of my bookmarks are private (or recs), bookmarkprivate will always be undefined for me on all stories, whether or not I have them bookmarked. Does AO3 provide a field indicating simply whether a story is bookmarked by the logged in user? Is there another way I’m missing to separate out my bookmarked stories from non-bookmarked ones (so I could create a custom column that would mark the bookmarked ones)?

I'm not sure why the AO3 adapter was collecting 4 other pieces of bookmark metadata without a simple bookmarked entry. It may have been harder to tell at the time, or simply the user who wanted those didn't ask for it.

But bookmarked should now do what you want (after installing the test version, of course).

[jesscat]

But bookmarked should now do what you want (after installing the test version, of course).

This works perfectly! Thank you!!!

[jesscat]

So I have another question... I understand that the meta information + additional AO3 meta information gets dumped into the tags: fandom, ship, characters, ao3categories, freeformtags, etc.

Is there any way to specify an order for these meta items so they aren't all mixed together alphabetically in the tag list? So, say, fandom is listed first, then characters, then tags, then ao3categories? I don't care so much about the order within each item (like that the characters are kept in their original order), just overall - that, e.g., characters are listed before freeform tags. Since the columns aren't wide and there are only a few items visible, and AO3 often has a proliferation of ridiculous freeform tags, I'd like to always be able to scan the beginning of the tag list to see the important stuff, the way I can on the site.

I know I could create custom columns for each of these different metadata categories, but I don't know that I care enough to do that - keeping the list in order would be sufficient if it was possible. I'm thinking maybe it can't be done, that once they are all included in subject_tags the different categories can't be separated out within the tag list anymore, but I thought I'd ask!

[JimmXinu]

Originally Posted by jesscat

... Is there any way to specify an order for these meta items so they aren't all mixed together alphabetically in the tag list? So, say, fandom is listed first, then characters, then tags, then ao3categories? ...

FFF has options for not alphabetizing its list type metadata entries. Eg, if you set keep_in_order_characters:true, it will not order characters.

But as I recall, Calibre always alphabetizes tags, so keep_in_order_* would only help with custom columns--and even then only non-tag type custom columns.

The only solution that comes to mind is to use replace_metadata to put a sort of label at the front of each item that will force the ordering you want:

replace_metadata:
 category=>^(.*)$=>0 \1
 characters=>^(.*)$=>1 \1

[ilovejedd]

Originally Posted by JimmXinu

But as I recall, Calibre always alphabetizes tags, so keep_in_order_* would only help with custom columns--and even then only non-tag type custom columns.

That behavior has changed in later Calibre versions (dunno when exactly). It still shows tags alphabetized in the library and book details view. However, it does use original tag order for templates, edit metadata, etc.

I've found the new behavior pretty useful for determining main characters or ships.

[jesscat]

I've found the new behavior pretty useful for determining main characters or ships.

If you don't mind my asking, how do you use it for this purpose (to determine main characters/ships)? That might be sufficient for me.

[ilovejedd]

Originally Posted by jesscat

If you don't mind my asking, how do you use it for this purpose (to determine main characters/ships)? That might be sufficient for me.

I have separate custom columns for ships, characters and other tags so in the first place, they're not just all jumbled together in the standard tags field.

First, I select books I need for metadata clean up. Then I go to bulk metadata edit and use a saved search that copies the first tag (or first few tags) to a custom column containing "normalized" values.

The method isn't 100% accurate (particularly with drabble collections) but it seems to work well enough for the most part.

Mind, even with the automation utilities available, AO3 tag wrangling still takes a lot of effort. I even use Excel+Job Spy for normalizing tags because with all the rules I have, my personal.ini would become unmanageable.

[jesscat]

But bookmarked should now do what you want (after installing the test version, of course).

I think there's an issue. When I update metadata from saved metadata column, the "Bookmarked" field disappears completely from the saved metadata file. This happens to me for any story in my library, no matter the value of the bookmarked field, and regardless of whether the changes I'm making affect that field.

[JimmXinu]

New Test Version Posted

2018-04-13
- Fix for saved custom column metadata and boolean values.
- Add bookmarked site specific metadata for adapter_archiveofourownorg.
- Fix for PI saved metadata not reading False & empty strings.

Originally Posted by jesscat

I think there's an issue. When I update metadata from saved metadata column, the "Bookmarked" field disappears completely from the saved metadata file. This happens to me for any story in my library, no matter the value of the bookmarked field, and regardless of whether the changes I'm making affect that field.

You are apparently the first person to try to use those settings that way, so you get the find the bugs. Congratulations!

Honestly tho, there are very few boolean metadata values in FFF. Most are strings, lists of strings, numbers or dates.

[jesscat]

Oh no problem! I don't mind debugging!

(Also, just to let you know, your dates for the latest test versions in the second post all have 2018 as the year....)

I have always liked using tristate boolean columns in Calibre. Getting them to work with FFF is stumping me a little, probably because of my own ignorance. For example: what I really want is for my "bookmarked" column to have a checkmark if the story is bookmarked but to be blank otherwise, *not* to have a red X. My basic custom column setting:

custom_columns_settings:
 bookmarked=>#my_bookmarks

doesn't accomplish this - "bookmarked" is set to "False" for non-bookmarked stories and so this ends up with a red X in the column for those stories.

Since my #my_bookmarks custom column is a tri-state column, I thought I could get what I wanted by adding this:

replace_metadata:
 bookmarked=>false=>empty

or

 bookmarked=>no=>empty

I also tried using "blank" instead of "empty," and even putting nothing there at all:

replace metadata:
 bookmarked=>false=>

None of these work. Any ideas why not?

It's really not that critical, I'd just like to understand better!

[JimmXinu]

I think you just need capital 'F' False.

replace_metadata:
 bookmarked=>False=>

By the time it hits replace_metadata the bool has been changed to a string and Python like False and True.

[jesscat]

I think you just need capital 'F' False.

Nope, that doesn't work either - I had actually tried that!