Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-1018] Ability to manage Donor information within FOLIO Created: 08/Aug/18  Updated: 05/Feb/24

Status: In Review
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P3
Reporter: Dennis Bridges Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority3, acquisitions, integration, loc, orders, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-organizations-with-donor.png     PNG File 2-edit-organizations-with-donor.png     PNG File 2-pol-donor.png     PNG File Donor modal mock.png     PNG File fund-with-donor-mock-1.png    
Issue links:
Continues
is continued by UXPROD-4666 Associate Donor organizations with In... Draft
Defines
is defined by MODFIN-333 BE - Add donor info to Fund Closed
is defined by MODORDERS-944 BE - Add donor info to POL Closed
is defined by MODORG-59 BE - Introduce 'isDonor' indicator fo... Closed
is defined by UIF-473 Add donor info to Fund Closed
is defined by UIOR-1147 Add donor info to POL Closed
is defined by UIOR-1150 Add donor info to Order facets Closed
is defined by UIORGS-383 Designate Organization as donor Closed
is defined by UIORGS-395 View list of donors on edit screen Closed
is defined by UIORGS-398 Modify summary display in organizatio... Closed
is defined by UIORGS-399 Add Donor to Organization facets & fi... Closed
is defined by UIPFO-46 Create or add list of donors Closed
is defined by UISACQCOMP-166 View list of donors Closed
is defined by MODORGSTOR-153 BE - Implement API for Privileged con... Closed
is defined by UIOR-1148 Populate donor info from fund into POL Closed
is defined by UIOR-1149 Disable donor field in POL Closed
is defined by UIORGS-397 Create Privileged donor information a... Closed
Relates
relates to UIIN-255 Item Record. Accordion Acquisitions. ... Open
relates to UIIN-237 Holdings Record. Accordion Acquisitio... Draft
relates to UXPROD-1141 Create, close, cancel, Purchase Orders Closed
Release: Quesnelia (R1 2024)
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: Medium < 5 days
Front End Estimator: Mikita Siadykh
Front-End Confidence factor: 70%
Back End Estimate: Large < 10 days
Back End Estimator: Serhii_Nosko
Back-End Confidence factor: 80%
Development Team: Thunderjet
UX Lead: Joseph Reimers
Kiwi Planning Points (DO NOT CHANGE): 10
PO Rank: 45.9
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R5
Rank: hbz (TBD): R5
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: Ability to enter donor information during the order process.  Provide a mechanism for this be passed to Inventory for display as an electronic bookplate or similar. Provide a mechanism for identifying donors, donated materials, and materials acquired with donated funds.

Use cases:

  • Donor information is input into the order so that it can be carried through to discovery as a bookplate.
  • Librarian needs to denote in the order that there were multiple donors
  • Donors wish to remain anonymous. Not having any credit display publicly
  • Donors do not wish to remain anonymous. They would appreciate having a credit display publicly
  • It is critical that we are able to attribute purchases to certain donors and to report back how much and on what we have spent their money
  • Some donors want to remain anonymous until a certain time or for a certain time and ideally we could set these details for a donation and not need to come back to it. Some times this would be a person who wants to remain anonymous until some time after their death.
  • Users often have a donor when there was no order involved in the first place. (Possibly need a feature for inventory (Instance, holding, item), MARC Holdings, ERM (Online resources) that allows for referencing a donor even when no order is in-place)
  • One donor may have different bookplates or "Text for public display". Donor has many children and donates things on each of their behalf. Some donate personally and from their business
  • In some cases there aren't really donors, but electronic bookplates are still needed. For example, Duke has a program that places bookplates for alumni who have passed away - https://blogs.library.duke.edu/magazine/2018/01/29/r-p-rest-perkins-wont-live-read-perfect-book/
  • Associate funds with specific donors (e.g. endowments)

Requirements:

Identify an Organization as a Donor and assign multiple points of contact to that donor.

Identify Orders/POLs and Funds associated with a given Donor.

Associate one or more Donors with a given Order/POL and/or a given Fund.

Associate Donors automatically with Orders/POLs that draw from a given Fund when Donors are associated with that Fund 

Pass Inventory the Donor Name/ID that allows them to associate the information Below. (Holding or Item)

The information needed for the bookplate:

  • Code (This represents the donor and it's details defined below)
  • Descriptive name
  • Text for display
  • URL to connect to electronic bookplate for online donor recognition

This could be a stand-alone app if needed to manage all aspects of donors. (TBD)

Proposed approach:
Donor can be assigned to order (Multi select)
Donor could be assigned to Fund (Multi select) if use on an order the donor filed should be populated with associated donor codes
Codes would be transferred to inventory record (Holding or Item)

https://miro.com/app/board/uXjVMpwk_bk=/?share_link_id=998364656167



 Comments   
Comment by Tom Wilson [ 04/Dec/19 ]

There already is a field in the POL for indicating donor. So, for us, it becomes a question of how that information is mapped to the item record, and if that information can be displayed in the discovery layer.

Comment by Felix Hemme [ 04/Feb/20 ]

Electronic bookplate in the item record (type-value field): Unable to render embedded object: File (screenshot-1.png) not found.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: We have legal obligations around on-line donor recognition.Perhaps there's a creative way to track a code in FOLIO and link it to a display string through an external lookup. That seems cumbersome on the face of it, but perhaps possible. -Tod Olson

Comment by Erin Nettifee [ 15/May/23 ]

Does this also include use cases where there aren't really donors, but electronic bookplates are still needed? For example, Duke has a program that places bookplates for alumni who have passed away - https://blogs.library.duke.edu/magazine/2018/01/29/r-p-rest-perkins-wont-live-read-perfect-book/

Comment by Erin Nettifee [ 15/May/23 ]

Also, if this is prioritized as a P4, why is it scheduled for Sunflower? Should it be reprioritized higher? Typically P4s aren't scheduled, right?

Comment by Dennis Bridges [ 15/May/23 ]

Thank you for the additional use case Erin Nettifee, we are still refining this issue but it is important to LC so for now it has been given a fixed version of Sunflower.

Generated at Fri Feb 09 00:12:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.