Consortia (Cross Tenant) (UXPROD-794)

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

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Consortia (Cross Tenant)

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Consortia (Cross Tenant)
Development Team: None
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R5
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: Leipzig (ERM Aut 2019): R4
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R4

 Description   

Description:
Vendor data (address, etc.) should be definable at the consortial level for any member library to reference

Notes:



 Comments   
Comment by Kelly Drake [ 12/Jun/19 ]

Does this reference a central address pool? or the ability of tenants to see/copy other library's vendor addresses.

Comment by Kelly Drake [ 12/Jun/19 ]

Perhaps check with RM SIG to determine if there is a related feature?

Comment by Tim Auger [ 08/May/23 ]

If I understand this correctly, this means that a given vendor record could be used by multiple libraries. Sensible. May need to retrofit existing software?

Dennis Bridges  fyi

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