Tag Archives: leganto

Leganto implementations #anzreg2018

eReserve, Alma-D and Leganto: Working together
Anna Clatworthy, RMIT

Project to move all 14,000 Equella e-reserve items to Alma Digital in a format to suit Alma/Leganto copyright and digitisation workflows

All course readings at RMIT are digital; eReserve team in library accepts requests, scans items, uploads, sends a link back to use in CMS. Helps withh copyright compliance. Mostly book extracts, some journal articles, Harvard Business Review

Lots of questions to consider: MARC or DC; multiple representation or single record; how to deal with CAL survey in middle of migration; how do records look in Primo and in Leganto (which they didn’t yet have live); what is copyright workflow and how to manage compliance?

DC records weren’t publishing correctly so migrated to MARC. (This may have been fixed now). Multiple portion representations on a single bib record – migration process quicker, chapter/portion info in 505_2$a. Custom 940 field with copyright info

Extracted parents as spreadsheet, extracted children as spreadsheet, script combined the two — then instead imported records from Libraries Australia with a norm rule for extra fields (505, 542 for extract and copyright info; 9XX for CAL information); trained non-library folk to use MDE and run norm rules.

eReserve in Alma has no custom fields. Creates confusion for non-eReserve staff (thinking they own the book so no need to buy it though in fact only have 11pages of ch.4 – looks like a book in Primo too!)
* DC doesn’t work in Analytics – only see title
* Determined best practices and process for migration; set up Alma-D collections config and display in Primo; created MARC RDA cataloguing template and training; Leganto training and pilot; configure Alma reading lists, copyright, Leganto set up, and more…..
* Would like enhancements:
– automatic fills in copyright workflow – only working for some fields
– search function in reading list view
– MARC deposit form
– digital viewer link – Share link doesn’t work, leads to ‘no permission’ page. (Users need to sign-in first but of course they don’t.)
* With Leganto, show-and-tells seem to be getting interest, as is word of mouth. Not actually live yet though due to IT delays.

Leganto at Macquarie University: impressions, adjustments and improvements
Kendall Kousek, Macquarie University

Macquarie had Equella for copyright collection. Teachers email list to library and list made searchable in Primo by unit code (via daily pipe). Move to Leganto to address some issues. Can search library for items or upload your own pdfs, images, etc.

Pilot with faculty of Arts to create reading lists for 9 courses. Next semester another 11; 1 person had done it before and confident enough to try their own. Next semester 3 departments; not many came to session but a few still created own reading list; total of 120 reading lists created.

Feedback – added survey as a citation to reading lists – not many respondents as end of semester. Later survey added to Moodle directly to capture those not using the reading list and finding out why. Teachers liked how they could track how many used links and when (eg hour before class); ability to tag readings (eg literature review, assignment, extra); students like navigability and ability to suggest readings to teacher. Student satisfaction very high: clear layout, saved time chasing readings and can track reading in the week. Library staff liked layout, ease of learning/adding PCI records; Cite It! bookmarket.

Improvements people wanted was better integration with Moodle (lots of clicks to get to article); found it slow to load; students getting confused about whether discussions should be in Moodle or Leganto. Edge broke something so told students to use other browser. Want a ‘collapse all’ button for previous weeks to get straight to today’s: ExLibris are releasing this soon. Library staff want subsections functionality (ExL not going to do this, so using ‘notes’ feature instead.)

Adjustments needed by
* students – easier to find readings in Primo – but not all are there (esp articles, chapter scans), Leganto is source of truth. So have created Resource Recommender record to link to Leganto.
* teachers – want them to create their own reading list instead of submitting it by email (or at least to include layout information in those emails). And get them to use more variety of resources.
* library staff – more collaboration, reading lists are never complete until end of semester so have to be on top of it.

* teacher finding more engagement as students aware they can see usage! Another planning to be more ‘playful’ with reading lists. Appearance of Leganto makes students more aware of resources as resources instead of just a list. Feeling will plan their teaching through Leganto. One teacher saying “These are the questions for the week, what are teh resources you’re using to answer them?”
* students can track which readings they’ve completed, can build own collection, can export in preferred referencing style.
* library staff have communication with teachers in Leganto; inclusion of all resource types (including web links using citation bookmarklet). Using public notes (eg trigger warnings)

4th stage of pilot will involve new departments, more volunteers by word of mouth. Need better communication/training eg presentations at dept meetings.

OER not currently dealt with – functionality maybe to come – can add CC license within a reading list but then depends on how widely you share that reading list!

Ex Libris company / product updates #anzreg2018

Ex Libris company update
Bar Veinstein, President Ex Libris

  • in 85 of top 100 unis; 65million api calls/month; percentage of new sales that are in cloud up from 16% in 2009 to 96% in 2017; 92% customer satisfaction
  • Pivot for exploration of funding/collaboration https://www.proquest.com/products-services/Pivot.html
  • aim to develop solutions sustainably so not a proliferation of systems for developing needs
  • looking at more AI to develop recommendation eg “high patron demand for 8 titles. review and purchase?”, “based on usage patterns, you should move 46 titles from closed stacks to open shelves?”, “your interloans rota needs load balancing, configure now?”, “you’ve got usage from vendors who provide SUSHI accounts you haven’t set up yet, do that now?”, algorithms around SUSHI vs usage.
  • serious about retaining Primo/Summon; shared content and metadata
  • Primo VE – realtime updates. Trying to reduce complexity of Primo Back Office (pipes etc – but unclear what replaces this when pipes are “all gone”)
  • RefWorks not just for end user but also aggregated analytics on cloud platform. Should this be connected/equal to eshelf on Primo?
  • Leganto – ‘wanting to get libraries closer to teaching and learning’ – tracking whether instructors are actually using it and big jumps between semesters.
  • developing app services (ux, workflow, collaboration, analytics, shared data) and infrastructure services (agile, multi-tenancy, open apis, metadata schemas, auth) on top of cloud platform – if you’ve got one thing with them very quick to implement another because they already know how you’re set up.
  • principles of openness: more transactions now via api than staff direct action.
  • https://trust.exlibrisgroup.com/
  • Proquest issues – ExL & PQ passing the customer service buck, so to align this. Eg being able to transfer support cases directly across between Salesforce instances.

Ex Libris prodct presentation
Oren Beit-Arie, Ex Libris Chief Strategy Officer

  • 1980s acquisitions not part of library systems -> integrated library systems
  • 2000s e-resource mgmt not part of ILS -> library services platform (‘unified resource mgmt system’)
  • now teaching/learning/research not part of LSPs -> … Ex Libris’s view of a cloud ‘higher education platform’
  • Leganto
    – course reading lists; copyright compliance; integration with Alma/Primo/learning management system
    – improve teaching and learning experience; student engagement; library efficiency; compliance; maximise use of library collections
    – Alma workflows, creation of OpenURLs…
  • Esploro
    – in dev
    – RIMs
    – planning – discovery and analysis – writing – publication – outreach – assessment
    – researchers (publish, publish, publish); librarians (provide research services); research office (increase research funding/impact)
    – [venn diagram] research admin systems [research master]; research data mgmt systems [figshare]; institutional repositories [dspace]; current research information systems [elements]
    – pain points for rseearchers: too may systems, overhead, lack of incentive, hard to keep public profile up to date
    – for research office – research output of the uni, lack of metrics, hard to track output and impact, risk of noncompliance
    – next gen research repository: all assets; automated capture (don’t expect all content to be in repository); enrichment of metadata
    – showcase research via discovery/portals; automated researcher profiles; research benchmarks/metrics
    – different assets including creative works, research data, activities
    – metadata curation and enrichment (whether direct deposit, mediated deposit, automatic capture) through partnerships with other parties (data then flows both ways, with consent)
    – guiding principles: not to change researchers’ habits; not to create more work for librarians; not to be another ‘point solution’ (interoperable)
    – parses pdf from upload for metadata (also checks against Primo etc). Keywords suggested based on researcher profile
    – deposit management, apc requests, dmp management etc in “Research” tab on Alma
    – allows analytics of eg journals in library containing articles published by faculty
    – tries to track relationships with datasets
    – public view essentially a discovery layer (it’s very Primo NewUI with bonus document viewer – possibly just an extra view) for research assets – colocates article with related dataset
    – however have essentially ruled research administration systems out of scope as starting where their strength is. Do have Pivot however.