Quote:
Originally Posted by AbyssalAriel
I know I need to put it under [archiveofourown.org], but I'm not sure about the syntax, because it's a Yes/No column.
|
Yes/No columns will be set True if the metadata entry is in ('t','true','1','yes','y'), False if in ('f','false','0','no','n') (case insensitive) and set 'None' for tri-state columns when any other value.
So you need to replace Competed and In-Progress to t/f or y/n etc if you want to use a yes/no column. I'd recommend making another extra entry, copy status, etc again before changing it.
Quote:
Originally Posted by AbyssalAriel
If I only set it the column for AO3 stories though, it won't try to overwrite stories from other sources yeses or nos with "undefined" or some other default, right?
|
Shouldn't. If it does, I'd like to hear about it.
Quote:
Originally Posted by AbyssalAriel
Question, does all this stuff get saved along with the other normal story metadata?
|
No. Only the original collected metadata is saved in the Saved Metadata column, everything is recreated from the original data and the configuration.
Quote:
Originally Posted by AbyssalAriel
How would this stop ordering entries in the list?
|
The
make_linkhtml_entries feature is a bit of a kludge. It relies on the newentry and newentryUrl lists having corresponding values. Therefore, newentry has to be kept in original order or else the newentryUrl entries won't line up correctly.
Quote:
Originally Posted by AbyssalAriel
And how does AO3 tagging being a mess affect it?
|
Mostly because it makes me leery of anything and everything to do with it.
AO3 has 4 different sets of tags which FFF users expect to be separate and stories routinely have dozens or even hundreds of tags. And most users want at least chars & ships sorted.
Quote:
Originally Posted by AbyssalAriel
Phrasing it that way sounds like it's not a technical barrier, and for design philosophy it doesn't seem any conceptually different from updating calibre's metadata using the same saved data column.
|
Here are some of the posts from the discussion:
https://www.mobileread.com/forums/sh...01#post3842401
https://www.mobileread.com/forums/sh...postcount=3407
https://www.mobileread.com/forums/sh...postcount=3425
The final conclusion was:
Quote:
Originally Posted by JimmXinu
I have spent waaay more time (including another hour today) than this corner case can justify trying to fit this into the existing system in way that both works 'as I expect to' and without breaking anything else. I give up. 
It's not like there isn't already a way to do it, it's just not as efficient. Use 'Update EPUB always', or don't; it's your choice. |