You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** Why are these changes being introduced:
The search UI needs to be connected with TACOS, in order to get insight
about interventions and allow term categorization to continue.
** Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/use-66
** How does this address that need:
This adds a route, controller, and model for the integration with TACOS,
along with defining some new environment variables. The approach is
similar, but not identical, to the integration present in the Bento app.
** Document any side effects to this change:
One oddity I can't explain is why the "tacos" cassette doesn't have any
record of a call to TACOS - only the call to TIMDEX for the requested
search is present. The related test passes, so everything worked and the
UI element is present - but no interaction is present in the cassette
(and thus made by the application when tested).
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,20 +120,29 @@ mode (e.g., `GDT=false` will still enable GDT features). Note that this is curre
120
120
may have unexpected consequences if applied to other TIMDEX UI apps.
121
121
-`GLOBAL_ALERT`: The main functionality for this comes from our theme gem, but when set the value will be rendered as
122
122
safe html above the main header of the site.
123
+
-`ORIGINS`: sets origins for CORS (currently used only for TACOS API calls).
123
124
-`PLATFORM_NAME`: The value set is added to the header after the MIT Libraries logo. The logic and CSS for this comes from our theme gem.
124
125
-`REQUESTS_PER_PERIOD` - number of requests that can be made for general throttles per `REQUEST_PERIOD`
125
126
-`REQUEST_PERIOD` - time in minutes used along with `REQUESTS_PER_PERIOD`
126
127
-`REDIRECT_REQUESTS_PER_PERIOD`- number of requests that can be made that the query string starts with our legacy redirect parameter to throttle per `REQUEST_PERIOD`
127
128
-`REDIRECT_REQUEST_PERIOD`- time in minutes used along with `REDIRECT_REQUEST_PERIOD`
128
129
-`SENTRY_DSN`: Client key for Sentry exception logging.
129
130
-`SENTRY_ENV`: Sentry environment for the application. Defaults to 'unknown' if unset.
131
+
-`TACOS_SOURCE`: If set, this value is sent to TACOS (as the `sourceSystem` value) to distinguish which application
132
+
instance is sending what search traffic. Defaults to "unset" if not defined.
133
+
-`TACOS_URL`: The GraphQL endpoint for the [TACOS API](https://github.com/mitlibraries/tacos/). When set, the
134
+
application will log search terms to TACOS (and eventually return suggested resources that TACOS detects).
130
135
-`TIMDEX_INDEX`: Name of the index, or alias, to provide to the GraphQL endpoint. Defaults to `nil` which will let TIMDEX determine the best index to use. Wildcard values can be set, for example `rdi*` would search any indexes that begin with `rdi` in the underlying OpenSearch instance behind TIMDEX.
131
136
-`TIMDEX_SOURCES`: Comma-separated list of sources to display in the advanced-search source selection element. This
132
137
overrides the default which is set in ApplicationHelper.
133
138
134
139
#### Test Environment-only Variables
135
140
136
141
-`SPEC_REPORTER`: Optional variable. If set, enables spec reporter style output from tests rather than minimal output.
142
+
-`TACOS_HOST`: Test Env only. Used to ensure the VCR cassettes can properly scrub specific host data to make sure we
143
+
get the same cassettes regardless of which host was used to generate the cassettes. This should be set to the hostname
144
+
that matches `TACOS_URL`. Ex: If `TACOS_URL` is `http://localhost:3001/graphql` then `TACOS_HOST` should be
145
+
`localhost:3001`.
137
146
-`TIMDEX_HOST`: Test Env only. Used to ensure the VCR cassettes can properly scrub specific host data to make sure we get the same cassettes regardless of which host was used to generate the cassettes. This should be set to the host name that matches `TIMDEX_GRAPHQL`. Ex: If `TIMDEX_GRAPHQL` is `https://www.example.com/graphql` then `TIMDEX_HOST` should be `www.example.com`.
0 commit comments