Reporting Feature Requests (UXPROD-1910)

[UXPROD-1862] Use results of a Reporting query to select items for batch edit in the FOLIO modules Created: 10/Jul/19  Updated: 09/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting Feature Requests

Type: New Feature Priority: TBD
Reporter: Sharon Beltaine Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: featurerequest, reporting, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Reporting Feature Requests
Back End Estimate: XXL < 30 days
Development Team: Reporting
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 15
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R3
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Use results of an LDP query to select items for batch edit in the FOLIO modules. See Angela Zoss for more details on this issue.



 Comments   
Comment by Anya [ 19/Jul/19 ]

FC: would this allow us to search the LDP, and find all the springer URLs and then be able to batch edit? if yes then go live as ranked above. If not please explain.

Comment by Sharon Beltaine [ 22/Jul/19 ]

7/22 Reporting SIG meeting - need to understand 5 Colleges go live ranking.

Identify items in one database to work with items in another database is an error-prone process.

There is no way to query across different data domains in FOLIO applications.

Offer results of LDP query to a FOLIO module.

Sharon to ask Angela and 5 Colleges about this issue.

Comment by Kristin Martin [ 14/Aug/19 ]

From Chicago: Can wait up to one year as long as we have the ability to select records by sets of identifiers (folio hrid, etc.)

Comment by Theodor Tolstoy (One-Group.se) [ 15/Aug/19 ]

Is this the way batch edit is intended to function or is this another way to acheive the same thing given that the LDP work is completed?

Comment by Nassib Nassar [ 15/Aug/19 ]

It seems this is adjunct to batch edit in that it would allow ad hoc or cross-domain queries to be used in identifying items that will be batch edited, subject to the limitation that LDP data are synchronized with the operational data in modules only once per day.

I think this feature more or less suggests having some way that a batch editing function within a FOLIO module can access LDP query results that identify a set of records to be edited (probably a column of IDs in a table).

Comment by Tom Wilson [ 21/Aug/19 ]

We need to be able to identify, export, and bulk edit bibs, holdings, and items. Perhaps this can be accomplished via other means, but those other means must exist in MVP and/or the tools to search, export, and import records.

Comment by Angela Zoss [ 12/Sep/19 ]

From Duke: In general, we need a way for batch edits can be done. Ideally, that would be in an app, and not a report. If the bulk export/import is a workaround, that would be better than a report, IMHO.

Comment by Nassib Nassar [ 02/Jun/20 ]

It appears to me this feature may require further definition.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: If we can get a text file of UUIDs out of the LDP and use that to initiate batch processes such as export and eventually batch edits, that would let us function. -Tod Olson

Comment by Charlotte Whitt [ 07/Nov/23 ]

Hi Nassib Nassar - wouldn't you say that this feature has been accomplished by now? And we can close this feature as done.
CC: Sharon Beltaine Corrie Hutchinson

Comment by Nassib Nassar [ 07/Nov/23 ]

This should be converted to a feature request for the Reporting App.

Comment by Charlotte Whitt [ 08/Nov/23 ]

Nassib Nassar - I updated the Story line (title). If you want to edit in the jira, then please go ahead

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