Quote:
Originally Posted by chaley
This sounds like an interesting use of series-type fields, one that I hadn't thought of. It sounds like you made a series column called (say) Awards. You then create a series for an award, say Nebula, and apply that series to books winning the Nebula. The series index is the year the book won the award, so some book might have Nebula [1993]. Do I have this right?
|
You have it exactly right. I started with Calibre in order to organize my books. Then I found it was no trivial task to get them all into Calibre, and I began to write code to solve minor problems with the adding process (Merge books, autosorting for similar author/title, etc.).
At last I'm at the stage where I'm actually trying to label books in ways that let me find what I want. Genre tags are what I mostly use, but recently I decided to identify books that have won an award or been nominated for one ("Hugo Nominated" and "Hugo" in #award, etc.).
Quote:
|
If I am right, then what do you do when a book wins two awards?
|
You're always causing trouble aren't you
1) Currently I pick the award I like best, put the other into comments and tags. All awards are also in the tags.
2) I may decide I need an #award2 and an #award3 column for overlaps. It would complexify searching, however.
3) I've considered a separate date-type column for each award, rather than my current system.
I've only added a few awards, and they haven't overlapped. I have overlapped some nominations in one year, with a win for the award the next year - I just use the actual year it wins.
As an aside, your custom columns are incredibly useful, even where I also have the data in tags.