Page Comparison

Use cases for containers

• The Container record is scheduled for development in Q1 of 2019.
• To prepare, the Acquisitions Small Group is conducting an analysis of features needed for this record.
• They have developed five use cases for containers, which are being used to test workflow and requirements
• Anne-Marie and Dennis reviewed each of the five use cases (slides to come): https://prezi.com/view/WPJokMUQeDxzssMpidlo/
• They then walked through the high-level workflow that will allow a user to create an order:
  • Select order type (one time, ongoing)
  • Select inventory type (container, instance, none)
  • Select PO line format (physical, electronic, mixed)
• Once these steps are complete, the app will present the user with a blank order. The fields will be customized based on the user's selections.
• Discussion:
  • Several people stressed the importance of making sure that it will be possible to move an order from one inventory record to another (container or instance) after creation.
  • A question came up about whether an inventory record will be able to have more than one order attached. This will be possible. An inventory record has no limit on the number of orders attached. Each order behaves independently of the others.
  • Initial feedback was positive, people felt like this approach helps solve some of the issues that came up in the last call related to the conflation of inventory type and PO line format.
  • We still need to see how Orders interacts with ERM. One outstanding question is whether you will need a container record and an ERM record or just the ERM record.
  • Anne-Marie stressed the importance of making sure there is a single place to search for previously purchased resources, regardless of whether they have inventory records or not. This will probably be Codex.
• Dennis plans to walk through the order creation process for each of the five use cases. We will aim to review one use case at next week's meeting.

Results from UAT testing for Finance

• Dennis presented the results of the Finance UAT: https://docs.google.com/presentation/d/1p-HI2JwoIfWDoy_qBWUdhColglJoKg5VLxqZqeVCwNw/edit?usp=sharing
• The functionality tested was creation of the ledger, fund, budget, and fiscal year, along with searches for those objects.
• Six institutions participated.
• The group identified feature-related issues, usability issues, and bugs.
• General satisfaction was medium. The goal is to see this improve as the app gets developed.
• Next steps will be to take action items back to the Acquisitions Small Group, add them to Jira, and schedule for development.
• Discussion
  • Benjamin Ahlborn from Bremen submitted some concerns about the lack of hierarchy available in the app.
  • Creating hierarchy between funds will be possible, but all the features to support that function are not yet available
  • Because Chalmers will not use Finance for their implementation, the app will not be finished in Q4
  • A lot of the missing features will likely be implemented in Q1 or Q2 of 2019
  • Information about the Q4 release and the Q4 dashboard in JIRA can be found here: FOLIO Q4 2018 (Aster) Weekly Status Report
  • The outcome of this discussion was a recommendation that future UATs include a briefing on what functionality is not yet completed, so testers will know what to focus on.

Presentation: https://drive.google.com/open?id=1h2bBjrHdb5UOXm_NnNptucKffvKjQmuI

We didn't get to this topic. It will be postponed until next week.