Access into Network Zone environment

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Recommendation

Background

Alma (including network zone) requires a 3rd party authentication to login to the system. In order to login to the Alma network zone, the site (campus or CDL) 's authentication will need to integrate with the NZ. All sites that should have access into the NZ environment will need to have their authentication integrated with the NZ.

Dependencies

UCOP (CDL) and UCSD (SCP) staff manage UC-wide services; both sites need authentication within the NZ. (may depend on SCP, SFX, and related resource records handling for eResource records in NZ )

Single UC-wide patron record database or separate institutional patron databases? (PDCG) : if there is a shared patron database in NZ, this may require more sites (besides CDL & UCSD) to have access to the NZ

(technical unknown): how many authentication integrations can NZ have? (posed to ExL May 8 )

(technical unknown): any conflicts arising from same authentication integrated at both IZ & NZ (for non-UCOP sites)

Answer needed for “3rd party integrations” due to ExL May 29th.

Questions to consider

Who (aside from those staff directly managing UC-wide services), if any, should have direct access to network zone instance?

ExL’s list of tasks requiring access to NZ environment

Consider if any required tasks could be accomplished in IZ (not requiring direct access to NZ, eg. updating shared NZ bibliographic records can be done in IZ)

Action Log