API key config checks out clean. Closing this to pick up ingest requirements per .

let’s not lose track of the need for https://openlibraryfoundation.atlassian.net/browse/DCB-1622?focusedCommentId=475233 to verify details and support ongoing testing during the implementation cycle. Additionally, per-tenant bib record count and clustered record count from existing union catalog are good baselines to corroborate ingest results.

In the first instance for me, it was to verify that we had associated the apikey with the correct institution, when mobius was setup there were a couple of copy and paste errors so the wrong apikey was associated with the wrong institution.

Unfortunatly there is no relationship between the apikey and the url, if there were my copy and paste errors would have been trapped earlier, I was just trying to verify this dosn’t happen for gil, so we do not need to blow away the harvested records and reharvest if we only spot this issue after the harvest has happened.

Will these be needed throughout the project for continued testing, and worth the effort of creating now?

I would say so. may also have a perspective.

Can you give us details on how this information will be used to help verify the connection? The FOLIO team has indicated that this will take hours of their time to create patrons and admins for each tenant, and then find examples of solely owned instances. Will these be needed throughout the project for continued testing, and worth the effort of creating now?

To help in the immediate: Is there another indicator that already exists in the harvested record that would indicate where it’s coming from? --In the LDR field?

• When we are building MOBIUS EDS catalogs, we cross-check identifiers for the code per tenant to know which records belonged to which site (Example, if identifier contains cs00000001_0017, the record is for State Tech College of Missouri). Do DCB records have a similar identifier?

we’ve been able to make a connection but need some additional info for each tenant to verify that we are connecting to the correct tenant in each case. Can you please send through, for each tenant,

• credentials for a patron that is unique to that tenant

• credentials for an admin account to log into each FOLIO

• solely owned instances we can look up (ie, that are unique to each tenant)

Also, can you send the edge APIs for the ingest please.

Thanks

a new set of keys should have been sent on Fri 25 Oct which includes Albany State University, which was originally missing.

I’ve renamed this ticket to reference GIL rather than GALILEO also (the consortium’s preferred / expected designation).

EBSCO confirmed there is an issue with the API keys following tenant creation.

Moving this to On Hold pending delivery of fresh keys