• Attendees / Apologies
• Upcoming Availability

Sprint Backlog

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-944

   / 
  • some questions raised in Slack

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-945

  • some help needed for ERM-945 
  • should ERM-945 be in settings
    • does this use similar behaviour to picklists?
    • technical architecture doesn't exist yet to support settings
    • would have to be hardcoded in each adaptor
    • preferable to not add more import functionality to mod-agreements?
    • theoretically could use a known model like LASER? 
      • not really
  • ERM-945 is not possible at this stage. Removing from sprint. 
  • Owen Stephens to create Mapping Feature
  • could be worthwhile to align the backend with JDK11 upgrade
  • Ian Ibbotson to set up new task "adding preferred term relationships" linked to new feature

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1010

  • seems clear
  • will get into detail tomorrow
• Pending dev review 

  • Jira
    server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1006

  • Jira
    server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1000

  • Jira
    server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1002

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1032

  • large reports > 1000 resources are not performant
    • due to MCL rendering rather than server response
  • pagination (like with eresources) is an improvement, but still poor user experience
    • problem here is different from eresources, but performance effect would be the same
    • nonetheless, pagination is still useful in this scenario
  • alternatively, rendering progressively is also not performant
  • no explicit requirement to make a report searchable ... however, when not paginated can use browser find
  • using a Load All button will complete, but still takes a long time
    • puts the option in the user's hands
    • some changes needed to the STCOM compoennt 
      • request for changes raised
      • being reviewed by John
  • Summary: use a combination of 

    • Jira
      server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1038

    • Pagination (100 first  + Load More + Load All)
      • Load More trumps Load All if only one button can be presented in MCL

    • Jira
      server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1023

       

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-904

Needs Elaboration

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-999

  • waiting or ERM-1010 feedback

QA / UAT: 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-994

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1024

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1025

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key ERM-1031

10 mins