Library Stuff.

[pperrin]

Hi

Progress has been made!

Good ideas/input from Craig and Ollie - and some v.persistent dev work
form Craig has given a proof of concept of the underlying web-services
required for the planned architecture.

The initial aim is to get to the point where people are allow(/
encouraged) to log when they use a book - simply by scanning the
barcode (with a smartphone or similar) and sending it by web, txt or
email - once this register is in place the stock and issues can be
managed, and all good thing flow from there.

There are more gaps to fill - Identifying users from the source of the
message (web (browserid), txt (phone number) or email (from address))
automatically - and what info about the user of a book gets published
in the public catalogue (email address?, twittername? anonymous unique
ID?).

Hopefully work out hot to consult on these soon?

Cheers

Paul /)/+)

[Thomas Parslow]

Well done guys!

Maybe the profiles app can help with identifying users, we could allow lookup of user by any publicly shown detail.

It would be great to see this up and running, how much extra work do you think there is in it?

Tom

--

Thomas Parslow
Freelance Developer
Django, Python, Javascript and more!

http://almostobsolete.net
+44 (0) 7951261227
@almostobsolete

[paul perrin]

Hi Tim

Sounds good - ultimately I'd expect the library app to get messages by text/web/email - so need an way of using this (source mobile number, browserID, email address) to look someone up, and get an identifier that people are happy to have 'published' as 'checked out to' in the library software.

Functions for updating librarything, twitter and google docs are lined up - needs functions to hit the 'profile app' and use browserID - and then a days work may get a web based check in/out done.

Regards

Paul Perrin
Immediate Data Ltd
Land: 01273 301512
Mob: 07798 505043
Email: pa...@idltd.com
http://www.idltd.com
ASP and .NET website software, service and skills

[Thomas Parslow]

What do you think about sticking QRCode (2d barcodes) on the books? There are QRCode apps for loads of phones and we have each QRCode encode a URL to a checkout page. Thus we wouldn't need to any specific phone software, much quicker and easier!

Tom

--

Thomas Parslow
Freelance Developer
Django, Python, Javascript and more!

http://almostobsolete.net
+44 (0) 7951261227
@almostobsolete

[C James]

Hi Tom,

Where do I go to see what's been progressed so far? Being a Werker I'm not a paid Skiffer, so I might not have access privileges?

I was speaking to Pete today, and we're all really busy, but I'm keen to stay in the loop and get involved if I can.

Regards

... Chris James

05creative Ltd
The Werks
45 Church Road
Hove
East Sussex BN3 2BE

t. 01273 900874

www.05creative.co.uk

[paul perrin]

Hi 

I had a look at QR codes originally - the size and url links were good - but for the bulk work (like shelf/stock checking) a dedicated bar-code reader wins hands down - like scanning at a check out... beep, beep, beep etc. very quick - with a couple of hundred books, small differences add up.

A QR code on the back/front could work (people reading them will have taken them off the shelf already).

I was thinking of having QR codes on the wall - to take people to the 'check in/out' webpage where they could then scan the actual barcode - a bit of a hybrid system. There seems to be a lot of software for phones to read bar-codes in shops (check for best deals etc) so I don't think phones have a problem with normal codes - its just making the check in/out as simple as possible (without making admin harder!).

Once the software is done (need to sort out the user lookup to log the book to - has anyone got code for that?) we can have a play with different phones/software to see what works - if the first interface is a qr code to a 'check out page' to then scan the actual code I guess the identification will be the browserId on the smartphone browser...

Cheers!

Paul