FOLIO Q4 2018 Weekly Status Report

Jakub Skoczen

• Started sprint 53

• Functional work items update:

  • CIRC-154: check-in by barcode API (DONE, Marc)

  • CIRC-146: Change status to "in transit" upon check-in (DONE, Marc)

  • Above means that all UXPROD-601 stories are now completed and wait for review (UICHKIN-17, UICHKIN-40, UICHKIN-41, UICHKIN-46, UICHKIN-60)
  • UXPROD-118 work, considered at risk, will go ahead in Q4 (Dec/Jan) but likely we will decide against shipping it with Q4

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (DONE , Kurt) required for UIU-485 (IN REVIEW, Aditya)

  • CIRC-156: dereference patron group ID to display the name along with the request (DONE, Kurt) UIREQ-114 is now IN REVIEW

• Q4 Release Management updates:

  • mod-feefines is required by FOLIO core modules (ui-users) but the release has not been made on time. CT made an out-of-band release. Trying to communicate with UNAM on the matter.
  • External modules (Acq, ERM, MarcCat, etc) release deadline was last Friday (2018-12-07), most modules have been released on time but there are cases where some releases have not been made properly (Acq) or are still pending (mod/ui-marccat, ui-licences). CT is communicating with the POs and leads to try to help with those releases.
  • This Friday (2018-12-14) is core UI modules release deadline. After all core UI modules are released, the DevOps team will attempt to build a fresh Q4 environment (most likely Monday 2018-12-17). The deadline for creating the environment is on Friday
  • Q4 Release Management: all modules, interfaces (APIs) and their Q4 versions are tracked in this spreadsheet (updated at real-time):
    https://docs.google.com/spreadsheets/d/1m966Ch822PUtsdvo01mS605ndB08ZhT7RRP3tnBRuX0/edit
  • Q4 Release is going according to plan:
    https://docs.google.com/spreadsheets/d/1-4fMUyfnMhaMoJuEiwaABGu7ZzePvzhjya-nyV3dvvs/edit#gid=0
    
    

• OKAPI/RMB, Performance NFRs

• Performance: MODINVSTOR-215: Julian implements solution agreed with EPAM DBAs throuh RMB-301 (IN PROGRESS), unfortunately no status since last week.

• Starting from this week and intensifying next week core back-enders will focus on various performance issues (Adam, Julian, Jeremy, William). Heikki is going to be away until the end of the year. Nassib will act as a partial replacement.

• Reference data loading functionality RMB-296 (DONE) and initial implementation in one of the modules (mod-inventory-storage) MODINVSTOR-216) is completed. We have decided against shipping the functionality in Q4 due to necessary deployment changes. It will be shipped with Q1 and all modules will be updated to implement this functionality.
  
  

• Devops:

  • Two new environments created: snapshot-core and snapshot-stable-core, with core modules only to allow for API updates

  • Working on non-standard deployment procedure to included edge-oai-pmh module in Q4, we will adress the tech debt around this in Q1.

  • FOLIO-1577: as mentioned above, an attempt to create Q4 environment will be made on Monday, Okapi can now generate a dependency graph to ease tracking dependency problems

  • FOLIO-1548: STCLI-114 IN PROGRESS (ability to run modules locally and have them communicate with the black-box)

• Quality/Testing:
  • Initial test coverage for nightmare (integration) UI tests has been completed for selected modules (ui-users) and shows coverage on the level of 30% percent. More work is needed to capture full coverage across core FOLIO modules. This work is grouped under FOLIO-1618, tasks will be handed out from next week.
  • 

Cate Boerema (Deactivated)

• Index Data having company meetup so I am running the Core team roundups
• Gap analysis team is working very hard to get the Q1 planning in place. This means:
  • UXPROD feature refactoring
  • Feature distribution across teams
  • Feature estimating
• Risk: there is a LOT of concurrent circulation work that needs to happen. We need to be very careful about how this is distributed across teams.

• Goal is to have the cap plan updated tomorrow

Getting issues...

Getting issues...

Cate Boerema (Deactivated)

• Several Core team Q4 features are at risk, but I am reluctant to move them out of the quarter, as we are hoping we can make at least some progress before feature freeze. POs for other teams are probably doing the same. Here's the full list of at-risk features across teams. There are 22 (of the total 107 targeted).
• I have tagged the features and stories coming out of the November Chalmers visit. View the list here.
• Circulation is still a risk area for Chalmers go-live. Specifically:
  • Request policy still be designed (re-designed) and some elements may be moving to the Loan policy. Cate, Sean and Tania working to get this nailed down for the developers asap
  • While some aspects of circulation are independent enough to be worked by a team other teams (e.g. loan and request policy CRUD, extending the loan rules editor) making these new policies effective will really need to be done by the Core team.
  • Making policies effective needs to be done in exactly the same code being modified for other ongoing circulation features such as in transit to home location and fulfilling pickup requests. Not a lot of work can be done concurrently here.
  • Title requests - still not clear what the plan is here.
  • Library opening hours calendar - Sean is finding bugs and issues with this Qulto-developed app. Which team is responsible for maintaining it? Sean would be the best fit from a PO perspective given his other features are primary consumers of calendar data.
  • Here is a list of circ related features likely needed by Chalmers to go live which will need to carry over in some form to Q1. The list is long and there are dependencies.
• Leipzig is hosting a self-built article index and are providing the data to a number of German libraries, most of them using vuFind discovery systems (are mostly hosted by Leipzig). The infrastructure/community is named finc. They are now getting ready to re-implement their configuration software on FOLIO. The code will of course be open source and re-usable, if there are any institutions interested in this kind of set-up. I have implemented a JIRA project (UIFC) for them to track their requirements.

Jakub Skoczen

• Started sprint 52

• Backend issues critical for completing functional work:

  • CIRC-154: check-in by barcode API (IN PROGRESS by Marc) will be completed by the end of the week.

  • CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS byt Marc) will be completed by the end of the week.

  • CIRC-150: validation of check-in/check-out SP during loan CRUD (IN PROGRESS by Kurt) required for UIU-485, will be completed by the end of the day

  • CIRC-156: dereference patron group ID to display the name along with the request (DONE, Kurt) no longer blocks UIREQ-114, needs handling of permissions
    
    

• Cross team

  • Core backend API freeze is this Friday (2018-11-30)
  • Q4 Release Management: send a reminder about upcoming external module release deadline (2018-12-07) to all POs listed in UXPROD. Asked them to update information (modules, versions, lead) in the Q4 RM spreadsheet:
    https://docs.google.com/spreadsheets/d/1m966Ch822PUtsdvo01mS605ndB08ZhT7RRP3tnBRuX0/edit
  • Q4 Release Timeline will be reviewed again during today's sprint review:
    https://docs.google.com/spreadsheets/d/1-4fMUyfnMhaMoJuEiwaABGu7ZzePvzhjya-nyV3dvvs/edit#gid=0
    
    

  
  

• OKAPI/RMB, Performance NFRs

• MODINVSTOR-215: Julian implements solution agreed with EPAM DBAs, see RMB-301 (IN PROGRESS)

• Adam is working on reference data loading; RMB-296 (DONE) and MODINVSTOR-216 (IN PROGRESS)
  
  

• Devops:

  • FOLIO-1577: two new Okapi feature implemented (OKAPI-683 and OKAPI-684) to better report dependency issues and catch unreleased dependencies at release time. John will perform a Q4 build on Monday (2018-12-03)

  • FOLIO-1548: STCLI-15 completed, STCLI-114 (ability to run modules locally and have them communicate with the black-box) starting

Getting issues...

Getting issues...