You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target release4.x
Epic Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Document statusDRAFT
Document owner

Unknown User (jamesenglish)

DesignerUnknown User (sharondenning)
DevelopersUnknown User (gregoryoneill) Unknown User (deansilfen) Unknown User (winniequinn)
QAUnknown User (josephdalton) Unknown User (willaarmstrong)

Goals

  • Improve user experience for patrons new to SimplyE (user On-boarding and app orientation)
  • Improve user experience connecting to their respective library (library discovery and registry support)
  • Improve support for non-english languages or low reading level (app localization, content word pronouncement, content word translation)
  • Improve reading experience for ePubs (R2 integration)
  • Improve search experience for content (dedicated search tab and improved search indexing)

Background and strategic fit

Strategic alignment goal to improve user ratings and grow adoption

Assumptions

  • Resources available

Requirements

#TitleUser StoryImportanceNotes
1

SIMPLY-53

SIMPLY-120

  • 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

2SIMPLY-54
  • 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.
3SIMPLY-55

Provide user notification support in SimplyE for iOS and Android regardless of vendor content provider limitations.

  • As a user I want to get a notification when my reserved books are available for download. SIMPLY-192
  • As a user I want to know when my borrowed ebooks are about to expire SIMPLY_193
  • As a user I want to know when my reservation checkout grace period is to expire.  SIMPLY-194
  • As a user I want to opt into notifications SIMPLY-195
  • As a user I want to select / subscribe to certain notifications SIMPLY-196
  • As a user I want to configure how my app notifies me. SIMPLY-197
 Must Have 
  • Vendor Notification Systems: Email push notifications from vendors can hijack the user or confuse them. Vendors push notifications from their systems through email. However, they do not provide subscription services for machine based API access to queued change events or notification queues which SimplyE can reliably integrate from vendor to vendor. These independent systems allow the vendor to manage the user experience by drawing users into their app through email notifications and potentially confusing the user.
  • Security and Privacy: Vendors such as Overdrive require a users security credentials in order to access the their holds and loans. This creates a challenge for SimplyE in that storing such information is against is principle privacy and security design and is not consistent across vendors. Therefore, SimplyE client initiated queries against a patron distributor bookshelf. This requires SimplyE to use a client initiated notification strategy vs a server based push notification strategy.
  • Polling Based Notifications
    Because the Circulation Manager is polling providers bookshelf only when prompted by the user, the mobile app can provide polling based notifications by asking the cric manager for an update of the users bookshelf on a regular basis. This server side strategy is due to the fact that the users ide and pin are required for access the service providers API in exchange for a temp token. Because SimplyE servers do not store a user’s service provider credentials, updates are user initiated from their client application. In other words, the users privacy and security is in their possession, not the libraries. While this may not allow Push based notifications it does enable near real time notifications based on the client's ability to initiate updates in the background while the user is “in” the app.

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

  • No labels