# idp-to-institution
Add information about institution with IDP.
# Enriched fields
| Name | Type | Description |
|---|---|---|
| institutionName | String | Name of institution. |
# Prerequisites
idp-to-institution enrichment middleware needs IDP. You need to find the file Etablissement.csv on Inist Gitlab on Istex repo and put at the folder of this middleware.
You must use idp-to-institution after filter, parser, deduplicator middleware.
# Example
# Headers
+ **idp-to-institution-source-field** : Fields in the ec for enrichment. "login" by default.
+ **idp-to-institution-enriched-field** : Enriched field in the EC. "institution-name" by default.
# 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 idp-to-institution 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: idp-to-institution" \
--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: idp-to-institution"
# curl
You can use idp-to-institution for an enrichment process with curl like this:
curl -X POST -v http://localhost:59599 \
-H "ezPAARSE-Middlewares: idp-to-institution" \
-H "Log-Format-Ezproxy: <line format>" \
-F "file=@<log file path>"