Tag Archives: esploro

Exploring Esploro #anzreg2019

Leave a reply

Exploring Esploro: migration and implementation of Esploro at Southern Cross University
Margie Pembroke, Southern Cross University

Southern Cross University punches above its weight research-wise and management looking to expose that research more.

In Australia many uni repositories were created from government funding. Initial focus on green open access. Then ERA (like PBRF) came along and hijacked repositories, and then publishers hijacked open access… CAUL review of australian Repository Infrastructure found that integrations was falling behind.

Currently use bepress for their repository, and have a separate CRIS. Lots of manual reporting, data entry, reconciliation etc. No integrations, no workflows, reliant on self-reporting. Submission process: researcher gets a PDF form from the website, fills it out, and emails it to repository and to the CRIS who enter this data independently.

Early adopter of Esploro. A chance to influence the platform – financial benefits but also risks. Aim to soft launch this November, running two systems in parallel until researcher profiles and outfacing pages in Esploro look how they should.

First migration has happened – OAI-PMH export using document export, all bepress data also backed up to AWS3. Ex Libris helped with metadata mapping. Could export bepress statistics into Esploro too.

New workflow – researcher writes article, it appears on the web, Esploro finds it and surfaces in both the repository and CRIS views. Automagic harvesting based on DOI/ISBN, leverages off the Summon index, de-duplicates, links to ORCID, will look to harvest from Research Data Australia, Figshare and Unpaywall, etc.

Integrations planned with HR system (never did this for Alma – staff added ad hoc when needing to request/borrow!), uni data warehouse, uni ORCID API, CRIS, Research Data Australia, Libraries Australia, Datacite for minting DOIs.

Public interface is essentially Primo VE plus researcher profiles.  Internal workflow is in Alma. Sherpa/Romeo etc.

Benefits for library:

  • automatic harvesting / ordering (for ERA auditing) which saves work, avoids typos, means people don’t have to remember to place orders
  • staff already familiar with how Alma works
  • can add preprint, post-print, link to paper etc all sharing basic metadata
  • ease of management of research profiles
  • support from Ex Libris community

Benefits for researcher:

  • massive timesaver – only need to manually enter metadata for items not published on the internet
  • increased visibility especially with automatic generation/updating of profile
  • compliance with funding requirements

Benefits for institution:

  • comprehensive picture of research outputs across the institution
  • can leverage Alma analytics to create reports
  • avoids duplication of data-entry; increases efficiency

 

Q: How do you get full-text in?
A: Initially pulls in from bepress. For new items, sends email to researchers to ask them to upload accepted manuscript.

Ex Libris company / product updates #anzreg2018

Leave a reply

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.