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
  •   
5 minsPrevious Actions
Test data

20 mins

WIP UpdatesPending: what's dependent?
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-518
  • Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyERM-538
      • no official decision from the project
      • for now, current thinking is to use backend codes to be translated by the frontend
      • can work for static content, but not so with dynamic values
      • instead, could pass code and translated message from backend - would use for static and dynamic content (preferable to have a common approach, so a single component)
      • still an issue if people are setting refdata values - probably need to handle those differently
      • external rather than internal values
      • Owen Stephens  has begun enumerating: 
      • some more thinking to be done on partially editable lists


    20 mins

    WIP Updates
    • Pending: 
      • Jira Legacy
        serverSystem
    JirakeyERM-505
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-376
    Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fc
        • backend done - current export functionality has moved to new url
        • next front-end priority
        • Owen Stephens to update with mockup, including standardise labels
        • Claudia Malzer  to pick up
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-
    362 Jira LegacyserverSystem JiraserverId01505d01-b853-3c2e-90f1-ee9b165564fckeyERM-297
      • 561
        • Mark looking into this, but can't reproduce locally
        • Owen can consistently reproduce
      • what's dependent?
        • nothing
    • In Progress: what's left to do?
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-
    567
      • 578
         / 
        • Jira Legacy
          serverSystem
    Jira
        • JIRA
          serverId01505d01-b853-3c2e-90f1-ee9b165564fc
          keyERM-
    418
  • Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-561
  • In Progress: what's left to do?
        • 580
           error messages added, along with mockups
        • Other applications (eg, OKAPI) may send some JSON errors (404, 500) which may not be easily distinguishable from Agreements errors
        • treat text errors as non-parseable general error (use response 1)
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM
    -578 / 
    Jira Legacy
    serverSystem Jira
    serverId01505d01-b853-3c2e-90f1-ee9b165564fc
    keyERM-580
      • -567
        • can be replicated - what endpoint should be used when testing on console?
          • /packages/import  doesn't seem to work, but should, for local development testing
    • For Review: 
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-558
        • may touch on same code as ERM-376
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-459
        • basics work
        • testing by Owen, Felix and Gill
        • some adjustments to fall out
      • Jira Legacy
        serverSystem
    Jira
      • JIRA
        serverId01505d01-b853-3c2e-90f1-ee9b165564fc
        keyERM-356
      • Jira Legacy
        serverSystem
    Jira
    •   

    10 mins

    New Issues
    • Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-583
    • Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-584
       / 
      Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-463
      • brought into sprint
    • Jira Legacy
      serverSystem JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-585
       / 
      Jira Legacy
      serverSystem
    Jira
    • JIRA
      serverId01505d01-b853-3c2e-90f1-ee9b165564fc
      keyERM-586



    <10 minsAOB
    TimeItemNotesAction Items
    •  

    Accessibility Testing

    • Gill has been doing some accessibility testing
    • Not clear that we have been applying aria consistently/correctly
    • Using Axe to sweep
    • Need some help about what to look for
    • Happy to co-develop a checklist
      • Best to add to the FOLIO wide resource
      • Some caution in Boulder about using checklists - potentially over prescriptive
    • ERM is being used early, so is in a position to lead the way
    • One approach (perhaps better suited to developers) to start with:
      • use the available tooling (Axe) to find the issues
        • Axe is showing a lot of noise from, eg, MCL
        • not easy to identify the signal from the noise here
      • fix what ERM can
      • raise anything to Stripes in the same way
      • see what's left
    • For now, continue with keyboard testing
    • Would be also useful to do screenreader testing, particularly on navigation