- Ka Pioioi
- E hara i te mea
- Tutira mai
- Maku ra pea
- Te Aroha
- Toia mai te waka nei
- Purea nei
- E toru ngā mea
- Ma wai ra
- Tai Aroha
- He Honore
- Me he manu rere
- Putiputi kanehana
- Tohora nui
- Oma rāpeti
I was just talking about 3000 year old Welsh skulls and Māori not being tangata whenua and bam, patu right in my face. Had to stop, and go down to the A&E
As I was being consistently wrong about everything, as I am wont to do, I heard a mighty yell of ‘D haaa’ and smack, patu on the point of the jaw. Shut me right up I must say.
We were performing our ‘Haka’ to advertise insurance, when someone came running up, and screamed ‘Ana tō kai, kai toa’ and hit the head of marketing in the face with some sort of club thing.
I don’t know what happened, one minute I was saying “muesli bars have too much sugar in them for growing bodies” and the next minute, tewhatewha upside the head. Well I never!
Look as the enlightened feminist I am I was just commenting on how ‘ethnic’ women are more attractive if they don’t look ‘ethnic’. Then crack, taiaha to the temple. I said don’t hit me I love women and what about fat yoga… and then pow, wahaika in the waha.
Paul presented about Coral which is an ERM (Electronic Resource Management) software. Paul told us it is well documented, with an extensive manual. It is software for Librarians to use, not end users. It is for managing all your subscriptions for digital resources. Large universities often have hundreds of subscriptions and tracking licenses and url, and acquisitions etc are very hard to track. Coral was developed to manage this.
It is not packaged, but is still pretty easy to set up. Setting up authentication is the hardest bit, but once you have done that, the rest is pretty easy. It has one big problem it is only available in English and it currently cannot be translated. Hopefully since it is OSS we can fix this issue, but it is a big task.
Coral is divided into modules
Paul then demoed the software for us.
My battery on the laptop went flat, so Tom kindly took notes on this session for me so I could write this blog post
Alvet and Ricardo from EBSCO talked about EDS and the integration work they have done with Koha
To start they began by explaining why they had developed this plugin
They then explained what a discovery service is:
Next the showed us what EDS looks like in its’ native interface so that they could show that it is quite similar in Koha using the plugin
Then they showed what EDS and Koha look like
They explained that support is only available in 3.12+ because integration has been implemented as a plug-in. Plugins allows for features to be added quickly through plug-ins in-between release Koha cycles.They then stepped us through how you install and configure the plugin
Improvements for the future
Where do I get it
If you google for EDS API Koha, you will find a github page that has the newest version available for download. EBSCO also provide a wiki, an Integration Kit as well as training and help
Brendan with help from Tomas who was translating talked about possibilities for funding the Koha project.
Brendan mentioned we need money for developments, and other things. He covered the process for getting code in, someone submits, another entity signs off, qa checks, then the release manager checks and pushes or not. Out of this whole process, the only part that is directly funded is the initial development of the feature/fix. Once it is passed to community, we rely almost entirely on volunteers.
Developers get paid for new features mostly, because new things are what libraries want to fund, but there are also things under the hood, often called plumbing problems, that they don’t want to fund. Some of these plumbing issues are big pieces of work. Brendan proposes as a community we need to create some kind of community that can collect and disburse money which we can use to fund fixes to these 2 issues.
Brendan showed the Koha dashboard, showing that today 215 patches need to be signed off, and 64 waiting for QA. He covered the fact that most signoffs are done on volunteer basis, and in a conservative estimate we can see we need at least 700 hours to per 6 months to keep up with development.
Two complementary options:
Big features take lots of time to test, very hard for a volunteer to deal with these, so they wait for a while. Also this means that if the code has moved, rebasing needs to be done. So if we can fundraise and have people working on signoffs and QA as their job.
Brendan then talked about stability vs rapid development. Brendan sees that both points are valid and that it is a balancing act. With so many libraries (10,000 ish) it is peoples livelihoods depending on the stability of the product. However we need to continue to innovate as well. So get involved have your ideas presented. Mail the list, come to hackfests, chat on IRC etc. No ideas are bad ideas, only the ones you don’t present.
An audience member asked about the idea of a foundation, Brendan said lets start with a funding organisation, and start small with perhaps a donate now button. But that organisation should not having anything to do with the direction of governance of the project, just collect funds.
Bob and Brendan are going to work on a proposal during hackfest for this funding organisation to present to the community, to get this ball rolling