Notes | Single Tenant + Multiple Libraries | Assigned notes must be tied to a library/institution

Description

Sara, an E-Resources and Discovery Services Librarian at Mt. Holyoke, whose school is a part of the Five College consortium
Wants to make sure a note assigned to a resource in the Mt. Holyoke eholdings app is only assigned to that resource in the Mt. Holyoke eholdings app AND not assigned to the same resource across all libraries a part of Five College.

Requirement

  • This requirement applies to a single tenant that

    • has multiple libraries

    • with multiple EBSCO KBs/eholdings

    • AND/OR do not share patrons OR funds

  • With eholdings app notes and tags are assigned to the resource. With a single tenant, when we switch EBSCO KB API credentials, notes and tags remain attached. Notes and tags cannot persist and must account for a single tenant with multiple libraries with different EBSCO KB API credentials.

  • Notes and Tags must be tied to the resource AND a unique library ID.

Acceptance Criteria

Given I am a Mt. Holyoke Librarian

AND I have accessed Mt. Holyoke's eholdings
When I create a note on the Academic Search Complete package
Then that note should only be tied to the Academic Search Complete in Mt. Holyoke's eholdings

Given I am a Mt. Holyoke Librarian
AND I have accessed Mt. Holyoke's eholdings
When I unassign a note on the Academic Search Complete package
Then that note should only be unassigned from the Academic Search Complete in Mt. Holyoke's eholdings

Given I am a UMASS librarian
AND I am viewing the UMASS eholdings
When I view the Academic Search Complete package
Then I should not see the note assigned to Academic Search Complete in Mt. Holyoke's eholdings
Only notes assigned to this resource in the UMASS eholdings

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
Won't Do

Details

Assignee

Reporter

Priority

Story Points

Development Team

Spitfire

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 6, 2019 at 10:12 PM
Updated October 11, 2023 at 1:33 AM
Resolved October 11, 2023 at 1:33 AM
TestRail: Cases
TestRail: Runs