Entity Management (UXPROD-787)

[UXPROD-2526] Entity Management App. Move inventory reference data to entity management app Created: 17/Jun/20  Updated: 09/Jan/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Entity Management

Type: New Feature Priority: P3
Reporter: Jason Kovari Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Entity Management
Development Team: None
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R1

 Description   

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:

  1. Instance-type uses RDA content types - terms should not be hard coded in FOLIO using FOLIO identifiers, but LOD identifiers.
  2. Instance Format use RDA terms for media and carrier type. - terms should not be hard coded in FOLIO using FOLIO identifiers, but LOD identifiers.


 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 09/Jan/23 ]

Hi Charlotte Whitt 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!

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