What is it?
In order to keep the e-resource domains up-to-date, the EZproxy configuration file gets imported every night. Currently there are two possible methods to do this automated configuration:
1: EZproxy status page integration:
The list of proxiable domains is collected through the EZproxy status page. To achieve this, we will need an account that has access to the /status page on the
If you have hosted EZproxy, you can ask the OCLC / EZproxy service desk (https://www.oclc.org/en/contacts/support.html) for these credentials.
Just send them this email:
We are implementing Lean Library and we would like a read only account with access to the /status page of our EZproxy server
Local EZproxy (or self-hosted)
If your library has a local EZproxy, you can ask your EZproxy admin for the credentials.
You can send them this email:
To automate the e-resource configuration in Lean Library, we need a user with access to the /status page of EZproxy. Could you send me those user credentials?
Thanks in advance!
See more information that OCLC provided about this below:
Add this to the user.txt file.
// where lladmin is the user and xxxxx is the password
2: Importing the proxy configuration file through the config.txt
Lean Library can download the config.txt file from URL or FTP server too. When using FTP, there are multiple sub-options: FTP, SFTP with password and SFTP with private key. Once set up properly, the e-resource domain list gets updated every 24 hours.
We strongly recommend using the status page integration because of the "messy" nature of the config.txt file. The status page is more structured and provides better results.
3: Importing rules
As we import the EZproxy configuration file every night, we are asked frequently, how this exactly works. Domains that are disabled manually in the dashboard will always stay disabled after every import, keeping the e-resources up-to-date this way. Additionally, domains that were once imported but that later got deleted from the EZproxy configuration file will also be deleted from the Lean Library dashboard after the next import after the deletion.