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

[UXPROD-4164] Support OCIO Organization integration for Momentum Created: 04/Apr/23  Updated: 05/Feb/24

Status: Analysis Complete
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: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority1, acq-sig-topics, loc, ocio-integration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-4396 AP system integration Draft
defines UXPROD-4312 Acquisitions - Go Live integrations In Refinement
Release: Quesnelia (R1 2024)
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Analysis Estimate: Medium < 5 days
Analysis Estimator: Khalilah Gambrell
Front End Estimator: Khalilah Gambrell
Back End Estimate: Medium < 5 days
Back End Estimator: Dennis Bridges
Back-End Confidence factor: 80%
Development Team: Thunderjet
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem: Some libraries need to output organization information to third party systems for a variety of purposes, such as invoice payment. The assumption in this case is that the library system has the most current information for the organization, and that information needs to be transmitted to other related systems.

Update as of 9/1/2023:

This feature is now an integration feature to help us track OCIO work. Barring technical obstacles, there is no development work associated with this feature.

In scope

Output organization records based on predetermined triggers and/or on a predetermined schedule
Output specified organization records on demand from within FOLIO
Output organization records in response to a third-party API call
Configure organization records for output in a defined format compatible with third-party systems (JSON, csv)
Logging associated with output operations

Out of scope

Output of order or invoice information

Use case(s)

Library maintains its "most correct" vendor database within FOLIO. As vendor information is changed or updated, the library needs to pass these updates to an external system (e.g. Banner, Momentum, DMEP).

Library adds a new vendor. The accounts payable system needs to be updated with the new vendor information.

Library participates in a materials exchange program and tracks partners and providers within FOLIO. This organization information must periodically be sent to the external clearinghouse system that manages the exchange program.

Proposed solution/stories

Output via API call

Library staff-initiated output

Output configuration

Links to additional info

Relates to Acquisitions SIG Topic number 89: https://folio-org.atlassian.net/wiki/x/NwNU

Requirements and user stories: https://folio-org.atlassian.net/wiki/x/IBZU

Questions



 Comments   
Comment by Dennis Bridges [ 11/Apr/23 ]

Discussed with SIG that we should consider this may satisfy the need for a "Simple" export results requirement as well. If not a separate feature should be created for that to address topic #89

Comment by Masami [ 12/Jul/23 ]

On Elena Petroselli's behalf, here is another use case:
The FOLIO ERM customer Universita di Cagliari as well is requesting to have the possibility of exporting Organizations info, in the same way customers currently have the 'Export results' option among the available Actions for some Apps (like Orders, Invoices, Licenses) - while there is none for the Organizations app. 

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