Release Candidates

• Code Review

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-434

     / 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-644

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-569-671

    • backend should already have been merged as part of other non-serial agreements
    • should be clear to progress to QA

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-671683

    • Functionality complete
    • Needs tests within components to complete
    • Returned to In Progress  to complete

• QA / UAT

  • Jira Legacy
    server System

    Jira

    JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-

    683
  QA / UAT

  • 680

  • Jira Legacy
    server System

    Jira

    JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-

    680

    569

Items at Risk / Spillover

• Open / Sprint Backlog

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-655

     / 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-427

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-688

• In Progress

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-692

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

  • Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-687

     / 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-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 Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-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 Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-668

     / 

    Jira Legacy
    server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-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 Legacy
      server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-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

Raised

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-696

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-695

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-691

Brought into sprint:  NA

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

• Encompassing feature is 

  Jira Legacy
  server System JIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-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. 

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-681

   - based on publicly available APIs

• Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key ERM-689

   - likely to be higher priority than ERM-681