Enhancement Request Guidelines

Guidelines for creating an actionable enhancement request:

  1. Check the Idea Exchange to see something like your request has already been submitted.
  2. Create a short but descriptive title.
  3. Describe, in as much detail as possible, the functionality being requested, including:
    • Technical requirements
    • Non-technical requirements
    • A clear, concise user story. For example, “As a <<patron, staff, system administrator>>, I would like to <<xxx>> so that I can <<yyy>>”
    • Justification/impact–Why is this enhancement important? What is the impact if this is developed or not developed?
    • Replicate steps with screenshots and other attachments whenever possible.
  4. Once you’re ready, follow the instructions for how to submit your enhancement idea.

 

Tips

  • Write the Idea in a positive statement
    • NOT – ‘There is no…’ or ‘We can’t…’
    • RATHER – ‘We would like the ability to…’ or ‘Allow option for…’
  • Do not include multiple requests within a single enhancement submission.
  • Although you may choose to reference another posted Idea in the context of your own request, do not rely only on providing the reference; provide all the information a user needs to evaluate your request, including the details from the other Idea as appropriate.
  • Describe the desired outcome of the enhancement but do not specify how it should be done; Ex Libris will need to determine development paths and possibilities.
  • Once you’ve created a draft, have someone who is unfamiliar with the workflow read it. Then, incorporate their feedback to make the document clearer.
  • Bugs or functions that don’t work as expected should be submitted as a Support Case. If your submission is the result of a Support Case, include the Case Number for Ex Libris’ reference.

Example

Display parallel titles in Summon

The correction in Summon to index parallel titles as titles (instead of as subtitles) was welcomed; however, the resulting elimination of parallel titles in search results displays was not. In the current iteration of Summon, which parallel title appears in the catalog is solely left to chance, and whichever appears first in a bibliographic record. However, if Summon can display all other title subfields and information in search results, including subfields B, N and P, it should include parallel title information as well.

The lack of parallel titles is problematic for patron search and retrieval. For example, a patron searching for “Pasqualino settebellezze” in our local catalog might think our DVD is the only available copy, since the title they searched for is not visible in our streaming video information.

Summon should still display the parallel titles in search results; preferably exactly as Primo does, with an equals sign between the two parallel titles. Information encoded into bibliographic records is meant to assist patrons with search and retrieval of items, and therefore should be fully visible in search results in our catalogs.

screen shot of results screen screen shot of results screen with parallel title highlighted

These guidelines are based on those developed by the Primo PWG which were based on the references listed below.

References

Collins, Kevin J. and Friesen, Betsy and Greenspun, Cindy and Moore, Lesli. Enhancing Your Enhancement Request. In: ELUNA 2018 Annual Meeting, May 1-4, 2018, Spokane, Washington.

Kucera, Ann, and Pepitone, Anne. Enhancements: Make ’em Sparkle. Webinar, January 28, 2021. Recording | Slides | U-Washington’s enhancement collection form questionnaire

Moore, Lesli M. and Kristin, Sherrie. Enhance Your Request – Tips for better enhancement requests. In: ELUNA 2012 Annual Meeting, May 9-11, 2012, Salt Lake City, Utah.