Affiliation and Permissions Handling in Data Export

Work in Progress

Affiliations

If an instance record has holdings in the tenants that the user is not affiliated with, then

  • Shared instance is exported but holdings and items records are omitted and the log contains following error: <Instance-record-id> - the user <username> is not affiliated with <tenant _id1, tenant _id2, etc> data tenant(s) and holdings and item records from this tenant were omitted during export.

  • Local instance is omitted.

  • The error is entered once for instance and not for each holdings or item record

If a holdings record is exported with the Default export profile and the holdings record is associated with the tenant that the user is not affiliated with, then

  • Holdings record is omitted and the log contains following error: <holdings-record-id> - the user <username> is not affiliated with <tenant _id> data tenant and holdings records from this tenant were omitted during export.

The same behavior is for export of holdings records with custom mapping profiles that might include item records.

 

Permissions

If an instance record has holdings in the tenants that the user is affiliated with but does not have view permission to view holdings/items records then

  • Instance record is exported but holdings and items records are omitted and the log contains following error: <Instance-record-id> - the user <username> does not have permissions to view holdings or items in <tenant _id1, tenant _id2, etc> data tenant(s). Holdings and item records from this tenant were omitted during export.

  • The error is entered once for instance and not for each holdings or item record.

If a holdings record is exported with the Default export profile and the holdings record is associated with the tenant that the user is affiliated with but does not have view permission to view holdings records then

  • Holdings record is omitted and the log contains following error: <holdings record uuid> - the user <username> does not have permissions to access the holdings record in <tenant _id> data tenant.