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 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 - 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

Raised

• ERM-696 - Getting issue details... STATUS
• ERM-695 - Getting issue details... STATUS
• ERM-691 - Getting issue details... STATUS

Brought into sprint: NA

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

• Encompassing feature is  UXPROD-2251 - Getting issue details... STATUS . 
• 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. 

UXPROD-2081 - Getting issue details... STATUS  

• ERM-681 - Getting issue details... STATUS  - based on publicly available APIs
• ERM-689 - Getting issue details... STATUS  - likely to be higher priority than ERM-681