[UXPROD-4193] Output organization information in delimited file format Created: 13/Apr/23  Updated: 07/Feb/24

Status: Analysis Complete
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)

Type: New Feature Priority: P3
Reporter: Joseph Reimers Assignee: Kathleen Moore
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority2, SolutionArchitecture, at-risk, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screenshot 2023-08-09 110656.png     PNG File export settings 2.png     PNG File export settings.png    
Issue links:
Defines
defines UXPROD-4312 Acquisitions - Go Live integrations In Refinement
is defined by MODFQMMGR-147 Organizations - add vendor terms fiel... Open
is defined by MODFQMMGR-136 Spike: Investigate 'organizations' en... In Progress
is defined by UXPROD-4171 Print shipping labels Closed
is defined by MODFQMMGR-135 Create organizations record entity Draft
is defined by MODFQMMGR-144 Organizations - add address fields to... Draft
is defined by MODFQMMGR-145 Organizations - add contact info fiel... Draft
is defined by MODFQMMGR-146 Organizations - add vendor info field... Draft
is defined by MODFQMMGR-148 Organizations - add accounts fields t... Draft
is defined by UIORGS-380 Allow user to select data points for ... Draft
is defined by UIORGS-381 Export organizations functionality - ... Draft
is defined by UIORGS-379 Create Actions menu for Organizations In Refinement
Release: Quesnelia (R1 2024)
Front End Estimator: Matt Weaver
Front-End Confidence factor: 80%
Back End Estimate: XL < 15 days
Back End Estimator: Matt Weaver
Back-End Confidence factor: 80%
Estimation Notes and Assumptions: Potentially minimize frontend work
Development Team: Corsair
PO Rank: 0

 Description   

Current situation or problem: LOC manages a Duplicate Materials Exchange Program (DMEP), which involves exchanging materials (print monographs and serials) with other libraries around the world. The current DMEP setup involves extracting data from the ILS into an external system, where the actual management of the exchange program takes place. The library needs to ensure FOLIO has the capability to store and export organizational and bibliographic information to the primary DMEP database.

In scope

  • Create the necessary APIs and/or exports for ingest into the DMEP central system
  • Facilitate printing of labels and other related outputs
  • Manage participant organizational information
  • Support for relevant item/holding statuses and updates
  • Output of DMEP partner records (Organizations) in csv format

Out of scope

  • DMEP storefront functionality
  • Primary management of DMEP activities
  • Management of "exchange points"

Use case(s)

Only current requirement not met is the ability to output organizations to csv files based on user-specified values.

Library needs to identify DMEP partner organizations and output for manual ingest into Microsoft Access.

Proposed solution/stories

Pattern should mirror export of invoices, transactions, etc.

Links to additional info

Miro Board: https://miro.com/app/board/uXjVMeziA4Q=/?share_link_id=168739588037

Questions



 Comments   
Comment by Mikhail Fokanov [ 10/Oct/23 ]

The primary service for exporting of data in specific (e.g, csv) format in Folio is data-export. The primary service for exporting of data in specific (e.g, csv) format in Folio is data-export. We need to consider if we need FQM to retrieve the data for this feature.

Comment by Dennis Bridges [ 23/Oct/23 ]

Kathleen Moore is this still scheduled for Quesnelia development? Is Mikhail suggesting that you have not settled on scope for Q? 

We need to make sure this functionality is accounted for in the Q release. thx!

cc: Joseph Reimers 

Comment by Mikhail Fokanov [ 24/Oct/23 ]

After the discussions, it turned out that we will implement such reporting functionality in FQM, so this dashboard should be also implemented in FQM. I will provide the solution design for this reporting functionality.

Comment by Mikhail Fokanov [ 14/Nov/23 ]

Kathleen Moore, Kathleen Moore If we implement custom reporting UI in scope of the https://folio-org.atlassian.net/browse/UXPROD-4104 , then the export to CSV will be just a button on this UI. In terms of server side implementation it is just streaming (database scroll) to the output http stream.

There is no need to use data-export-spring for it, because data-export-spring is primarily used for mod-inventory-storage data and the functionality of export to CSV from snapshot table can be implemented much more efficiently from the FQM itself without involvement of data-export-spring.

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