Page Comparison

Participants:

Role	Name	Approval
Solution Architect	Taras Spashchenko	- approved
Java Lead	Dima Tkachenko
Product Owner	Khalilah Gambrell

Spike goals:

1. Define fields set 

2. Define a format for the export document

3. Design an endpoint for export

4. Define possible difficulties

General view of the export tab 

 The first phase of "Cost-per-use" feature should include the option for the user to export title records tied to particular package. As it is seen from the screenshots, export tab location is under the 

"Actions" button. 

1. Define fields set  

Based on

• Title
• Type
• Cost
• Usage
• Cost per use
• % of usage

Below you can find an example table with sample data:

Here is a "Package" column added to provide a context of the package and will not be included to the the result document.

The last column "Product Owner Approval" - defines whether Product owner is agree with suggested format for the values

- will not be included to the result file

- approved to be added to the document

- under discussion

Column Name	Package	Title	Type	Cost	Usage	Cost per use	% of usage	year
Example value	EBSCO Open Access Journals	Writings of Professor B. B. Edwards	Book	500.00	2225	0.22	16	2019
	EBSCO Open Access Journals	The Seasons and the Symphony	Streaming Video	800.00	4544	0.18	20	2019
Product Owner Approval

2. Define a format for the export document

The result format of the export file should be csv.

the name of the file - <package_name>.csv 

Title, Type, Cost, Usage, Cost per use, % of usage 
Writings of Professor B. B. Edwards,Book,500.00,2225,0.22,16 
The Seasons and the Symphony,Streaming Video,800.00,4544, 0.18,20

3. Design an endpoint for export

The "mod-kb-ebsco-java" module should provide an endpoint for the package-title export option.

The definition for the ModuleDescriptor. json file

The definition for the raml file:

... 
/export:
   get:
	 description: |
	   Endpoint provides a cost-per-use information about the titles included into the package in csv format.
 	 responses:
	   200:
         description: OK 
         body:
           text/csv:
			 example:
			   strict: false
			   value: !include examples/export/package_title_get_response.csv

4. Define possible difficulties

The main concern and point to be mentioned in this section - the response time from the APIGEE service for the huge amount of the entities (i.e ~10000 items).

The actual log files can be found

Proposed export flow:

The steps for the export titles process:

1. UI sends a request to the backend to get the csv information about the package titles.
2. Backend is 
   1. fetching title ids from the holdings table
      1. if records are in table - fetch them
      2. if no records - return empty result
   2. define request number needed to be performed to APIGEE
      1. split total title ids/1000 to get request number
      2. prepare batches with title ids max 1000 entities
   3. fetch titles cost-per-use info 
      1. if APIGEE returns [200 OK] - continue processing
      2. if APIGEE returns [<error>] - return error message to the user
   4. calculate title cost-per-use info
   5. send export information in text/csv format
3. UI gets text file and
   1. create a file based on package name
   2. download file for the user

Questions:

Reading: Harvard Views of Readers, Readership, and Reading History

• the max amount of title cos-per-use information should be defined in a separate spike.
  • PoC backend story -

    Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODKBEKBJ-518

  • PoC frontend story -

    Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIEH-990

Update:

for the PoC testing of maximum number of titles that can be exported, the following data used:

Vagrant box - 'testing'

holdings credentials - sandbox

Image Added

Export findings

The OutOfMemoryError occurs for the export titles if their range between 200 000 - 300 000 entities. The current setup for the sandbox KB Credentials does not have such amount.