Switch patron lookup tool to use rosetta API

[spelkey-ucd]

Background

Campus is retiring the old IAM API in favor of a new one, Rosetta. We're migrating this application over. As part of that, a new search component (rosetta-person-search) and a new RosettaModel now exist on the rosetta branch, meant to replace the old PersonModel-based lookups across the app.

Task

ucdlib-iam-page-patron-lookup.js currently has its own duplicated search form and results UI, built directly against PersonModel, rather than using the shared ucdlib-iam-search component. Update this page to use rosetta-person-search and RosettaModel instead.

Once that's in place, clean up anything in the page that's no longer needed as a result - e.g. properties, methods, docstrings, template functions. It should be a fair amount, so please be thorough.

Secrets

You can find the credentials for the API in Google Cloud. You will need to set the ROSETTA_API_CLIENT_ID and ROSETTA_API_CLIENT_SECRET env variables.

Branch

Work off rosetta (origin/rosetta) — that's where the new component and model live. They aren't on main yet.

Acceptance criteria

• Patron search (all existing search methods) works end-to-end through the new component
• Selecting a person still navigates to their detail view correctly
• Direct navigation to a patron's detail page (by URL) still works
• No remaining references to PersonModel in this file
• Manually tested in the browser using a variety of people.

[sbagg]

My understanding

The new Rosetta API is being added to the current IAM system, and the patron lookup tool is to use this instead of the previous PersonModel and corresponding API endpoint. That means using the new Rosetta search element as well as the information it gives as its new information source. This affects the librarians that use the patron lookup tool and its LDAP, Alma, and external employee features. This change is needed to stay up to date on current API practices for the library.

Proposed approach

I propose changing the search element to the Rosetta one, then calling the model to use the new data in the lookup tool. I also may have to add references to different data not currently in the endpoint if it does not match up to what is currently needed for the tool. This may require modifying the patron lookup pages, the model call, or the RosettaPerson file, depending on what applies.

Possible impacts and edge cases

Some previously existing entries may not exist in this endpoint, which means I need to either request that they be added or determine which is no longer needed. So far this includes:

Department Information:

• Department End Date:
• Admin Title
• Appointment

Student Information:

• Start Date
• Modified Date

Other Information

• isStudent
• isExternal
• isStaff
• IsFaculty
  I as well need to know if certain people just don’t have this information listed and create edge cases for this, such as “Not Listed” or just not appearing.

Verification plan

I will test by checking multiple people in different positions to see if the table does not break or if there are blank spaces. I also have to make sure that LDAP and ALMA are still in use as expected. Each click should navigate to the correct page, and individuals’ URLs should still work. Any errors in fetching or otherwise should return the proper error message while not breaking the page, and no previous reference to the existing endpoint should exist

[spelkey-ucd]

FYI here is documentation on the new endpoints:

• https://kb.ucdavis.edu/?id=13040
• https://anypoint.mulesoft.com/exchange/portals/university-of-california-346/9b04bfa8-6eeb-4d85-b676-91db930f8411/iam-rosetta-api/minor/1.0/console/method/%231869/

Some of the properties you mention above as potentially missing exist but under a different name.