Reporting Feature Requests (UXPROD-1910)

[UXPROD-1864] Store custom fields from apps in LDP Created: 06/May/19  Updated: 16/Sep/20  Resolved: 03/Aug/20

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

Type: New Feature Priority: TBD
Reporter: Angela Zoss Assignee: Nassib Nassar
Resolution: Done Votes: 0
Labels: ldp-platform, reporting, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
requires UXPROD-2143 Q1 2020/Q2 2020 | Custom Fields (for ... Closed
Epic Link: Reporting Feature Requests
Back End Estimate: XXL < 30 days
Back End Estimator: Nassib Nassar
Development Team: Reporting
PO Rank: 17
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

FOLIO apps are being designed with custom fields, in part to allow institutions to tailor their experience, but also potentially to correct problems arising from certain features not being available for go-live. At Duke, for example, I believe we will be using custom fields to track additional patron identifiers past the maximum set by the UM app.

These custom fields may well include fields that will be important for the reporting needs of institutions. I have had a request that the LDP be set up to be responsive to custom fields in the various apps. It was suggested that this might logically connect to thinking about how to have the LDP accommodate new apps developed in the future.



 Comments   
Comment by Sharon Beltaine [ 09/Jul/19 ]

REP-221 Closed may be a use case for this feature request. At Cornell, we use stat codes to capture additional patron demographic information. If this functionality is not included in the User Management application, we need to use Custom Fields functionality. For Cornell, this feature can wait - up to a quarter after go-live.

Comment by Erin Nettifee [ 10/Jul/19 ]

REP-104 Open could be a use case, as we may want to store D2D or ILLiad transaction identifiers in the request as a custom field to then report on after, and link to external data.

REP-217 Open is another users-oriented audit report. We may want to use custom fields to capture information about where operators are working and have that available as part of that feed, to use in troubleshooting or volume/traffic reporting for how much work is being done.

REP-154 Open could be a use case, depending on how e-usage information is captured and stored in ERM (an eternal holy grail of those systems.)

REP-30 Closed is a potential use case, depending on how gifts management is approached from the acquisitions side and what information a particular institution needs to keep as part of the gifts process (which is often influenced by development and non-Library university policy.)

Comment by Sharon Beltaine [ 15/Jul/19 ]

Ranking reviewed at Reporting SIG Meeting 7/15/19. We need to review this issue again.

Vandana working on gathering examples of how we would use custom fields in reporting. We need to know if User Management app will incorporate additonal fields into their application.

Comment by Erin Nettifee [ 15/Jul/19 ]

Sharon Beltaine, custom fields was recently assigned a PO, Khalilah Gambrell, so while nothing is currently implemented I think UM is certainly hoping for progress soon.

Or were you talking about additional non-custom fields? There are some UXPRODs in that I don't think have moved since we've been waiting for a PO, but hopefully will soon.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: The custom fields we create in User Management, for example, we will need those in LDP for reporting. (Currently we do the same thing with a custom table in OLE, and it is used frequently in operations.) -Tod Olson

Comment by Erin Nettifee [ 03/Aug/20 ]

Hi Nassib Nassar - do you have a sense as to when / what quarter this might be worked on? I know that your development cycle is separate from the larger project. It would help us at Duke to have an idea, if there is one, of when this might be in place. Thank you!

Comment by Nassib Nassar [ 03/Aug/20 ]

Have custom fields been implemented in Folio?

Comment by Erin Nettifee [ 03/Aug/20 ]

Hi Nassib Nassar - yes, they've been implemented for Users. I don't know what other apps are next in line for them, but it's at least in the Users app right now.

Comment by Nassib Nassar [ 03/Aug/20 ]

If someone could create a custom field in folio-snapshot, we can take a look to see how it is stored.

Comment by Erin Nettifee [ 03/Aug/20 ]

There are two in Snapshot right now - their labels are test1 and test2 - but I don't know if they persist or if someone created them this morning. Khalilah Gambrell is the custom fields PO, she might know.

Comment by Khalilah Gambrell [ 03/Aug/20 ]

Erin Nettifee and Nassib Nassar, someone created the custom fields today.

Comment by Nassib Nassar [ 03/Aug/20 ]

Thanks. They show up in LDP, though for now they have to be extracted using json_extract_path_text(), e.g.:

SELECT id,
       json_extract_path_text(data, 'customFields') AS custom_fields
    FROM user_users;
Comment by Erin Nettifee [ 03/Aug/20 ]

Thanks @Nassib

When custom fields expand to other apps, will there be work needed to bring those custom fields into the LDP, assuming that otherwise the app is already sending data into the LDP? Or will those custom fields show up in the LDP automatically?

Comment by Nassib Nassar [ 03/Aug/20 ]

Assuming that they are stored in a similar way in FOLIO, they should show up in LDP automatically.

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