FOLIO now enables FOLIO-only multi-tenant environments to Declare items lost, Claim items as returned, and Mark items missing and the synchronize statuses across the Loans and Items. This UAT ensures Staff can verify functionality for the following development:

• Claimed returned functionality (UXPROD-5261)

• Declared lost functionality (UXPROD-5262)

• Mark missing functionality (UXPROD-5468)

Testing will take place January 13-20, 2026. Please submit any feedback by the end of the day on Tuesday, January 20, 2026.

Test environment: https://folio-edev-vega-2nd-consortium.ci.folio.org/

Feedback form: Declared lost, Claimed returned, and Marked missing functionality

Test credentials: (username/password)

• m1/Test1313#

• m2/Test1313#

• m3/Test1313#

• m4/Test1313#

• m5/Test1313#

Test affiliations: Central, College and Secure (Instructions on checking & changing affiliation)

Test Patrons - Complete

How to test an Inactive patron UAT (cenin00000000002) - Shared instance in Central; One holding in College (LB 2395 .E65 2010)

• 94558246

• 1238579634

• 4563257

• 554435812

• 7851386

• 875946528714

How to test an Inactive patron 2 (cenin00000000003) - Shared instance in Central; One holding in College (LB 2395 .E67 2010)

• 123578

• 12359468792

• 2597642419

• 5798546

• 5592345

• 456852

How to test an Inactive patron 3 (cenin00000000005) - Shared instance in Central; One holding in secure University (LB 2395 .E69 2010)

• 8523699755

• 12358975

• 987987556

• 12359468793

• 2597642418

• 5798545

How to test an Inactive patron 4 (cenin00000000004) - Shared instance in Central; No holdings

Declared lost functionality

• See Comments in UIU-3435

Claimed returned functionality

• See Comments in UIU-3413

Marked missing functionality

• See Comments in UIU-3444

• The Instructions to test functionality below require the creation of cross-tenant Requests and open loans

• For authorized staff members working with the Secure tenant, use the Secure tenant where the Central tenant is mentioned in Instructions

• For authorized staff members working with the Secure tenant, rely on the requests creation process that begins with creating and confirming a Mediated request

• When in doubt, please review screencasts in associated features or reach out to Anne E. Ekblad (aekblad@ebsco.com - or via Teams or Slack)

• This test requires testers to create open loans via requesting process.

• Actions to Declare Items lost, Mark missing, and Claim returned can be taken

• Loan and Item statuses sync correctly depending on actions taken.

• Resolution workflows (check-in, lost, missing) function as expected.

1. Log in to XYZ environment

2. Navigate to the Users app in the Central tenant

3. Find a User with an Open loan (e.g., an Item that is Checked out)

4. Click on the Loans accordion and select an open loan

5. Click on the “Action” ellipsis to the right in the row with the open Loan and Declare the Item lost OR Click on Declare lost button at on the upper left of the Loan details page

6. Enter Additional information into the “Confirm item status: Declared lost” pop-up

   1. Verify in the Central tenant loan details that the Item is Lost and paid and the Loan is closed

   2. Verify in the Data tenant loan details that the Item is Lost and paid and the Loan is closed and ensure the ensure the Declared lost Button is Inactive

7. Navigate to the Requests app in the Central tenant

8. Attempt to create an ILR Request for the Item that has been Declared lost

   1. Ensure that the Request is not placed in the Central or the Data tenant where the Item lives

1. Log in to Central tenant.

2. Open Users app → search for patron with active loan.

3. Expand Loans accordion → select loan.

4. Click Claim returned → add claim info → Confirm. Validate sync between Loan status and Item status when a loan is marked Claimed returned.

   1. Loan status = Claimed returned.

   2. Item status = Claimed returned (synced across Central and Data tenants)

5. Ensure restrictions on Claimed returned items are enforced:

   1. Cannot be checked out

   2. Cannot be recalled, placed on hold, or paged

6. Perform check-in of Claimed returned item in the Central and Data tenants.

   1. Loan closed.

   2. Item status updated to Available (or appropriate status).

1. Navigate to the patron’s open loans list and select a loan with status Claim returned.

   1. Loan details window opens, and the Resolve claim button is visible.

2. Click Resolve claim, then select Mark as missing.

   1. Confirmation pop-up appears.

   2. User is prompted to enter required additional information.

   3. On clicking Confirm, the loan remains in the patron’s open loans list.

   4. Loan status updates correctly to reflect resolution.

   5. Item status changes to Missing.

3. After confirming Mark Missing, check both loan and item records.

   1. Loan record reflects resolution without fines

   2. Item record status is updated to Missing

   3. Synchronization between loan and item records is consistent.

4. Ensure restrictions on Missing Items are enforced:

   1. Can be checked out

   2. Can place on hold, cannot be recalled or paged

5. Perform check-in of Missing Item in the Central and Data tenants.

   1. Loan closed.

   2. Item status updated to Available (or appropriate status).

Related work to be covered in T:

https://folio-org.atlassian.net/browse/MCBFF-158
https://folio-org.atlassian.net/browse/MODREQMED-185