[MAINTENANCE] Update ror-reconciler to use schema v2

[adambuttrick]

Service/repository
ror-community/ror-reconciler

Describe the current state/issue
The ror-reconciler interacts with the ROR API, which is currently configured to serve v1 as the default response version for any requests that do not specify a version in the URL path. As part of the planned sunset of the v1 API at the end of 2025, the default response version will be switched to v2 of the ROR schema in July of 2025, as described in #314.

When the default API version switches to v2, the reconciler will fail because the reconciler is not set up to parse the v2 response structure.

Describe the desired state/solution
ror-reconciler should be updated to be compatible with the v2 schema:

1. Update logic in (app.rb):

   • Introduce new helper methods to correctly extract data from the v2 JSON schema.
     • A get_display_name(record) helper to parse the names array and retrieve the name value where the type is ror_display or label.
     • A get_country_name(record) helper to parse the locations array and retrieve the country_name from the geonames_details.
   • Update the /reconcile, /suggest, /preview, and /flyout routes to use these new helper methods.

2. Update the view templates (views/):

   • Modify preview.erb and flyout.erb to correctly access name and location information from the v2-compatible data structure passed by the updated app.rb.

3. Update test suite (spec/):

   • Since the API response will change, the existing VCR cassettes must be deleted and re-recorded to capture interactions with the v2 schema.
   • New tests should be added to spec/reconciliation_spec.rb to specifically verify that reconciliation, suggestions, and previews work correctly with the v2 data structure.

[adambuttrick]

Relative to dev availability, we should consider whether to do a minor change to specify v1 in the URL path until the full scope of work can be completed.

[jrhoads]

Just as @adambuttrick mentioned, I think it would be a good idea to split this into two phases

1. Specify V2 in the URL path (to reduce temporal pressure)
2. Update the reconciler to use V2

[jrhoads]

Looks like providing an environmental variable for ROR_API that points to https://api.ror.org/v1 should be sufficient for phase 1 above. Internal app apis are built on that.

[jrhoads]

All Environments were updated yesterday.
This completes phase 1.

[adambuttrick]

Updated to v2 and new Ruby version in ror-community/ror-reconciler#44, ror-community/ror-reconciler#45, ror-community/ror-reconciler#46, ror-community/ror-reconciler#47, but failed to resolve deployment issues.

[adambuttrick]

https://ror.org/02q7mkh03 and https://ror.org/00v8p7w89 awaiting fixes.

[jrhoads]

As mentioned in slack, I was able to solve the deployment issues.
Adam is now testing the production deploy.

[adambuttrick]

All productions test passed and reported fixes to users. Treating migration as now complete.