Skip to end of banner
Go to start of banner

2020-02-05 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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

    • ERM-434 - Getting issue details... STATUS  /  ERM-644 - Getting issue details... STATUS
    • ERM-671 - Getting issue details... STATUS
      • backend should already have been merged as part of other non-serial agreements
      • should be clear to progress to QA
    • ERM-683 - Getting issue details... STATUS
      • Functionality complete
      • Needs tests within components to complete
      • Returned to In Progress  to complete
  • QA / UAT

    • ERM-680 - Getting issue details... STATUS

    • ERM-569 - Getting issue details... STATUS

Items at Risk / Spillover

  • Open / Sprint Backlog
    • ERM-655 - Getting issue details... STATUS  /  ERM-427 - Getting issue details... STATUS
    • ERM-688 - Getting issue details... STATUS
  • In Progress
    • ERM-692 - Getting issue details... STATUS
      • one test left to do, and then should be good to code review
      • Mark is liaising
    • ERM-687 - Getting issue details... STATUS  /  ERM-690 - Getting issue details... STATUS  
      • 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 - Getting issue details... STATUS )
        • can be simplified if needed to prioritise update vs new use cases
        • Owen Stephens to confirm via subtasks
    • ERM-668 - Getting issue details... STATUS  /  ERM-684 - Getting issue details... STATUS
      • 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 - Getting issue details... STATUS
      • 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 - Getting issue details... STATUS
  • ERM-695 - Getting issue details... STATUS
  • ERM-691 - Getting issue details... STATUS

Brought into sprint: 


10 mins

Next Sprint



<10 minsAOB

UXPROD-2081 - Getting issue details... STATUS  

  • ERM-681 - Getting issue details... STATUS
  • ERM-689 - Getting issue details... STATUS



  •  
  • No labels