Bounties
From Dev8D
This is the page for Prizes, Challenges and Bounties for Dev8D 2011
Rules:
1. Entries should have at least one developer, though we encourage teams to participate.
2. The entries must be presented, in person, at Dev8D 2011. Not all of the team members need be present at Dev8D 2011, but at least one team-member must be.
3. Teams must register their entry / idea using this page of the Dev8D 2011 wiki. Teams can enter before the conference and may change their idea/entry up to the deadline.
4. Deadline for Entry is 2pm Thursday February 17th, 2011
5. All Challenges will be judged by the challenge 'givers' and selected group of developers between 2pm and 3pm on Thursday 17th 2011 in private. Each entrant(s) will be asked to pitch their work to the panel between 3.00pm and 4.00pm on Thursday 17th 2011, each entrant will have a maximum of 10 minutes to present their entry and answer questions from the panel of judges. Judging will take please in the Venue or the Gallery, please put your name down in an available slot in the Base Camp (Upper Hall) by 3pm on Thursday 17th 2011 on the sign up sheet.
6. The criteria for judging the prototype will be:
- Addressing / meeting the requirements of the challenge
- Usefulness
- General Coolness
- Feasibility of prototype
7. We reserve the right to not award a prize if no suitable entries have been submitted.
8. In order to enter, please state your name in the 'Entries Section for each challenge below'
- State your name(s) that is/are being entered / name of group.
- The title of what you have produced.
- Description of what you have produced.
- If you have time, you should produce a short video/screen cast describing what you have developed and provide a link to it.
- A URI to anything you might have produced.
Prizes will be awarded at the Dev8D Awards Reception on Thursday 17th February between 6 and 7pm.
Web2.0 Apps for Science - Elsevier
(in case you encounter problems or have questions, send an email to developer@elsevier.com)
"Write an OpenSocial gadget using JavaScript for SciVerse. The gadget can use the SciVerse Content and Framework APIs, or open APIs and data."
Register for the Elsevier Challenge by sending an email to challenge-register@elsevier.com with your name, your app's title and description. Follow the instructions to complete registration and get access to SciVerse for the Challenge.
SciVerse contains 10 million scientific publications, 2500 journals and reaches 15 million researchers worldwide via ScienceDirect, Scopus and Hub.
SciVerse is an OpenSocial container like iGoogle, and uses JavaScript (JSON, JQuery etc) and HTML5 to build apps that can access scientific articles and meta-data using SciVerse's open APIs.
For Elsevier Challenge information on Sciverse go to the following URL http://developer.sciverse.com/dev8d
The Intellectual Property of the app remains 100% with the developers! Developers get full access to SciVerse for the Challenge.
Prizes
1. $1500 (Amazon gift card)
2. $1000 (Amazon gift card)
3. $500 (Amazon gift card)
Entries for ELSEVIER Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won Second Prize)
- Bharti Gupta/Yogesh Patel
- OpenGadget
- This application finds causes and related information for the health problems with a geo-spatial perspective.
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 2 (Won First Prize)
- Sam Adams
- Search Assistant
- There is quite a high barrier to getting started developing SciVerse apps, due in part to the relatively complex API. This entry presents a simple JavaScript API making it easy to perform SciVerse searches, and presents some example applications. The same approach could be taken to simplifying the content API.
- http://bitbucket.org/sea36/sciverse-dev8d/
Entry 3
- Nick England, Dan Hagon and David Jessop
- HelloRick
- This application adds links to external content which may be of interest
- Due to the difficulty of using the SciVerse API the original bibliographic clustering aims and ontology usage were abandoned due to lack of time.
- https://gist.github.com/832019
Entry 4 (Won Third Prize)
- Cass Johnston & Sander Van der Waal
- AweSomeThing
- Uses the SciVerse data with Google's mapping and visualisation tools to generate author profiles with information and visualisations of publications, collaborators, location, citations etc.
- GitHub
DevCSI Challenge
Take all our video, twiter, blog, hash tag (#devcsi, #dev8d, #jiscri) content and create a spectacular navigable / browsable showcase / dynamically updated visualization for our content!, see http://www.netvibes.com/devcsi#DevCSI_%2F_Related_Tags
* First prize: £250 Amazon voucher
- Second prize: £150 Amazon voucher
- Third prize: £100 Amazon voucher
Entries for DevCSI Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Picture This!
There will be a developer challenge focussing on how image metadata can best be used to deliver the services that real, front-line web services such as repositories, on-line image stores etc need to offer their users. Prizes will be offered for the most innovative and successful solutions developed during Dev8D as part of this challenge. Check out the Picture_This page where you can get updates of problems practitioners are facing and see if you can offer a solution - Come along on to the workshop and listen to lightning talks outlining more problems and issues - Talk to practitioners about your ideas for solving their problems - Work with them to develop solutions - Grab your prizes - Feel our respect for you!
First Prize
- £50 Amazon voucher
Second Prize
- £25 Amazon voucher
Other Fantastic Prizes:
- Tokens to swap for exciting, enticing mystery prizes throughout the day and night of 16th Feb
- Rewards for your solutions from grateful practitioners
- Free lunch
- Our undying respect and devotion
Entries for Picture This Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won first prize)
- Name: Robert Baker and Roger Greenhaigh
- Title: Creative Commons Images
- Description: Adds creative commons logo and copyright info from embedded metadata into a source image to provide copyright attribution.
- Screencast or similar (if possible):
- URI to working example (if possible): Write up
Entry 2 (Won Second Prize)
- Name: Bharti Gupta
- Title: Embedding metadata in geo-spatial images
- Description: geo-coordinates, acquisition dates, license info (see Ideas Swap Shop for further details)
- Screencast or similar (if possible):
- URI to working example (if possible):
Entry 3
- Name: Scott Renton and Ianthe Hind
- Title: Automatic generation of image metadata and image recognition
- Description: see Ideas Swap Shop for further details
- Screencast or similar (if possible):
- URI to working example (if possible):
Molly Project Challenge
Prize for the most significant/useful/novel contribution to the Molly Project by the end of Dev8D.
The Molly Project is an open source framework designed to help HE institutions deploy mobile web services quickly, it was a spin-off from Mobile Oxford (http://m.ox.ac.uk) and we're keen to get more people deploying it and contributing to it. Some of the ways to get involved are listed below, but to start with please do join the developer mailing list or IRC channel and get talking to the others in the community.
It's written in Python on top of the Django framework and is designed to work on a wide range of web-capable devices using browser detection and graceful degradation. We're due to release version 0.9/1.0 (with the aim of making it fully transportable and generic) in time for Dev8D so any help/feedback/code/prodding towards that would be gratefully received!
IRC: irc://irc.freenode.net/#molly Github: https://github.com/mollyproject Mailing Lists: http://sourceforge.net/mail/?group_id=309230 Home: http://mollyproject.org/
Prize: £30 Amazon gift voucher
Entries for MOLLY Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won First Prize)
- John Harrison
- SRU Provider and Demo App
- An SRU Search provider for Molly, and an app for searching archive collections. Demonstrated in a customized deployment of Molly for Liverpool
- Committed to Molly Project fork at http://github.com/bloomonkey/mollyproject
Entry 2 (Won First Prize)
- Giuseppe Sollazzo
- Install Wiki for CentOS 5.5
- [[1]]
PIMS Challenge - Mobile data/API Challenge
JISC has mobile Programme Managers, but no mobile programme data. A £50 Amazon voucher, plus coverage in JISC Inform, will be awarded for the best mobile application that uses JISC's API to its 'Programme Information Management System' (PIMS). Prize funded by SoftMuse Ltd.
For more information about how to access the APIs, please see: http://misc.jisc.ac.uk/pims/api/documentation/documentation.html
Entries for PIMS Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1
- Paul Walk
- PocketPIMS
- A mobile interface with extra search functionality goodness, optimised for iPhone and Android but tested successfully on very latest Blackberry devices too.
- PocketPIMS
Entry 2 (Won First Prize!)
- Mike Jones
- Mobile PIMS
- A native iPhone application to browse project information
- Screencast: http://fairlypositive.com/wp-content/uploads/2011/02/pims.mov
Entry 3
- Christopher Gutteridge
- Anyone for JISC?
- Geolocates your current postion and tells you about nearby projects from the PIMS data. (only shows one currently due to an issue in the project .json format)
- http://graphite.ecs.soton.ac.uk/pims/
Unsubmitted Entry 4
- Peter Millington
- Mobile PIMS Statistics
- This is a concept that extracts statistical data from the JISC PIMS database, presenting the data either as tables and/or charts. Does this by using the PIMS API to emulate the Protocol for Statistical Harvesting (PSH) en route to generating tables and charts.
- http://www.opendoar.org/demos/pims/
Open Knowledge Foundation - Open Bibliographic Data Challenge
This challenge was announced on the 17th of January 2011 and will be awarded at the awards ceremony at Dev8D 2011 on Feburary 17th 2011. What can you do with open access to data? What great ideas do you have for utilising open access to bibliographic catalogues? Or what example prototypes can you come up with in a month? We want to find out!
- 2 x £50 prizes for great ideas using bibliographic data *
2 x £500 prizes for building prototype apps using open bibliographic data
For more information, please visit http://openbiblio.net/challenge/
Entries for Open Bibliographic Data Challenge Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won First Prize)
- Damian Steer
- Joining bibliographic data to university of bristol researcher data
- It won't look very interesting. I have a sparql endpoint on my laptop.
- Blog post about what I got up to at Dev8D.
Open Planets Foundation Challenge
For preservation and beyond, broad and reliable format identification has proven to be a critical shared problem across many institutions. Recent discussions on the OPF blogs have illustrated this point, and showed that we all like using DROID and Fido but would also like to improve them.
The main challenge is to improve the coverage and quality of the signature files for Fido. The developers would create or update format signatures, and to ensure the quality we would specify the required information and embed a peer review process where a second developer has to sign-off on the new format record. At the end of the day we should have a much better set of signatures and format information that we can submit to PRONOM or elsewhere. To improve format records, attendees will just need a basic understanding of XML, but to hack signatures, will need to be comfortable with regular expressions and the command-line (for testing). A alternative and parallel challenge is to improve Fido itself (this would require Python expertise), or improve other identification tools in impressive ways.
Prizes
The prizes are as follows:
- First Prize, Samsung Galaxy Tablet
*Second Prize, Samsung Galaxy Player
The prizes will be awarded to the developers who create, update and/or review the most new signatures, or who make the most significant contribution to the development of the existing preservation tools.
http://openplanetsfoundation.org/
Entries for Open Planets Foundation Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won First Prize)
Bill Ray ( rodsit4@gmail.com ) Mr Java & python developer Produced a plan for GUI of FIDO and jython version of FIDO ALso: Stand alone FIDO propsal, App Engine, Python GUI standsalone proposal, https://github.com/openplanets/FIDO
Entry 2
- Dave Challis
- Extension to unix 'file' command to pull in info from FIDO
- Short python replacement for unix 'file' command.
Wrapper around 'file' and FIDO which allows file to accept two additional arguments '--show_version', which pulls file format version info from FIDO (file doesn't do this at all), and '--use_fido_desc' which uses FIDO's format description over the Unix file default. All other arguments/flags handled by 'file' as normal.
- Source code at: file
To run: Download, and edit the path to file (default is /usr/bin/file), and path to fido (default is /usr/local/bin/fido.sh), then execute using: ./file <filename>
Enabling Integrated Learning Environments (EILE) Project (JISC Funded)
To build a menu linking Full LTI provider to work with our Moodle consumer hosted on http://code.google.com/p/eile (code will be going up shortly). Entrants should look at our wordpress implementation for reference.
* First prize: £200 Amazon voucher * Second prize: £100 Amazon voucher * Third prize: £50 Amazon voucher
Entries for EILE Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (First Prize Won by Michael Aherne)
- Michael Aherne, University of Strathclyde
- Converted PMWiki, an open source wiki tool, in to a Full LTI Provider based on the EILE Wordpress integration. The tool registers and launches, using the LTI information to control edit access and auto create basic content seamlessly.
- Screencast - http://screencast.com/t/UFOTf8bX3iMc
- Code - https://github.com/micaherne/pmwiki-lti
Surprise Challenge! Enabling Integrated Learning Environments (EILE) Project (JISC Funded)
Surprise challenge to be announced at the event. I would like to challenge attendees to investigate the functionality provided by the full LTI specification and present a low-fidelity prototype of an exciting LTI provider idea.
- First prize: £100 Amazon voucher
* Second prize: £35 Amazon voucher
* Third prize: £15 Amazon voucher
Entries for EILE Surprise Challenge
Provide some basic information about your app here. Please put your entries to this challenge below this heading:
- Name
- Title
- Description
- Screencast or similar (if possible)
- URI to working example (if possible)
Entry 1 (Won first prize)
- Monica Duke and Julian Cheal, UKOLN m.duke@ukoln.ac.uk
- Integrating Repository data into VLEs
- We run an aggregation of metadata harvested from UK repositories listed in OpenDoar.
This resources are mainly research papers but there are also images and other types. There is reasonably good basic metadata descriptions of the resources. We have a machine query interface that we can use to retrieve results based on searches of the various metadata fields.
The idea is to use the LTI specification to carry out searches on the collection behind the scenes. The results can then be presented to users with a list of relevant resources.
The advantage is that once an LTI bridge exists to bring the content to the VLE, it could be repurposed to bring content from similar query interfaces. Our implementation uses the SOLR interface to carry out queries. An alternative would be to build an LTI bridge to query SRU (which we do not currently offer but is also possible).
The advantage for the service providers is that once an LTI bridge exists for their content (or query interface) that content will become available to all VLEs supporting LTI irrespective of the specific platform used.
- Screencast or similar (if possible)
The idea is to offer a lecturer interface so that a lecturer can search the collection, pick specific results and use them to build a list that can then be associated with a module inside the VLE. For the student view the list recommended by the lecturer will be presented as being relevant to a study module.
Ideas for improvement: Lecturers could tag the content with an 'audience level'; this would be fed back to the metadata thus enhancing the metadata so that it is more useful to others. Lecturers or students could have watchwords that match their interests (stored within the VLE) and this could be used to query the interface regular and bring back new items that match that interest. This last improvement would be taking advantage of the personlisaation information held by the VLE such as the search service will be offering a customised view without needing to implement personalisation services or hold personal data itself.
- URI to working example (if possible)
Not available yet.
