We highly encourage everyone who is interested in submitting a proposal to read through the information below.

Before you submit

The following applies to all events – Developers Day+, Analytics Afternoon, and the Annual Meeting – unless otherwise specified:

Presenting with co-presenters?

  • One proposal for the group should be submitted by one presenter, all co-presenter information should be added by the submitter. You will need full name, email, job title, and institution name for all co-presenters. All presenters will have a chance to review their information for accuracy before acceptance and publication.
  • All co-presenters must be included in the proposal at the time of submission to ensure no scheduling conflicts.
  • Include only those who will be attending ELUNA in person as co-presenters. Non-presenting co-author credits may be on the slides and/or ELUNA document repository.
  • Panel session proposals are welcome for consideration; however, please be sure to indicate it is a panel in the proposal form.
  • Sessions may have up to 4 co-presenters or panelists. For panels, the moderator is not included in this count, but should be added as a co-presenter in the proposal.

Consider the best event fit for your proposal

Would you rather present at Developers Day+, Analytics Afternoon, or the Annual Meeting? Please make sure that you’re submitting to the call you want your proposal to be considered for. Proposals are not transferable between calls, so any proposals submitted to one call must be resubmitted for the other call.

Developers Day+ & Analytics Afternoon pre-conferences
  • Developers Day+ consists of a day-and-a-half of content and collaboration ahead of the ELUNA Annual Meeting. It’s an event for systems administrators, customizers, and developers to network, show what they have been working on, and learn both from coders at other ELUNA Member institutions and from Ex Libris. It’s a community exercise for implementers, by implementers.
  • Analytics Afternoon is a half-day focused on intermediate and advanced topics in analytics and data visualization. Attendees are expected to have basic familiarity with Analytics in Alma.  Ex Libris offers Knowledge Days for beginning instruction in analytics.
  • Calls for Developers Day+ and Analytics Afternoon workshops and lightning talks/presentations are separate, so be sure you’re submitting to the intended call!
  • Developers Day+ and Analytics Afternoon take place concurrently. You cannot attend or present at both.
Annual Meeting
  • All breakout sessions are 45 minutes long — typically 30-35 minutes of presentation and 10-15 minutes for questions and follow-up commentary.
Review the Annual Meeting Track List

The Program Committee has made extensive revisions to the conference tracks for the Annual Meeting once again. Your proposal can be designated for only one track. Tracks now indicate the general structure and intention of your session, rather than any specific topic or product focus.

  • ELUNA Groups & Governance
    • Includes: Leadership pre-meetings, organizational updates, Working Group and Community of Practice share-outs, speaker orientations, and leadership involvement opportunities
  • Product Roadmaps & Conversations
    • Includes: Q&As, vendor announcements, plenary sessions, product introductions
  • Demonstrations & Overviews
    • Includes: Tool-focused demonstrations showing core functionality, user interfaces, and standard workflows (mix of user and vendor presentations). Beginner-to-intermediate knowledge of product, general application potential.
  • Practical Projects, Case Studies & Tips
    • Includes: User-led presentations sharing real-world experiences, custom technical configurations, process designs, interactive audience/panel discussions, and institutional lessons learned. Deeper dives into specifics and troubleshooting.
  • Data Sharing & Comparative Evaluations
    • Includes: Comparing tool function and performance (e.g., AI search comparisons, Specto Essentials versus full), reviewing white papers, data-driven discussions, or presentations of survey results.

Submission Requirements

Presentation Proposal Details and Formatting

Once you begin to enter field information, Dryfta will autosave until you submit. You should use your login to access in-progress submissions rather than begin a new proposal.

Presentation Topic (Annual Meeting only):

A streamlined selection of topics now encompasses the Ex Libris product families and covers all areas of library operations. You may only choose one. Use your summary or learning outcomes to mention secondary subject areas.

  • Discovery Tools & UX
    • Covers: Primo VE/NDE, Summon, Vega, import profiles, Dedup/FRBR, wayfinding (StackMap), user accessibility, campusM, Blacklight and VuFind
  • Integration & Automation
    • Covers: Library Open Workflows (LibOW), CloudApps, Third Iron, data exports (Analytics, Power BI), APIs, authentication, custom integrations, chat services, consortial collaboration
  • Metadata
    • Covers: BIBFRAME, inclusive metadata practices, metadata enrichment, MARC reconciliation, Linked Open Data, CDI, normalization processes, publishing profiles, Authority Control
  • Resource Sharing & Fulfillment
    • Covers: Rapido, RapidILL, external ILL systems, Article Galaxy Scholar (AGS), copyright, circulation configuration, lending services, borrowing practices, notices and letters
  • Academic Support & Engagement 
    • Covers: Leganto, Esploro, WoS, campusM, research tools, course reading lists, textbook affordability/affordable learning, OER, AI literacy, Subscribe to Open (S2O), digital rights management, open sources, campus partnerships, reference/instruction
  • Resources & Collections
    • Covers: Rialto, Specto/S-Essentials/Alma Digital, Rosetta, acquisition models, electronic resource management, COUNTER/SUSHI, content evaluation, government docs, archives, and special collections
  • Staffing, Strategy & Administration
    • Covers: Project management, preparing for change/continuity planning, trauma-informed service, strategic staffing, building internal relationships, assessment, documentation, training/continuing ed, institutional planning, disaster response, marketing/promotion, library event planning

Presentation Title: 

Titles should be no longer than 15 words, proofread for spelling and typos, and capitalized in title case. You may use this title case converter as needed. 

Example: Alma and Your Library: Best Practices 

Presentation Summary: 

Summaries should be no longer than 150 words. Summaries appear in the conference app and online program details. Please proofread your abstract for spelling and typos. 

Presentation Duration (Developers Day+ & Analytics Afternoon only): 

Select your desired/needed duration length. 

Options are 15, 30, 45, or 60 minutes long.

Learning Outcomes (Annual Meeting only): 

Please provide at least one learning outcome.

Supplying learning outcomes not only helps the Program Committee make informed decisions regarding proposal acceptance, but it also allows attendees to make informed decisions when picking sessions during the meeting! When developing your proposal, consider what you want attendees to learn at your session. A well-written learning outcome uses verbs that are specific and actionable and avoids broad verbs such as “understand” or “appreciate.”

Examples:

  • At the end of this session, participants will be able to perform basic Alma normalization rules.
  • At the end of the session, participants will be able to describe the Primo road map.

For more tips on writing good learning outcomes, here are some suggested resources:

Presenters and co-presenters: 

List all speakers who will be physically present and participate in the session.


After Submission

The Review Process

Understanding the Rubric

The Program Committee reviewers (representatives from ELUNA working groups and/or appointees by the Program Committee Chair and Developers Day+ Chair) will review and rate each proposal with the following criteria:

  3 Outstanding 2 Acceptable 1 Needs Improvement
Title The title generally describes the session in a way that generates attendee interest The title generally describes the session The title is vague or doesn’t align with abstract
Summary The summary clearly and succinctly describes the session while generating attendee interest; is well-organized, requires no additional proofing The summary generally describes the session; may have some minor errors to be fixed; may need some adjustment to sentence flow The summary has multiple spelling and typos, is not descriptive enough, or doesn’t align with title
Learning Outcomes

 

Learning outcomes clearly and succinctly describe the anticipated outcomes of the session and generate attendee interest

Outcomes seem reasonable based on session summary and format

Learning outcomes adequately describe the anticipated outcomes of the session Learning outcomes are not clear or hard to understand
Overall Coherence

Does the chosen track and topic match the impression from the title and summary information?

Title, summary, track and topic create a cohesive and clear idea of the session. One or two elements of the proposal don’t match the reviewers’ impression of the proposal. Notable confusion between title, summary and track, topic selections.
Overall Relevance The proposal is of high relevance to current or emerging issues in the profession, Ex Libris products, or the conference theme The proposal is relevant to the profession, Ex Libris products, or the conference theme The proposal does not appear to have value for the program content; is unclear; topic appears to be already addressed in a higher quality proposal