Nov 20, 2019 

09:30am ET, 2:30pm UK, 3:30pm Germany

Video Call in FOLIO Slack: #erm-developers

<5 mins

Introductions

• Attendees / Apologies

• Upcoming Availability

5 mins

Previous Actions

• @Owen Stephens to liaise with Benjamin/Felix on test data - TODO

• @steve.osguthorpe  to follow up with @Marc Johnson on translation strategy (following ERM-436)

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

    • Ref Data lists and values in Agreements, Licenses and Local KB Admin 

    • review and comments welcome

  • some more thinking to be done on partially editable lists

20 mins

WIP Updates

• Pending: 

  • https://folio-org.atlassian.net/browse/ERM-376

    • 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

  • https://folio-org.atlassian.net/browse/ERM-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?

  • https://folio-org.atlassian.net/browse/ERM-578 / 

    • https://folio-org.atlassian.net/browse/ERM-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)

  • https://folio-org.atlassian.net/browse/ERM-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: 

  • https://folio-org.atlassian.net/browse/ERM-558

    • may touch on same code as ERM-376

  • https://folio-org.atlassian.net/browse/ERM-459

    • basics work

    • testing by Owen, Felix and Gill

    • some adjustments to fall out

  • https://folio-org.atlassian.net/browse/ERM-356

  • https://folio-org.atlassian.net/browse/ERM-579

• For Release

  • https://issues.folio.org/issues/?jql=Sprint%3D362%20and%20status%20%3D%20"In%20QA"

10 mins

New Issues

• https://folio-org.atlassian.net/browse/ERM-583

• https://folio-org.atlassian.net/browse/ERM-584 / https://folio-org.atlassian.net/browse/ERM-463

•  

  • brought into sprint

• https://folio-org.atlassian.net/browse/ERM-585 / https://folio-org.atlassian.net/browse/ERM-586

  • @Gill Osguthorpe  to confirm whether margin is round all

<10 mins

AOB

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