Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Goals

  • Notetaker: Uschi
  • Discuss Bugfest Feedback (Steffi)
  • CAP Plan Jiras (Erin)
    • https://docs.google.com/spreadsheets/d/19j98iCQs41xIUXLJyArvcZwTKWuCMlZflKYkCHHwdAM/edit?usp=sharing - have you reviewed?
    • The following Jiras did not make the CAP plan. Do we need to discuss?
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUXPROD-1744
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUXPROD-242
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUXPROD-1790
      • Jira
        serverFOLIO Issue Tracker
        serverId6ccf3fe4-3301-368a-983e-20c466b11a49
        keyUXPROD-259
  • Testing for User Fielded Search, and next steps (Uschi; Erin; - see 2019-09-11 Meeting notes for Uschi's test results at the bottom of the page)

...

  • It's difficult to find out which character combinations are allowed → It's not userfriendly
    • Example: no two identical letters in a row
  • Proposal: make the password strength configurable
  • Result / Action item: ???

CAP plan JIRA issues (Erin)

  • Summary of the institution responses to MVP: https://docs.google.com/spreadsheets/d/19j98iCQs41xIUXLJyArvcZwTKWuCMlZflKYkCHHwdAM/edit?usp=sharing
  • Discussing the following Jiras which did not make the CAP plan.
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1744

      • The UM SIG agrees that this is not important for MVP.

    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-242
      • Meaning of CAP comment is unclear. Björn: Perhaps if a field is not delivered (=empty), it will not be overwritten. Phil: But you might want to remove a field in FOLIO during import.

      • Result / Action item: Patty will ask the CAP plan group
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-1790
    • is important for Duke. Was put on hold when the Custom Fields were marked for MVP. But now CF are non-MVP.
    • Patty: meanwhile the CF development team was given other tasks. Notes could be used as an alternative to CF.
    • Erin: What about the National Library of Florence? They need CF for their FOLIO migration.
    • Jira
      serverFOLIO Issue Tracker
      serverId6ccf3fe4-3301-368a-983e-20c466b11a49
      keyUXPROD-259
    • can be closed
    • Result / Action item: Patty will add a comment to that JIRA
  • For Q1, only a few issues will be planned; the focus will be on testing, bugfixing and stabilization.

User search facilities (Uschi)

  • postponed to next meeting

...