Beginning on 9/18 you will be able to change your enterprise password from within Jira!

Skip to end of metadata
Go to start of metadata
Target release3.x or 4.x
Epic SIMPLY-52 - Getting issue details... STATUS
Document statusDRAFT
Document owner

James English [X]

DesignerTBD
DevelopersTBD
QATBD

Goals

  • Improve user experience for patrons new to SimplyE (user On-boarding and app orientation)
  • Improve user experience connecting patrons to their respective library (library discovery and registry support)

Background and strategic fit

Strategic alignment goal to improve user ratings and grow adoption

Assumptions

  • Resources available

Requirements

#TitleUser StoryImportanceNotes
1

SIMPLY-1015

SIMPLY-120 - Getting issue details... STATUS

  • As a product manager I want libraries who deploy simplyE middleware or publish compatible OPDS catalogs to be able to have their collection easily discovered and their users easily connect to that library in the mobile clients
  • As an engineer, I want the app to be able to be able to dynamically find libraries with circ managers it can connect users to so I don't have to build and release new versions of the app for each new library.
Must have

Libraries will have to be compliant with DCMA safe harbor provisions and accept NYPL terms of use to be in the registry

Libraries will need to register through the circulation admin panel their library

Institutions that run compatible OPDS catalogs need a way to be discoverable in the app

2 SIMPLY-54 - Getting issue details... STATUS
  • As a user I want to explore what libraries use SimplyE and add them to my app.
  • As a user I want to find libraries near me
  • As a user I want to add my libraries to one app.
  • As a library I want to communicate my brand to SimplyE users who could be a member of my library.
  • As a nonprofit interested in providing access to the ebooks I want my collection in SimplyE.
Must haveMere location is good for connecting people to their local library. However, for libraries that are not geographically bound, geolocation may add to many libraries to the result list or eliminate users from exploring and discovering new libraries.

User interaction and design

To be developed

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing