Network Zone API Access
Legend: not started IN PROGRESS STALLED decided
Status | In Progress |
|---|---|
Description | Process for requesting a NZ Account API Key |
Decision summary | Access to NZ production APIs, and any sandbox write APIs, requires approval from SILS Operations Team. However, the operations team representative from each campus can approve access to NZ sandbox read-only APIs. |
Owning group | Operations Team (SILS-OT-L@listserv.ucop.edu) |
Approver | Operations Team |
Consulted |
|
Informed |
|
Decision-making process | SILS Ops Center proposal and OT approval |
Priority | Normal |
Target decision date |
|
Date decided |
|
Recommendation
Access to NZ production APIs, and any sandbox write APIs, requires approval from SILS Operations Team. However, the operations team representative from each campus can approve access to NZ sandbox read-only APIs. When access to an NZ sandbox read-only API has been approved, SILS Ops Center will inform OT.
Impact and Reasoning
Operations Team believes there is minimal impact in allowing authorized campus and CDL users access to the sandbox read-only API keys.
However, the impact of using NZ production APIs, as well as using write APIs to change data in the NZ sandbox, should be considered on a case-by-case basis.
Write access to the NZ sandbox could potentially impact existing testing.
NZ production APIs could impact production performance and write access should be use should be evaluated. In the case of NZ production, we want to evaluate whether there could be negative performance impacts with using any APIs as well as unanticipated data changes.
NZ Sandbox Read-Only API Request Process
Campus user reaches out to their SILS Operations Team representative
If the OT rep approves the request, they should email SILS Ops Center the following information
Name of approved campus user
User email address
User job title
What the read-only API access will be used for
Risks & Mitigations
Risk: SILS Operations Center does not know which campus users have a legitimate need for sandbox read-only API access.
Mitigation: Rather than each user directly contacting SILS Operations Center for access, they will go through their campus or CDL representative who will evaluate the request and then, if approving, forward the information to SILS Ops Center.
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
SILS Operations Center | May 1, 2025 | Draft decision page |
|
OT | May 14, 2025 | Vote on decision page |
|
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu