David Nind is one of a kind. Neither he nor the organisation he works for use Koha, but he has been active in the community for many many years. He helps with maintaining the wiki, running the twitter account, answering many many emails on the mailing list, attending user groups and so much more. The work he does has been incredibly valuable and is a major part of the success of Koha.
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
Noel – a Historian (no really, you can just say you’re a historian and the Herald will print any drivel you make up)
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.
Alan – Author (sort of, he had one ok book but the rest are all pretty crap)
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.
Spokesperson for ARAG insurance
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!
Judgey McJudgerson – Kindy parent/teacher
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.
Someone whose core is super soft
He’s just three …
The “journalist” couldn’t finish this statement as he was promptly hit 16 times with a mere
Some one started an email to me with Kia ora, so I was typing out a reply saying “I’m not Māori please address me in English”. As I was about to hit send a felt an immense pain at the back of my head and someone yelled “English that, cracker”
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.
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
NIWA, a research institute in NZ, wanted a simple interface where their users could access discovery services
An a interface where Koha was the Front end
They then explained what a discovery service is:
A way to access all of the library’s full-text content (electronic and print) in a single search
High quality metadata = high quality search results
Match on subject heading
Match on article titles
Match on other keywords
Match on keywords in abstracts
Match on full text
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
showed the NIWA search (Discovery) box, including the detailed list of field codes you can search on.
Demoed the Catalyst work to use tabs instead of drop-downs to segregate the search options
When the drop downs are changed a pop-up appears that notifies you of the search mode
demoed the integration between the Koha catalog and the EDS resources, including patron services, accessing EBSCO resources through the koha interface, limiting the resources searched to what the library has available,
reserving resources across Koha/Ebsco and cart functionality
demoed guest access restrictions to show that limited resources will not be displayed unless authorized
demoed login and authorization methods (userid/passwords, ip addr restrictions, etc)
demoed interaction between search results and checkboxes including the functionality that depends on those boxes (more details, etc)
demoed accessing EBSCO content from the Koha interface (html results, PDF, etc)
showed that all EBSCO functionality is available through Koha interface in advanced search and that the Koha advanced search can be toggled through tabs/links including add/remove of search
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
Support for newer versions of Koha (3.16, 3.18) (ready at the end of October)
Looking to enable default language support in Koha and the Ebsco plug-in
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