Releases: moravianlibrary/VuFind
Releases · moravianlibrary/VuFind
Central library portal - August version
This is the progress we have reached by the end of August 2015.
Main functionalities we've managed to implement since the fork of vufind-org/vufind are:
- Connecting & managing multiple user's identities - these does not have to be from library, it is enough if it is possible to log in with them via Identity federation (we use eduID.cz)
- Connecting & managing multiple libraries to communicate with using either Aleph or XCNCIP2 driver.
- we are currently working on new driver for Dublin Core
- There has been created new Statistics section where can the libraries being connected into this portal easily see many useful graphs. For now it is parsing data from Piwik, but we expect it to fetch also live data from user's actions, which is about to be done soon.
- There has also been improved Piwik's API connectivity.
- Many styling improvements were done in order to support Bootstrap 3 & it's mobile user-friendly interface
- It has also been written a lot of specific Solr drivers for Czech libraries
- you can look for them in modules CPK & MZKCommon
- We have also developed some utilities we won't use probably. These are mainly WantIt, PerunShibboleth
- WantIt had to be a feature on screen with search results in order to let user easily choose what he wants to do with found result, such as buying it, seeing an e-version, ordering it home or just looking at the list of institutions which do have that record
- PerunShibboleth was fully functional connectivity driver for Perun, the Identity and Access Management System developed by © 1991–2014 CESNET, z. s. p. o . The plan was to maintain the user's connected identities inside Perun & retrieve only a few personal information. The plan have failed after we found out there is a need for managing a lot more ecosystems than it would be needed if we wrote the connected identities managing system ourselves. Now it is know as ShibbolethIdentityManager class, which needs another 'eppn' column inside user_card table to have unique user's identity string. EduPersonPrincipalName is guaranteed to be unique since we allow to connect only from the Identity federation eduID.cz. It would be probably usable with eduGAIN.com