ELUNA ENHANCEMENT PROCESS:

HOW TO CRAFT MEANINGFUL ENHANCEMENTS

ANNE PEPITONE

Chair, ELUNA Primo Working Group

/Enhancements Co-Coordinator

----

Head, Integrated Library Systems

University of Washington

MARY GRENCI

ELUNA ALMA Enhancements Coordinator

----

Interim Director, Collection Strategies

University of Oregon

01 - ALMA VS PRIMO

02- SCOPE

03 - ENGAGEMENT

04 - BEHIND SCENES

05 - SCHEDULE

06 - INSTITUTION TIPS

• Short & Descriptive

TITLE

• Which module in the system does this live in?

MODULE

• Description of the functionality
• Technical Requirements
• Non-Technical Requirements

DESCRIPTION

• Is the functionality for the Network Zone?
• Will the functionality effect consortial work or workflows?

CONSORTIUM

• Use case for the enhancement
• Why is it important?
• What is the impact if this is developed? What is the impact if this is not developed?

IMPACT

• What would it look like if this was developed?
• How would the system function differently?

EXPECTED OUTCOME

• Short & Descriptive

TITLE

• Description of the functionality
• Technical Requirements
• Non-Technical Requirements

DESCRIPTION

• Why is it important?
• What is the impact if this is developed? What is the impact if this is not developed?

JUSTIFICATION

• What is the use case for the enhancement?

USE CASE

• Complicated for vetting, pointing and voting
• Often get rejected
• Can take more complexity points than we have available

MULTI-PART ENHANCEMENTS

ARE NOT ENCOURAGED

• Encouraged not required
• Easier to get through the process
• Better chance in voting
• Provides more clarity for all parties

BREAK ENHANCEMENTS INTO SMALLER PIECES

• Use information for someone who is aware of the details of the request
• You can enter details for someone other than the NERS contact
• Keep it up to date

PROVIDE CONTACT

INFORMATION FOR PROPER STAFF

• Do not ghost coordinators
• Be prepared to work with coordinators
• Be quick with responses

BE RESPONSIVE

REQUESTS ARE EXPORTED FROM NERS SYSTEM

ALMA PRODUCT WORKING

GROUP [PWG] SUBGROUPS PERFORM IN-DEPTH REVIEW

ENHANCEMENT COORDINATOR CLEANs UP DATA

SUBMITTERS ARE NOTIFIED IF CHANGES ARE NEEDED

PREPARATION OF BALLOT AND COMMUNICATIONS

01

02

03

04

05

REQUESTS ARE EXPORTED FROM NERS SYSTEM

PRIMO PRODUCT WORKING

GROUPS [PWG] MEET & ASSIGN REQUESTS

ENHANCEMENT COORDINATORS CLEAN UP DATA

SUBMITTERS NOTIFIED IF CLARIFICATION/CHANGES ARE NEEDED

PREPARATION OF BALLOT AND COMMUNICATIONS

01

02

03

04

05

TOP 20(PRIMO)/TOP 25(ALMA)

SENT TO EX LIBRIS FOR POINTING

DEVELOPMENT PROPOSES SOLUTIONS

FOR EACH ENHANCEMENT

EX LIBRIS AND PWG MEMBERS DISCUSS EACH ENHANCEMENT

EX LIBRIS GETS INPUT ON DEVELOPMENT SOLUTIONS FROM SUBMITTERS AND PWG MEMBERS

PREPARATION OF BALLOT FOR ROUND TWO OF VOTING

01

02

03

05

06

EX LIBRIS POINTS/REJECTS ENHANCEMENTS BASED ON COMPLEXITY

04

• Create a form for staff to fill out
• Sample form
• Remind staff to submit an enhancement request when indicated in Salesforce cases
• Create a spreadsheet for stakeholders when the ballot is live--have them rank priority

SIMPLIFY THE PROCESS

• Is it a bug/defect/regression?
• Is it something that should work or is it already in the system?
• Is it an accessibility issue?
• When in doubt file a case

​

SALESFORCE CASE

• Created to help the Ex Libris product management teams to set development priorities
• Not contractually bound to develop anything on the site

IDEA EXCHANGE

• The only channel for Roadmap commitments
• Contractually bound to developing enhancements from the IGeLU and ELUNA communities within the annual point allotments

NERS ENHANCEMENT

01

02

03

HOW CAN WE MAKE THE PROCESS MORE MANAGABLE?

IS THERE ANYTHING THAT WOULD HELP AT THE ALLIANCE LEVEL?

SHOULD WE MERGE ALMA AND PRIMO ENHANCEMENT CYCLES?

01

02

03