Feb 5, 2020 

09:30am ET, 2:30pm UK, 3:30pm Germany

Video Call in FOLIO Slack: #erm-developers

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

20 mins

Sprint Cutoff

Release Candidates

• Code Review

  • https://folio-org.atlassian.net/browse/ERM-434 / https://folio-org.atlassian.net/browse/ERM-644

  • https://folio-org.atlassian.net/browse/ERM-671

    • backend should already have been merged as part of other non-serial agreements

    • should be clear to progress to QA

  • https://folio-org.atlassian.net/browse/ERM-683

    • Functionality complete

    • Needs tests within components to complete

    • Returned to In Progress  to complete

• QA / UAT

  • https://folio-org.atlassian.net/browse/ERM-680

  • https://folio-org.atlassian.net/browse/ERM-569

Items at Risk / Spillover

• Open / Sprint Backlog

  • https://folio-org.atlassian.net/browse/ERM-655 / https://folio-org.atlassian.net/browse/ERM-427

  • ERM-688: Define UI for setting additional data required for importing KBART filesClosedPreview

• In Progress

  • https://folio-org.atlassian.net/browse/ERM-692

    • one test left to do, and then should be good to code review

    • Mark is liaising

  • ERM-687: Create tsv parserClosedPreview / ERM-690: Implement KBART importClosedPreview 

    • can use curl to get a kbart file and create a package

    • cannot create searchable titleInstances yet

      • would need to have a type of 'Electronic', which should fix it

    • need to modify the ingest service to ensure the right publication dates are allocated 

    • then ready to move onto the UI (as defined in ERM-688: Define UI for setting additional data required for importing KBART filesClosedPreview)

      • can be simplified if needed to prioritise update vs new use cases

      • @Owen Stephens to confirm via discrete subtasks

    • query about whether title enrichment is being done - currently not defined as a story/bug

      • there may be stubs, but no concrete functionality related to data import routine

      • to follow via Owen

  • ERM-668: Add ability to search/filter licenses based on custom properties (aka "terms")ClosedPreview / ERM-684: Create query builder for license termsClosedPreview

    • proof of concept went up for Owen this morning

    • feedback has been very positive ("sick")

      • searching is a good starting point with this

      • next thing is the types of licenses to compare

      • more work to do on collecting use cases, eg, internal notes across results

    • filters essentially work

    • waiting on text-contains backend, to be done as part of ERM-704: Backend to handle contains and not containsClosedPreview

    • some better ui and cleanup needed for production

    • parent issue is stable and now transitioned to Open 

    • do not have the ability to find licenses where terms are not set. 

      • some ui/designs mocked up

      • question marks about how that could be implemented

      • =null wouldn't work as nothing is null

      • that part of it will be pushed back - @Owen Stephens to create separate story for future rescheduling

15 mins

New Issues

Raised

• ERM-696: Agreements: Reason for closure is not displayedClosedPreview

• ERM-695: When switching between Jobs in KB Local Admin ensure that correct logs are displayedClosedPreview

• ERM-691: Current period note should display below the Cancellation deadlineClosedPreview

Brought into sprint: NA

10 mins

Next Sprint

Looking at bringing in data from external systems (specifically LASER) to create licenses and agreements. 

• Encompassing feature is UXPROD-2251: LAS:eR / Folio ERM integrationClosedPreview. 

• more work being done on the data model

• makes sense to start from licenses

• then move on to iterating over the subscriptions to create agreements and packages

• institutional rather than consortial, and non-editable

Next sprint will likely focus on whether we can get the data across with provenance (mostly backend). 

From UI/UX perspective worth thinking about how to prevent edits. 

<10 mins

AOB

https://folio-org.atlassian.net/browse/UXPROD-2081 

• https://folio-org.atlassian.net/browse/ERM-681 - based on publicly available APIs

• https://folio-org.atlassian.net/browse/ERM-689 - likely to be higher priority than ERM-681