Entity Management App. Move inventory reference data to entity management app
Description
Priority
P3Labels
Fix versions
None
Development Team
None
Assignee
Solution Architect
None
None
Parent Field Value
None
Parent Status
None
Checklist
hideTestRail: Results
Activity
Show:
Ann-Marie Breaux January 9, 2023 at 5:25 PM
Hi Just catching up on some EM conversation in Slack. When/if this Jira is worked on, please make sure to include informing the many non-Inventory apps that rely on Inventory Reference data, like Orders, Data Import, Data Export, etc. Thank you!
Reporter
Jason KovariRank: 5Colleges (Full Jul 2021)
R4
Rank: Cornell (Full Sum 2021)
R3
Rank: GBV (MVP Sum 2020)
R4
Rank: TAMU (MVP Jan 2021)
R3
Rank: Chicago (MVP Sum 2020)
R2
Rank: U of AL (MVP Oct 2020)
R1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 17, 2020 at 3:41 PM
Updated November 18, 2024 at 4:04 PM
TestRail: Cases
TestRail: Runs
Purpose:
When reference data is expected to be provided by external vocabularies as well as local vocabularies, the data should be managed via the entity management app(s) and not with inventory seetings to support real-time or cached access to the vocabulary.
Use cases:
Instance-type uses RDA content types - terms should not be hard coded in FOLIO using FOLIO identifiers, but LOD identifiers.
Instance Format use RDA terms for media and carrier type. - terms should not be hard coded in FOLIO using FOLIO identifiers, but LOD identifiers.