Page Comparison

• Each feature or piece of functionality that team Vega completes should have at least one user acceptance testing (UAT) session

• UAT is needed for functional feature work in single tenant and ECS environments, both standard ECS and ECS + mod-tlr

• UAT should occur as soon as possible to enable the identification of bugs and issues as early as possible

• Both types of environments need:

  • to be snapshot-like, but with persistent data

  • to include all circulation modules (Check in, Check out, Circulation log, Requests, fees and fines, patron notices, loans, etc.), plus Inventory, Users, and Settings

  • to have applicable permissions for the above and specific to the features being tested

  • to be accessible to community testers and members

  • an appropriate data set and configuration for the feature/case being tested

    • for example, multiple (25-30) instance, holding and item records with valid barcodes

    • multiple patron records

• Circulation setting should be set for each environment before UAT begins. Testers should not have to spend time setting up policies, notices, et.

Ramsons features UAT - Workflows/tasks to test

...

• Permissions & affiliations

• Requests (standard, not private)

  • Create request in borrowing tenant

  • Edit request in borrowing tenant

  • Cancel request in borrowing tenant

  • Reorder queue on Primary circulation request

  Duplicate request in borrowing tenant

  • TLR enablement

    • Central/data

    • Consortium

  • Appropriate patron notices sent for Requests

• Loans

  • Check item out from Central tenant

  • Check item in to Central tenant

    • Ensure item is routed back to home location in data tenant

  • Appropriate patron notices sent for Loans

  • Find above transactions in the Circ log & verify info in each column

• TLR enablement

  • Central/data

  • Consortium

• • Look at Loan details

  • Look at User details

• Staff slips

  • Print pick slips

  • Print hold search slips - item

  • Print hold search slips - title
    

 UXPROD-4657 Mediated requests

• Permissions

• Create a new m-request

• Edit a m-request

• Approve folio created m-request

• Decline folio created m-request

• Decline locate created request

• Edit locate created request

• Duplicate folio created m-request

• Duplicate locate created m- request

• Use search to find m-request

• Use filters to find m-request

• Confirm item arrival

• Send item in transit

...

• Permissions, including access to secure tenant

• Place secure request in Congressional tenant and ensure patron data is anonymous in the Central tenant and other related data tenants

• Place a secure request for an oLOAN item and ensure request is visible only in the secure tenant

• Reorder a request queue in the Congressional tenant and ensure the queue in the Central tenant aligns with your changes and the same in the Central tenant to Congressional tenant

• Cancel a request in the Central tenant and ensure the private mediated request has changed to the appropriate status (Closed - Cancelled?) and the same for the Congressional tenant request (Closed - Cancelled) - Note: Can only cancel Primary circulation requests. Need clarification on where the Primary request is placed for secure tenant requests that are not for oLOAN materials. If a m-request is confirmed as a circulation request, is the Primary request in the Secure tenant, or is it in the Central tenant?

• Edit a Primary private request in both tenants and to ensure the changes are reflected in the other both [the secure tenant and Central] tenant

• Check a private request out and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant

  • Is this… - Check out an item to a private patron requester and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant (Should we say - other related tenants?).

• Check that the patron information in Item details, Loan details are obfuscated (Action ellipses)

• Check a private request in and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant

  • Is this…- Check an item in from a Congressional patron (e.g., private patron) and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant.

  • OR - Check in an item that has a request on it for a Congressional patron and ensure the private patron information is visible in the secure tenant and obfuscated in the Central tenant.

...