Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Meeting Details

Date
 
Time

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

LocationVideo Call in FOLIO Slack: #erm-developers


Apologies

Discussion items

Time

Item

Notes

Action Items

<5 minsIntroductions


20 minsSprint Cutoff

Release Candidates

  • Code Review

    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-434
       / 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-644
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-671
      • backend should already have been merged as part of other non-serial agreements
      • should be clear to progress to QA
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-683
      • Functionality complete
      • Needs tests within components to complete
      • Returned to In Progress  to complete
  • QA / UAT

    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-680

    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-569

Items at Risk / Spillover

  • Open / Sprint Backlog
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-655
       / 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-427
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-688
  • In Progress
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-692
      • one test left to do, and then should be good to code review
      • Mark is liaising
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-687
       / 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-690
       
      • 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 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-688
        )
        • 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
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-668
       / 
      Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyERM-684
      • 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 
        Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyERM-704
      • 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

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-696
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-695
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-691

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 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyUXPROD-2251
  • 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 minsAOB

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyUXPROD-2081
 

  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-681
     - based on publicly available APIs
  • Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyERM-689
     - likely to be higher priority than ERM-681
  •