This This document will illustrate how search will operate in a consortium using a central index for all members of a consortium.
...
Payload retrieved from mod-inventory will be stored in two tables in the central tenant, consortium_instances and consortium_authorities. Both tables will have the following columns
| Column Name | Column Description | Column Datatype |
|---|---|---|
| tenantId | tenant Identifier | varchar |
| instanceid | instance identifier | UUID |
| json | payload | JSON(NOT JSONB) |
| created_date | created date | date |
| updated_date | updated date | date |
| Info |
|---|
The primary key for the table should be tenantId & instanceId. There should also be an index on instanceId. |
...
Name | Values | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Shared |
| ||||||||||||
Held By |
|
Active Affiliation
A new query parameter “active_affiliation“ will be added to signal the active affiliation for a search request. The active affiliation of a search request will be tenant context with which a search request is made. A “Local Record” can be different depending on the active affiliation for the search. For example, If there are three records in mod-search: Consortial Tenant Record, Tenant A Record & Tenant B Record.
...