Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work) (UXPROD-1153)

[UXPROD-2665] Export records from search results in acquisitions apps Created: 17/Sep/20  Updated: 04/Apr/23  Resolved: 26/Sep/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work)

Type: New Feature Priority: P4
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acquisitions, needs-ranking, needs-rmsigreview
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-export-dropdown.png    
Issue links:
Defines
is defined by UXPROD-2318 Export orders in bulk via delimited f... Closed
is defined by UXPROD-3435 Export invoice data in delimited file... Closed
is defined by UXPROD-3620 The ability to EXPORT fund detail via... Closed
is defined by UXPROD-3662 Export piece data in delimited file f... Closed
Epic Link: Exporting Orders and Importing Invoices in EDIFACT format (Thunderjet work)
Front End Estimate: Large < 10 days
Back End Estimate: XL < 15 days
Development Team: Thunderjet
Report Functional Area(s):
Import and Export
PO Rank: 71.5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2
Rank: MI State-Lib of MI (Sum 2021): R1
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Note: This feature potentially overlaps with other functionality provided by FOLIO tools like the LDP.

Purpose:

Libraries frequently analyze order information. Allowing users to export order records from their search resutls will allow them to perform ad-hoc analyses and compared data with information from other sources. The report must contain key order data like current encumbered and expended values.

Use cases:

  1. Librarian is being pressured to change budget numbers. Need to review currently open orders (Standing orders), discuss them with colleagues and make decisions about canceling some. This is managed in a list and potentially shared with a vendor as an excel file. See UXPROD-2318 Closed
  2. Librarian is preparing a summary of order information for presentation. To achieve this data is often export so that it can be presented in graphs or other visuals. See UXPROD-2318 Closed
  3. Library environments are not plentiful with digital interfaces like Tablets and projectors. Often times teams will print a list of items so they can quickly be reviewed with a group. Also not all staff have permission to see certain areas of the interface. Exporting records allows the exporter to easily filter out data or data points they do not want to share.
  4. Export receiving information to share with a staffer that will actually go out into the library and look for/gather these items. Primarily they would need to know where to look for them and how to identify them. Also whether they have actually been received or not. See UXPROD-3662

Approach:

Use the UI only approach to accommodate this functionality within capacity restrictions. Performance with this approach is good enough to support requirements.
https://folio-org.atlassian.net/wiki/display/DD/Data+export+by+using+Spring+Batch

Out of scope:

Order export split off to  UXPROD-2318 Closed
This will not include an ability to import orders via csv file. It is not intended to provide the user an ability to bulk edit orders outside the system and re-upload them.

Grooming



 Comments   
Comment by Dennis Bridges [ 17/Sep/20 ]

This has been created for review with RM/Reporting SIG on September 18, 2020

Comment by Ann-Marie Breaux (Inactive) [ 23/Sep/20 ]

Hi Dennis Bridges What epic do you want to put this feature under?

Comment by Dennis Bridges [ 23/Nov/20 ]

Note: I have removed the R1 rank from this feature as it aims to cover all acquisitions apps. It will be split into separate features, one of which is UXPROD-2318 Closed with has been added to R1 in its place. UXPROD-2318 Closed will cover the export of order records to csv following the design pattern and use cases originally defined under this story.

Comment by Khalilah Gambrell [ 11/May/22 ]

Dennis Bridges - is this supported?

Comment by Dennis Bridges [ 11/May/22 ]

Khalilah Gambrell Many of these features have been completed in the last few weeks as we opted to use the same FE approach used in the orders app. The only acq app without an export will be the organizations app. So I believe this can be closed in Morning Glory.

Comment by Dennis Bridges [ 26/Sep/22 ]

I am closing this feature with Morning Glory as all related UXPRODs have now been completed. 

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