View Single Post
Old 10-25-2022, 11:12 AM   #7654
dailyalice
Geek of All Trades
dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!dailyalice rocks like Gibraltar!
 
dailyalice's Avatar
 
Posts: 55
Karma: 100878
Join Date: Aug 2012
Location: Minneapolis
Device: Kindle Oasis (3rd gen)
Quote:
Originally Posted by JimmXinu View Post
Calibre has a feature where it makes incoming tags (from FFF*) matches existing tags, case-wise.

This is a bit of data-normalization to save space, plus a way to help users keep matching tags.

So I believe, if you search your library, you'll find "Man from Uncle" is an existing tag on an existing book.
Thanks for the quick response!

Huh. Since I have two columns for Fandoms in my library and I'm only changing one of them, the column with fandoms as they are on AO3 still had "Man from Uncle - Fandom" as tags for two works. (Basically I change category tags using replace_metadata in personal.ini to populate my main fandoms column, but I also put AO3's "fandoms" into a separate column "Fandoms (AO3)" so I have both my cleaner list and AO3's full list.)

So I'm guessing that Man from Uncle - Fandom was the hangup, even though it was in a different column. I changed that to Man from UNCLE - Fandom and also manually changed the category to Man from UNCLE.

Quote:
Originally Posted by JimmXinu View Post

* It also used to work that way when manually editing tags. It looks like Calibre now (v6.7.1) updates the tags on all books when you change the case on one.

So if you change that 'Man from Uncle' in your library to 'Man from UNCLE' on one book, it should change for all books. If it doesn't, use the Tag browser or search and replace to do that and then try it with FFF again.
I like that changing case on one tag in your library now fixes them all. That's handy (and good to know.)

I was able to update the rest of my Man from UNCLE works from Saved Metadata and they're now all Man from UNCLE.

Going forward, I'm guessing this will work. I should think any future instances of "Man from Uncle - Fandom" will be changed thanks to personal.ini, but i'm only changing them in category not fandoms. But i'm guessing the preferred capitalization will be what is in the library.

. . . And I just tested this by finding a really old work on AO3 that still had "Man from Uncle - Fandom" as the fandom. Downloaded it and the category change worked (to Man from UNCLE) and the data downloaded to the AO3 fandoms column reads "Man from UNCLE - fandom" instead of "Man from Uncle - fandom" as it is on AO3. Huh.

So I guess whatever capitalization that is in the tags that are in my library first wins? (But then if I change tags in my library, going forward they'll show up consistently in my library the way I like them. Though the point of the few AO3 specific custom columns I have is to retain the data as it exists on AO3; I guess I'll have to assume capitalization won't necessarily match the archive, which is fine. The AO3 data is still in Saved Metadata.)

Huh. This might explain why so many character names have had the correct cases; I've been adding lines to my personal.ini as I come across names that are misspelled or aren't capitalized correctly and have been surprised I haven't had to do that as much as I did in older libraries. Neat. I guess that's something I don't have to bother with using replace_metadata if I get the names capitalized correctly in my library initially.
dailyalice is offline   Reply With Quote