Install, configure, and load the resolver database for JScholarship Identifier Resolver Proxy.
The Identifier Resolving Proxy Server (IDproxy) acts as a proxy for content in JScholarship, the institutional repository of the Sheridan Libraries at Johns Hopkins University, and redirects to content that has been migrated from JScholarship into other service applications (e.g., the Lester S. Levy Sheetmusic Collection). The resolver also handles Shibboleth authentication, which makes it easier to make changes to the proxied DSpace instance and allows us to avoid directly connecting the DSpace server to the Internet.
- $ ansible-playbook [--vault-password-file <vault-password-file>] [-K] -i <dataverse-host-name>, [-u <ssh-username>] idproxy.pb
- e.g.: $ ansible-playbook --vault-password-file ~/.ansible/.vault-pw -K -i idproxy05.my.org, idproxy.pb
- The comma after the hostname is needed if only one host is listed, which is probably the typical case.
- This role currently requires CentOS 7 and deploys all services on the same machine.
- Some content in this Ansible role is encrypted as Ansible Vaults.
After completing this installation, you should have a working ID Proxy installation.
- The idproxy-load phase expects one or more files in the /files/resolver folder.
- To be included in the resolution database, the filenames must end with mappings.txt (e.g., levy-id-mappings.txt).
- The record structure for these files should be:
- <Handle> <collection>:<collection-specific-id>
- e.g., For the item with URI http://jhir.library.jhu.edu/handle/1774.2/28748, the entry would be:
- hdl:1774.2/28748 levy:140.009
- As new collections are migrated out of JScholarship, new mapping files can be added to this directory.
- Add a new rewrite rule to /templates/httpd/jhir.vhost.conf.j2 and /templates/httpd/ssl.conf.j2. This line can be added after the existing resolver rewrite lines in each of these files. For example, the mod_rewrite rule for the Levy collection is:
- RewriteRule ^/resolved/levy:(.*)$ http://levysheetmusic.mse.jhu.edu/catalog/levy:$1 [R,L]
- Add a mappings file to the /files/resolver folder.
- TODO: Create a playbook to run just the idproxy-load phase to update the mappings database.
- Shibboleth Service Provider
- Configuration location: /etc/shibboleth
- Apache httpd
- Configuration location: /usr/local/solr/example/solr/collection1/conf/schema.xml