Page Comparison

As mentioned at last week's meeting, the Prokopovych team has 2.5 FTE BE devs on paper, but only about 1.0 FTE in actuality.  We need to focus our limited BE capacity on what is most important.  Aside from critical bugs that pop up with Juniper, what should we focus on first?

• UICHKOUT-726 (SPIKE: Improve check-out speed) – this is a P2 because you are able to check-out items, but it takes too long - starting ticket is CIRC-1181 (Research checkout speed)
• UICHKIN-269 (SPIKE: Improve check-in speed) – this is a P2 because you are able to check-in items, but it takes too long - starting ticket is CIRC-1182 (Research check-in speed)
• Karate tests

(Note:  Code freeze for Kiwi is in less than two months, on September 17th.)

Creating Karate tests is important, but we really need to figure out how to improve performance with checkouts and check-ins.  It is summer now, so performance will get worse when the fall semester starts.   The likelihood that we will have a long-term fix in place by then is slim, but we need to start on this ASAP.  

The team is focused on fixing P1 and P2 BE bugs right now.  We will see if another team can donate a BE dev with circ experience to work on bugs while our BE dev focuses on this research. 

We will start with checkout given patron is standing at the circ desk waiting (while check-in is usually completed without the patron standing there). Our person should work with Martin.  We should define both short-term and long-term solutions. 

Need to include test where data import is occurring while doing checkouts and check-ins. 

UXPROD-3046

Planning roll out of implementation of Elasticsearch in Inventory - timeline: Lotus? 

The current technical approach for search in Inventory is using PostgreSQL, JSONB columns, CQL and RAML Module Builder. Using Elastic Search as a long term solution has been explored Autumn 2020 - Spring 2021 (POC). We should now plan for when to swap the current solution and use Elasticsearch in production.