Linked Data User Story Collection
Would you like to influence the Linked Open Data projects Ex Libris takes up? Do you have ideas for how linked data could enhance your internal workflows or end-user discovery in your Ex Libris products? Help the IGeLU/ELUNA Linked Open Data Working Group (LODWG) communicate your needs to Ex Libris by answering our call for LOD Use Cases/User Stories. Submit one, two, or ten ideas (one at a time, please), and help us improve library workflows and library users’ experience. The Use Cases/User Stories call will be kept open indefinitely.
The LODWG will share submitted stories with the appropriate IGeLU and ELUNA Product Working Groups and Steering Groups (e.g., Alma, Summon, Primo, etc.) on a monthly basis and work with those groups to support appropriate communication with Ex Libris. With your permission, we may make these user stories public.
Submitting a LOD Use Case/User Story does not commit you or your institution to action. However, either a member of the LODWG or Ex Libris may contact you for fuller detail about your proposal. The Working Group may use your stories to inform our planning for future web Town Hall discussions or presentations.
Questions or comments? Please contact David Bucknum of the Linked Open Data Working Group at
What is your name?
What is your job title?
What is your institutional affiliation?
Your User Story
A user story is a concise way to describe a need, who it is for, and what it will result in, and is used to define what is, and is not, in scope for a particular chunk of work. User stories typically follow this pattern: As a <member of a role>, I want to <do or see something new> so that I can <achieve my end goal>
We will ask three questions: what type of user, what is needed, and what is the goal.
For example, the user story for creating this story collection form might be, “As a member of the Linked Open Data Working Group, I want to collect information about linked open data needs from Ex Libris customers so that we can advocate for functionality that will improve library workflows and user interfaces.” User stories are not necessarily succinct, but they provide information about who, what, and outcomes.
As a <kind of user> -- tell us what kind of user
I want to <do something> -- tell us what the user wants to do
So that I can <achieve my end goal> -- what is the goal?
What Ex Libris Products does your story relate to? (Please select all that apply.)
Does this data need to be shown in an interface, made available via API, or both?
Shown in an interface
Made available via API
In an interface AND via API
Any additional details on the value of the enhancement, what the user experience would be, technical details, other use cases for a feature, etc?
Anything else you'd like to tell us?
Never submit passwords through Google Forms.
This form was created inside of University of Michigan.