Barcode Scanner

[GoogleCodeExporter]

Write a plugin that scans barcodes and creates the book in the database.

I have done it before, should be semi-trivial.

Original issue reported on code.google.com by roberto.alsina on 28 Jan 2011 at 4:45

[GoogleCodeExporter]

I like this because it will allow me to use Aranduka to keep a database of my 
physical library. Should we show differently eBooks (of which we have the 
files) and regular (or virtual, since Aranduka doesn't know where the actual 
book is) books?
If we have physical books we may want to let the user define some sort of 
identifier so that he can find the book in his library.

Original comment by andresgattinoni on 28 Jan 2011 at 5:30

[GoogleCodeExporter]

I can add a "this book is physical" flag in the identifiers. And then we can 
use that for filters, or emblems.

Original comment by roberto.alsina on 28 Jan 2011 at 5:32

[GoogleCodeExporter]

I don't know if it should be in the identifiers or as another field of the Book 
table. What I meant about the identifiers was that if I add the books on my 
library I may want to invent an identifier like "2R0025" (to remember me that 
the books has the number 0025 and it's in the 2nd row or shelf of my library).

Original comment by andresgattinoni on 28 Jan 2011 at 6:42

[GoogleCodeExporter]

The idea of the identifiers field is precisely "a way to add things we don't 
know about beforehand". But sure, we can add another field, instead.

Original comment by roberto.alsina on 28 Jan 2011 at 7:04

[GoogleCodeExporter]

Another two possibilities:

- A book that's not associated to any file is a *real* book.
Or
- A book that's associated to a *virtual* file is a *real* book.

I don't know, I'm not completely comfortable with any of the posibilities. 
Is it possible that I have the same book in PDF and in paper? What happens 
there?

Original comment by andresgattinoni on 28 Jan 2011 at 7:14

[GoogleCodeExporter]

Of course you can have the same book in paper and PDF. That's why you can't say 
a book with no file is a real book.

You may also create a book and tag it as "to read" to remember you want to buy 
it later, for example.

I don't understand what a virtual file would be in this context.

Original comment by roberto.alsina on 28 Jan 2011 at 7:20

[GoogleCodeExporter]

The "virtual" file would be a record on the File table for a physical book. But 
it doesn't make much sense. Maybe it would make more sense if instead of a File 
table it was a Location table. So you can have the same book in different 
locations, one could be a PDF file and another could be "the third book from 
the left in the second shelf".

But if we can also have "to-read" books, maybe the way to go is to leave 
everything as it is and let the user add a "Physical book" tag if he wants to 
and a custom identifier for "third book from the left in the second shelf".

Original comment by andresgattinoni on 28 Jan 2011 at 7:26

[GoogleCodeExporter]

And I can add that tag automatically when the file is imported using the 
barcode scanner.

Original comment by roberto.alsina on 28 Jan 2011 at 7:55

[GoogleCodeExporter]

Cool. We could define a set of default tags that the user can later edit (like 
GoodReads' shelves).

Original comment by andresgattinoni on 28 Jan 2011 at 7:59

[GoogleCodeExporter]

Yes. In fact, we could use exactly those ;-)

Original comment by roberto.alsina on 28 Jan 2011 at 8:04

[GoogleCodeExporter]

Initial plugin merged into integrate branch. Still needs lots of love.

Original comment by roberto.alsina on 28 Jan 2011 at 9:53

[GoogleCodeExporter]

This is looking good, really. It *almost* works well.

TODO: an explanation when zbarcam starts so the user can understand how it's 
used
TODO: get the ISBNs line-at-a-time instead of all in one batch, so the user can 
scan->import scan->import etc.

Other than that, I think it's not horrible!

Original comment by roberto.alsina on 3 Feb 2011 at 2:07