Page Comparison

...

1. Could several integration details be created for each vendor?

   1. JR: Multiple integrations are possible for each vendor. We plan to separate order integrations from claiming integrations (i.e. separate integrations for ordering and claiming are required), but we are also adding the ability to copy integrations to simplify that.

   2. Please see:

      1. Jira Legacy
         server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIORGS-441

      2. Jira Legacy
         server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UIORGS-442

2. If there are more then one integration details per vendor available:

   1. Could one of them be selected manually in each order?

      1. JR: We are evaluating the best approaches for this. Ideally it would be programmatic, based on location, custom field, or similar. Manual selection is also a possibility, but for large libraries, might be cumbersome.

      2. JR: Update - based on feedback from the SIG, it appears the preferred method is to apply integration based on account number.

   2. Could one of them be defined as default value in the order templates?

      1. JR: That is definitely a strong possibility.

...

1. Can orders be filtered by the expected receipt date before dispatch? 

   1. Goal: It should be possible to manually change the expected delivery date in order to delay the reminder. 

   2. Note: There are mock-ups from Dennis Bridges that describe similar scenarios 

      1. 2023-09-12 Acquisitions Meeting notes

      2. 2023-10-03 Acquisitions Meeting notes

         1. JR: Delay claim functionality already exists. We are planning an interface to allow this in a dedicated claims space rather than having to go title-by-title

Related links

https://miro.com/app/board/uXjVKGhaLwU=/?share_link_id=21429580107 (Please note that the Miro link is a whiteboard/work in progress for mocks and consideration of approaches)