Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-293

Union Catalog support

    XMLWordPrintable

    Details

    • Template:
    • Analysis Estimate:
      XXL < 30 days
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Calculated Total Rank:
      13
    • Kiwi Planning Points (DO NOT CHANGE):
      1
    • 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):
      R5
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R5
    • Rank: hbz (TBD):
      R5
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: TAMU (MVP Jan 2021):
      R5
    • Rank: U of AL (MVP Oct 2020):
      R5

      Description

      Configure a single catalog that allows holdings/items that contain library identifiers that represent all libraries in the collective. The catalog allows libraries and patrons to borrow and transact from each organization and borrowers to determine status in each of the libraries. By default each library can view their own sub-catalog with the option to see holding/item for parts or the entire union.

      One option (planned for v1):

      • Multi-institution tenant. Not a cross-tenant feature.
      • Would want to scope permissions to location - current understanding is that permissions are scoped to processing center, but maybe we can change that...
      • What about other metadata elements that might need to differ based on location (e.g. patron group)
      • Workaround might be to give them different logins could even do a kludgey linking of records by extending the proxy linking capabilities
      • First version, patron group will not be location-specific
      • Need to be able to filter inventory and codex by institution location - but location filter is already planned

      Option two:

      • Cross-tenant functionality

      Per WOLFcon discussion on single-tenant consortia implementation, permission scoping is not required for v1. No other data needs to differ based on location (with the exception of loan policies and patron notices which are both tied to location via loan rules). Some users may have to have >1 user record, but this is okay. Given that, I am marking this feature post-v1. NOTE: It was deemed important, though, that each institution support >1 time zone. I have created a separate feature for this UXPROD-592

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                kdrake Kelly Drake
                Reporter:
                cboerema Cate Boerema
                Analysis Estimator:
                Cate Boerema Cate Boerema
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases