Page Comparison

Moved all issues relating to Invoicing to Q12019 as they are not priority for the upcoming go-live. Focus will shift to Receiving.

• UXPROD-727, UXPROD-783 still require analysis and approval by the larger SIG
• UXPROD-717, UXPROD-721, UXPROD-719, UXPROD-720, UXPROD-196, UXPROD-703, UXPROD-694, UXPROD-695 Have been moved to make room for checkin and receiving.

Moved issues relating to Finance

• UXPROD-203, UXPROD-198 Rollover and the finance dashboard will need to be address post Q4.
• UXPROD-777, UXPROD-696, require further analysis and approval by the SIG.

At Risk/Will Split

• UXPROD-861 Work slowing on Finance app means the remainder of this task may need to be postponed or split.
• UXPROD-189 Activity log is not needed for upcoming go live and may need to be postponed to make room for other work.
• UXPROD-1026 Will split into respective modules to as work is focused on Orders, Vendor and Receiving for Q4

Adding to Q4 but at risk depending on capacity

• UXPROD-187, UXPROD-186 Recent meetings with early adopters have Identified these as a higher priority than the finance application.

• Moved Paging Requests feature (UXPROD-272) out of Q4 and into Q1 2019. There are some questions we still need to answer (with SIG) about this feature:
  1. Are paging requests really needed if FOLIO supports the ability to configure which item states holds can be put on? This configurability is something we have been told we must absolutely have. If the only difference between a hold and a page is the item states on which they are allowed, I am not sure both are necessary
  2. Also, it seems that paging requests are not really any different from recalls and holds vis-a-vis how fulfillment is handled. Therefore, if we do go ahead with this feature, much of what is needed will already have been covered by UXPROD-118.

  Given the remaining uncertainty and the fact that the development scope on this is smaller than originally thought, I think it makes sense to move this out of Q4 and into Q1 2019.

• Removed Manual Transfer Fee/Fine UXPROD-1117 (and the related settings UXPROD-986 and report UXPROD-839) from Q4 2018 after Chalmers University downgraded their ranking of these features. Will focus instead on bugs and tasks related to implemented features (in addition to implementing new features manual patron blocks and user permissions). 

• Moved UXPDROD-1124, UXPROD-1125, UXPROD-1126, and UXPROD-1220 from Q4 2018 to Q1 2019. These features are for adding tags functionality to various types of acquisitions and data import records.

2018-11-05

• Split Requests Permissions into Requests Permissions (Simple) (UXPROD-1279, targeted for Q4) and Requests Permissions (Advanced/Action-Based) (UXPROD-236). This is because:
  • We need to get at least a basic requests permission functioning for Chalmers. The more granular permissions can wait.
  • Also, since the basic permission is UI-only, we should be able to squeeze it in given the UI devs are often blocked on backend work
  • Finally, the more granular/advanced requests permissions are (to some extent) blocked awaiting "Action-Based Permissions" design and implementation (FOLIO-1504)
• Added Requests: access to list of requests via links in the item detail and user detail (UXPROD-235) to Q4 as it was UI-only and we had excess UI dev capacity on the Core team while blocked awaiting backend work.

• Split Permissions into Permissions (Simple) (UXPROD-238, targeted for Q4) and Permissions (Advanced/Action-Based) (UXPROD-1251)

• Still finalizing UI screens for Data Import mappings and logs.
• Many revisions/refinements to overall Data Import architecture document and diagrams, based on feedback from Lead Architects.
• Discussions with several related POs & Dev teams to determine responsibility for cross-app issues (e.g. File upload, ISBN handling rules)

• Requests - Have implemented a simple filter of the Requests app for a v1 requests queue ( UIREQ-122). Dedicated request queue page (UIREQ-112) has been deferred
• Locations and service points
  • Switching direction of the relationship. No longer support adding locations to service points. Instead, service points will be added to locations (to ensure each location has at least one primary SP)
  • May have time to pick up some of the lower priority UX improvements for Location CRUD, as they are UI only and many other stories are blocked awaiting backend support: UIORG-92,  UIORG-93, UIORG-94, UIORG-117.