View Single Post
Old 04-16-2011, 07:09 AM   #68
ldolse
Wizard
ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.
 
Posts: 1,337
Karma: 123457
Join Date: Apr 2009
Location: Malaysia
Device: PRS-650, iPhone
Getting around to porting this now that the new framework is usable enough for general testing.

Does the new framework differentiate between 'identify' and social metadata? Just asking because thus far all the plugins list only 'identify' and/or 'cover' in the capabilities.

capabilities = frozenset(['identify', 'cover'])

The way Overdrive works there are three ways to get data:
'identify' - Search overdrive and get a list object back with various metadata.
'cover' - comes from the same search as above, but use a separate function to populate the cover url cache from those results.
'social metadata' - Or whatever it's equivalent might be considered in the new framework - go to the actual book page and scrape for further details not included in the identify results.

I would think that for many metadata providers this might be the way things work, even if it requires scraping - fuzzy search returns a list of results which already contain some metadata, full metadata by going to the book identifier's actual page.

Scraping the book details page is actually the slowest in the case of Overdrive, so I was thinking to make it optional and disabled by default. Not sure if the listed capabilities is the way this will be managed or if I should configure similar to .7.x metadata plugins.


The other way to do it, based on reviewing the new GUI, is to default disable the specific fields that require the book record to be loaded. This looks like the 'touched_fields' configuration in the plugin, but that only adds them to the list - will it be possible to default disable them?

Last edited by ldolse; 04-16-2011 at 07:11 AM.
ldolse is offline   Reply With Quote