Inventory (UXPROD-785)

[UXPROD-2308]  Save libraryId, campusId, and institutionId in the item record Created: 09/Mar/20  Updated: 16/Sep/21  Resolved: 02/Apr/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Inventory

Type: New Feature Priority: TBD
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skærmbillede 2020-03-30 kl. 17.56.36.png     PNG File Skærmbillede 2020-03-30 kl. 17.56.51.png     PNG File Skærmbillede 2020-03-30 kl. 17.57.12.png    
Issue links:
Relates
relates to UXPROD-771 Locations and Service Points In Progress
Epic Link: Inventory

 Description   

Suggested by Erin Nettifee at Duke.

One feature I'd like to see added is storing libraryId, campusId, and maybe also InstitutionId in the item record, even if it's not displayed in the GUI. That would allow for much easier reporting queries on items via the LDP.

Could also explore whether this feature and could directly support adding Library to the filter menu for items (see UIIN-761 Closed ). But this aspect is out of scope for this feature.



 Comments   
Comment by Cate Boerema (Inactive) [ 09/Mar/20 ]

FYI Charlotte Whitt, I drafted this feature based on a comment from Erin Nettifee in Slack: https://folio-project.slack.com/archives/C20V5L40P/p1583504160073800?thread_ts=1583250570.042600&cid=C20V5L40P

Comment by Charlotte Whitt [ 09/Mar/20 ]

I agree - but I'd like also to hear what the developers think re. how this will impact the performance of Inventory?

CC: lew235 Christie Thomas

Comment by Cate Boerema (Inactive) [ 09/Mar/20 ]

I did run it by Marc Johnson. He didn't have any technical concerns with creating a feature for this. That said, he pointed out that the usual caveats of keeping the data in sync apply to this, like the other copying of data features / issues.

Comment by Charlotte Whitt [ 09/Mar/20 ]

Yes, it's definitely a problem copying data across the apps, and then keep the data in sync. Somehow we should solve to be able to search across apps, instead of copying data from one app to another app, in order to be able to search on this.

Nassib Nassar lew235 - the purpose of this feature is:

One feature I'd like to see added is storing libraryId, campusId, and maybe also InstitutionId in the item record, even if it's not displayed in the GUI. That would allow for much easier reporting queries on items via the LDP.

Is this thinking aligned with your understanding of the LDP? Only asking to be sure, we do not implement something which affect the performance of Inventory, to solve join of tables in LDP.

Comment by Erin Nettifee [ 09/Mar/20 ]

It could perhaps start with just copying the LibraryId if there are performance concerns, I suppose. And InstitutionId may not really be needed. Because LibraryId is in the Location record, I don't think it will be difficult to do. But, if you take a library that has, say, 20 locations in a building, this would make it a lot easier to run a report rather than having to provide a SQL query that walks each of those locations.

At Duke, we are considering mapping our existing libraries to the campus level in FOLIO, to allow for two levels of coordination below Library. This is something that would alleviate a lot of reporting pain for us.

Comment by Nassib Nassar [ 02/Apr/20 ]

Duplication of libraryId, campusId, or institutionId in item records within FOLIO or LDP would result in database anomalies and should be avoided. In LDP, the joins required to access these attributes can be expressed in a derived table, which can be reused by multiple reporting queries if needed.

Comment by Erin Nettifee [ 02/Apr/20 ]

Cate Boerema I think you can close this feature. I met today briefly with Nassib Nassar and Angela Zoss and the reporting needs can be accommodated in a different way that doesn't generate data inconsistency issues as others have noted.

Comment by Charlotte Whitt [ 02/Apr/20 ]

Hi Erin Nettifee and Nassib Nassar - thanks much for investigating this further. Sounds all good. I can close the feature.

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