Background
Discussions about an Analytics group began just before IGeLU 2015. Alma’s Product Working Group was forming an Analytics subgroup, and Ex Libris’s announcement of Oracle OBIEE as the analytics tool for hosted Primo suggested that a joint group would be useful. Skills in OBIEE would obviously be transferable across the 2 products. John Krug volunteered to get the group started and a round of recruitment began. The first remote meeting took place in April 2016.
Since then (coordinator / deputy coordinator)
- Q1 2016 – John Krug, Lancaster University (UK) / Margaret Briand Wolfe, Boston College (USA)
- Q3 2016 – Margaret Briand Wolfe / Joan Kolarik, Weizmann Institute of Science (Israel)
- Q2 2020 – Joan Kolarik / Davin Pate, University of Texas at Dallas (USA)
- Q3 2021 – Davin Pate, University of Texas at Dallas (USA) / Maya Amichal, Weizmann Institute of Science (Israel)
- Q3 2024 – Maya Amichal, Weizmann Institute of Science (Israel) / Daisy Nip, California Digital Library (USA)
Mission
Analytics, the activity of collecting, structuring and combining data into relevant and actionable information for organizations, is more than reporting. Analytics focuses on finding the added value that data, such as assets and their patterns of use, can offer an organization, providing insight into their business and highlighting new opportunities in support of decisions or predictions. As Library processes develop and become more complex, the ability to analyze the resulting data has never been more crucial.
The IGeLU/ELUNA Analytics group is not part of any single Product Working Group because the analytics data is created in multiple applications and some of those applications have their own analytics interface, as well. The group’s cross-product view allows this group to cover broader topics from outside the perspective of any single product. Specific areas of examination include data extraction, consistency, processing and enrichment, visualization, documentation, user interface, and APIs. Integration of other tools, general analytics, and data warehousing are also relevant to the group. A fundamental principle of this group is that Ex Libris users must benefit from openly specified, documented, and understood product data models, analytics data models, and processes for transforming product data into analytics data. Therefore, all issues pertaining to how product data is extracted, enriched, stored, accessed, and used are pertinent topics for the Analytics group. Whenever possible, members of this group also participate in ongoing development and planning.
Tasks and Responsibilities
- maintain a ‘key goals’ document
- maintain an open use cases and scenarios document
- discuss and promote the various uses of analytics in Ex Libris products
- discuss and promote the use of analytics in ‘evidence-based-librarianship’
- help ensure all relevant product data is available to use within the associated analytics products (for example, all relevant Alma data is available to the OBIEE Alma instance)
- help ensure data created using Ex Libris products is readily available, ideally via APIs and through publishing / batch export routines so as to enable the use of special processing, such as institutional data warehouses, big data tools, visualization tools, and programming languages
- encourage and provide some support for groups (geographical or interest-based) to hold analytics skills development days such as those that have taken place in the UK (Alma Analytics) and UNSW for sites in Sydney (Alma Analytics) and through the Ex Libris Northeast Users Group (Tableau).
- maintain close links with the LOD, Interoperability, and Content groups and their communities
- coordinate common problems and enhancement requests for the NERS process
- maintain a repository on Google Drive for sharing information, tips & tricks, discussion, etc
- maintain a mailing list for announcements and discussion
Membership
| Members | Role |
|---|---|
| Maya Amichal (Weizmann Institute of Science) | Coordinator |
| Daisy Nip (California Digital Library) | Deputy Coordinator |
| Davin Pate (University of Texas at Dallas) | |
| Michael Johnson (University of Minnesota) | |
| Michelle Eichelberger (State University of New York, SUNY) | |
| Rebecca “Becky” Smith (Memorial University of New Foundland) | |
| Susan Bond (University of Toronto) | |
| Laura MacNeil (Edinburgh University) | |
| Thomas W Fesmire (Liberty University) | |
| Allison Erhardt (University of Manitoba) | |
| Paul Harding (University of York) | |
| Emily Nilson (George Mason University Libraries) | |
| Phillip Kozjak (OBV) | |
| Lisa Wong (University of California, Santa Cruz) | |
| Ariel Lock (National Library of Israel) | |
| Francesc March (Open University of Catalonia) | |
| Leon Krauthausen (Free University of Berlin) | Alma Liaison |
| Matt Black (University of Calgary) | ELUNA Primo Liaison |
| Paul Harding (University of York) | IGeLU Primo Liaison |
| Joan Kolarik (Drexel) | Esploro Liaison |
| Alysa Hernandez (California State University, San Marcos) | ELUNA Leganto Liaison |
| Chris Jones (University of Sheffield) | IGeLU Leganto Liaison |
| Mehmet Celik (KU Leuven) | Interoperability Liaison |
| Janell Bekauri (William and Hobart Smith Colleges) | Summon Liaison |
| Rami Attebury (University of Idaho) | Rialto Liaison |
| Sam Alloing (National Library of the Netherlands) | Rosetta Liaison |
| Kristen Clark (University of Minnesota) | ELUNA Steering Committee Liaison |
| Wei Xuan (University of Manitoba Libraries) | IGeLU Steering Committee Liaison |
Data Understanding
A common theme for users of Analytics is that it is difficult to understand, in many circumstances, what exactly the data presented in Analytics products means. Everybody has the experience of not being sure how what is presented in Analytics is derived from what is being presented in Alma/Primo or other source products. The data in Analytics is not directly the data from Alma/Primo, etc. but there has been an ETL (Extract, Transform, Load) from Alma/Primo, etc. to OBIEE Analytics or other analytics products. We believe there are benefits for all product users in having the product data models, the Analytics data models and the transform process openly specified and understood. It would make it more likely that problems arising will be accurately diagnosed. We believe this also benefits Ex Libris in that Analytics will be better understood, be more effective and users will be able to help find issues and improve the quality of the service that is delivered for the community.
Data Access
This goal is held in common with the other groups. We entrust Ex Libris with our data, its storage, manipulation and security. It is our data and we wish to maintain and extend access to it whether through batch processes or APIs. The community wants to use this data with external data warehouses and visualization tools, not just within Ex Libris products.
Gather Evidence
It is our on-going job to collect and analyze evidence that identifies:
- problems/bugs found in the data in Analytics
- incorrect labeling or mapping from products to Analytics
- data not mapped at all from products to Analytics
- difficulty in understanding what is available via Analytics due to incorrect or incomplete documentation
We work to present this evidence in a unified format and persuade Ex Libris to devote resources to address the issues in a timely manner. The majority of the evidence is based on group research, Analytics issues documented in product lists, support cases, and issues raised at ELUNA and IGeLU. Once evidence has been gathered it is presented to the ELUNA and IGeLU steering committees as well as the Product Working Groups for comments and then presented to Ex Libris for discussion and with a goal of getting it on the roadmap towards resolution.
Education and Advocacy
We will work with Ex Libris to improve and extend documentation and training materials within the community about the ETL process between Alma and Primo and Analytics and build a more complete thesaurus / data dictionary of the data available in analytics and where it derives from in Alma and Primo. There is also a need for a common language so that elements are called the same thing in Analytics as they are called in Alma and Primo. It is often hard to find data in Analytics when it has been renamed to something else. There has already been some community-generated material, and this should be collected, preserved and built upon.
Meetings and Communications
We have a Discussion List for Analytics PoC members.
A monthly virtual meeting takes place on the third Tuesday of each month.
To join the Analytics CoP (Community of Practice) listserv please complete the subscription request located here.
After Subscribing, you may open a discussion by emailing: analytics@exlibrisusers.org