SPIKE: Review Cost Per Use Controller APIS and Authentication documentation
Priority
Labels
Environment
Template
Description
Development Team
Release
Story Points
Sprint
Attachments
- 27 Aug 2020, 02:40 PM
defines
relates to
Checklist
hideTestRail: Results
Activity
Khalilah Gambrell August 27, 2020 at 2:57 PM
@Natalia Zaitseva and @Sobha Duvvuri, although I have placed Usage Consolidation under eholdings settings, please note that usage information may display at some point on an Agreement record. Unsure if that will change the placement of the Usage Consolidation settings.
Khalilah Gambrell August 27, 2020 at 12:35 PM
@Natalia Zaitseva, adding a screenshot
Natalia Zaitseva August 27, 2020 at 11:27 AM
document with questions - https://folio-org.atlassian.net/wiki/display/FOLIJET/SPIKE%3A+Investigate+Cost+Per+Use+Controller+API
Khalilah Gambrell August 25, 2020 at 6:26 PMEdited
@Natalia Zaitseva and @Oleksii Petrenko, potentially we can break up this spike into multiple spikes. Here is my suggested outlined. Each number represents a spike.
Authentication and Storing credentials
Storing Usage Consolidation settings (e.g. Fiscal start month)
Multi-libraries in a single tenant handling (See story - (https://folio-org.atlassian.net/browse/MODKBEKBJ-471)
Display Usage Consolidation on a Package record
display selected titles in a package
export titles
calculate cost and cost per use information
Display Usage consolidation on a Package+title record
calculate cost, cost per use, and usage information
display usage statistics (month to month)
Display Usage consolidation on title record
calculate cost, cost per use, and usage information
display usage statistics (month to month)
Objective:
Review cost per use controller apis and authentication documents
Outcome:
Create spikes to better understand APIS
Create design documentation stories to support implementation of EBSCO Usage Consolidation - FOLIO Integration