Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2) (UXPROD-4485)

[UXPROD-4270] Vendor data (address, etc.) should be definable at the consortial level for any member library to reference Created: 05/May/23  Updated: 22/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)

Type: New Feature Priority: P4
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-4137 Managing unique identifiers in acquis... Closed
Epic Link: Features that will be implemented to enhance FOLIO's ability to support consortia (Phase 2)
Front End Estimate: XL < 15 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XXL < 30 days
Back End Estimator: Khalilah Gambrell
Back-End Confidence factor: 20%
Development Team: Thunderjet
PO Rank: 0

 Description   

Current situation or problem: The central office of a consortium may want to maintain an "official" list of certain types of records - Organizations in particular - for members to access and use and attach their own member-specific information in appropriate accordions. The main information (e.g. name, code) is only editable centrally. Other information (e.g. contact persons, account info, integrations) should be customizable at the member level.

In scope

  • The consortia can make their organization records visible to one or more agencies An agency can make their organization records visible to one or more agencies including the consortia
  • Preserve global uniqueness of these records to satisfy integrations
  • Allow local modification of designated portions and/or associate related records locally (e.g. associate a contact record with an organization at the member level)

Out of scope

Use case(s)

Organizations generally have data that is unique to them and not unique to their relationship with a specific library. Eg. Names, addresses, URLs, accepted currencies etc.

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Dennis Bridges [ 21/Dec/23 ]

Joseph Reimers I just noticed the LC tag on this but I have removed it as it will not apply in their system (All orgs will be central). Need to figure out what release this should be associated with as it will be important to consortium moving forward.

Comment by Joseph Reimers [ 21/Dec/23 ]

Dennis Bridges I had put the LC tag on this before we had finalized the centralized ordering model (so data tenants have no need for this.) Having said that, this was identified as a desirable feature by MOBIUS, so it's something we want to keep on the relatively near-term roadmap.

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