View Single Post
Old 10-12-2013, 12:12 PM   #5
eggheadbooks1
Read, don't parrot.
eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.eggheadbooks1 figured out that Keyser Söze was the Kevin Spacey character in less than 20 minutes.
 
Posts: 224
Karma: 110242
Join Date: Apr 2011
Device: Kindle Fire, Kobo Touch, Aldiko for Android
Yes, I am aware of that. But KWL, for example, does not have a field to input keywords but the programmers are looking at ways to use embedded keywords to assist searching -- so the keywords have to be in the metadata. Then there is the problem that, while you can input BISAC codes when uploading your file to, for example, Amazon, some BISAC codes are not used by Amazon yet factor into search results. So once again, it's better to have it in the metadata. And finally, as noted in my earlier post, if you use an aggregator you may not have any means to input keywords and BISAC codes. Thus, the ability of the author to input such integral information into the metadata would be a huge step forward.
eggheadbooks1 is offline   Reply With Quote