A project, not a single «product» The aim was to explore- how the library can get access to its own data - what can be done with that data Oslo public library ABM-utvikling Trond Aalberg, NTNU (FRBR) IT-students Libriotech
Mashups - travel - music VuFind FRBRLinked data/Semantic Web
MediaWiki The software that Wikipedia runs on Semantic MediaWikiMore capabilities, can export data as RDF http://semantic-mediawiki.org/
A wiki of Norwegian library historyNot yet launched – living at a temporary URL
Linux for patrons at Oslo public library «Semi-thick» clientsUbuntu on the server - http://www.ubuntu.com/ Lubuntu on the clients - http://lubuntu.net/ Libki for administration - http://libki.org/http://digital.deichman.no/blog/2011/06/22/publikumspcer-del-3/http://it.deichman.no/projects/halvtykke-klienter http://it.deichman.no/projects/libki
Koha The first free software ILS(Integrated Library System)http://koha-community.org/
Whos using it?● The Naval Academy, Bergen● Norsk Senter for Folkemusikk og Folkedans
Koha at The Naval Academy http://sksk.bibkat.no/
Who will be using it soon?● Nesodden school of Waldorf education● Buskerud county library● Lørenskog «friskole»● 5-10 school libraries in Time municipality
Challenges for Koha in Norway● NORMARC ● More or less solved● NILL – the national ILL protocol● National library cards● Translations
Please take note, here comes the main point...
When making changes to F/LOSS code, submit your changes «upstream»
Its how free software moves forward Give something back to the community You dont have to maintain your changes as a separate «fork»It pays off in the long run even if you have to putin an extra effort to get it into the upstream code Its fun!
Koha bug #2593 - way to duplicate items● Suggested by Nicole Engard, US● Paid for by The Naval Academy, Norway● Implemented by BibLibre, France● Integrated into Koha version 3.2● http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2593
Contributions dont have to be financial Report bugs Verify bugs Answer qustions Write documentation Test bugfixes/improvementsTime is the most scarce resource of all!
If you are paying someone to «do» F/LOSS for you, make sure «upstream» is part of the dealNew developments should be made availabe to the upstream projectIn a «lasting relationship», giving back should be part of the package
Libriotech tries to give back on behalf of itself and on behalf of its customers Minor bugfixes and improvements Testing new code Organizing bug squashing days Answering questions
Be a part of the community! You learn things You make new friends Its fun!But yes, it does take some time...
Is «the old way» (proprietary software) doing what we need it to do for us? Or have we been serfs long enough?...paying our masters (vendors) to protect us from having to think about our systems and our data?
Freedom to tinker Libraries need to be able to experiment...or pay someone to experiment on their behalf F/LOSS is the best platform for tinkering and experimenting!
Move fast Break things ...and fix them Development needs to happen in real time, not on a 2-3 year scaleThe distributed, peer-to-peer nature of F/LOSS is perfect for this
Libraries need hackers, in-house Development needs to be a part of business-as-usual, not just a bunch of projects Perpetual beta, baby!...not as an excuse for bad software and services, but as a reminder that we are never «done»
New roles for libraries?https://www.amazon.com/gp/feature.html?docId=1000718231
Documenting the (hyper) local - history - happeningsSharing with CC licences makes it available globally
Bridging the digital divide Put free software in the hands of patrons Empower them to do things on their ownLet them take the software tools they found in the library home with them
And finally...Every library conference should have a hackfest!
Thanks for your patience! Magnus Enger firstname.lastname@example.org Libriotech.no