This could definitely be a viable option. Identified in this video as an emerging technology. We could even implement it in both the form of in the ID card, or using the existing technology in some smartphones
Monthly Archives: October 2012
Over the last few days we have been all working on different design tools to aid in the refinement and development of our system.
As a result we have thus questioned the need for a device to assist library use. The main purposes of a device would be to login, and to direct the user to the physical location of a book.
As the way of the future is probably going to be digitally based, and there will be even less need for navigation around the physical space we concluded that it was not necessary to have an additional device. But to instead simplify the current login system and focus on the online interface, and the rewards system that we have devised.
Things that we have discounted:
USB device (will eventually be outdated as do most storage technologies)
Additional device (could get lost easily, and people may not generally carry it with them)
The physical navigation system (gps to find book) as thinking practically about it, people are generally familiar with the section that they are looking for a book in, it would only really be necessary for new library users.
Things that we made more defined:
We have decided to use audio barcodes to log users into the system. These would be issued at acceptance into uni, and can be stuck to anything that the person decides. Could be mobile phone…id card…eftpos card or whatever they feel is appropriate and something that they will always have with them at uni. This gives people a sense of control, they can personalise to some extent how they interact with the system. The audio barcode also has audio-haptic feedback and is interactive, involving the user in the logging in process.
We discussed the problems possibly arising from a security perspective. There is the possibility of people losing their login codes, and thus there could be security issues as other people could login to their accounts. The only perceivable solution would be you still need a login password; however we identified that people would have more respect and take more care of the ‘login sticker’ if it simply logged you straight in. In the case of losing your code you would be issued a new one; not unlike what happens with a credit card.
Immediate login with the code speeds up the process and makes it much easier for users.
We also discussed the details of the rewards system. Identifying that there would be a points tally; you receive points for returning a book on time, participating in tutorials put on by library staff and for rating/reviewing books.
rating and reviewing
>would be peer reviewed by someone else, this is when you would receive the points, hence adding a layer of reliability to the rating system.
Another idea regarding rewards is that you could use x amount of points to enter a monthly competition, for a prize like an ipad or e reader etc
Looking at gamification:
Status– More you review have top scholar
Access– Could give you access to an exclusive area
Power– you have the power to allocate others points by recommending/ verifying their comments
Stuff– coffee, internet and printing credit
Moving forward we will continue to use our development tools
Importance of the device?
– navigation around the physical space
– login to the digital system
Should we be questioning the need for the device, is it an unnecessary addition to the system?
Blueprinting demonstrated the fact that the links between each of the domains we were hoping to integrate (rewards, online and navigation) are very weak.
Is navigation of the physical space reason enough to necessitate a new device?
Looking at our key insights, possibly not. The simple interface online and the rewards system fulfill the brief we have and our aims for this project. Navigation of the physical space is generally fairly easy once you are familiar with the library and have been there a few times. The addition of clear and simple maps would suffice. These could be touch screen panels that are voice activated, or could also be static 2D images.
This is a cool example of how a system could be conveyed visually. so nice and simple
Communicate well the way that all parts of the system are integrated.
Well resolve the sub-systems.
Be careful of testing the concepts, use role playing, blueprints etc
Effectively go through each stage of the system
Further resolve the way that the system will work in the future,
Look at new technologies and how they could be integrated into our own system
http://www.flickr.com/photos/bjdawes/2671013162/in/set-72157606180439879/ << web development sketches
http://iclarified.com/# << Nice and simple
W ordpress reader is also pretty good