# ebscohost
Assign titles in the official short names list (opens new window)
# Enriched fields
| Name | Type | Description |
|---|---|---|
| db_title | String | Title of database. |
# Prerequisites
Your EC needs a print_identifier for enrichment.
You must use ebscohost after filter, parser, deduplicator middleware.
# Headers
- ebscohost-enrich : Set to
falseto disable ebscohost enrichment. Enabled by default. - ebscohost-ttl : Lifetime of cached documents, in seconds. Defaults to
7 days (3600 * 24 * 7). - ebscohost-throttle : Minimum time to wait between queries, in milliseconds. Defaults to
200ms.
# How to use
# ezPAARSE admin page
On the /admin/middlewares page, you can choose to move the middleware from “Available Middleware” to “Active Middleware for Processing.”
# ezPAARSE process page
On the /process page, under the “2 Settings” tab, in the ‘Settings’ menu, you can choose to move the middleware from “Available Middleware” to “Active Middleware for Processing.”
# ezp
You can use ebscohost for an enrichment process with ezp (opens new window) like this:
# enrich with one file
ezp process <path of your file> \
--host <host of your ezPAARSE instance> \
--settings <settings-id> \
--header "ezPAARSE-Middlewares: ebscohost" \
--out ./result.csv
# enrich with multiples files
ezp bulk <path of your directory> \
--host <host of your ezPAARSE instance> \
--settings <settings-id> \
--header "ezPAARSE-Middlewares: ebscohost"
# curl
You can use ebscohost for an enrichment process with curl like this:
curl -X POST -v http://localhost:59599 \
-H "ezPAARSE-Middlewares: ebscohost" \
-H "Log-Format-Ezproxy: <line format>" \
-F "file=@<log file path>"
← deduplicator enhancer →