Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

*reporting team user accounts: z_slm5, z_jl41, z_lm15, z_np55, z_vp25, z_ama8, z_jmp8

...

Schema NameSchema DescriptionPermissions
local_automationThis schema is for internal use by the Automation Team.

r/w z_metadbuser_cornell user account

local_coreThis schema is for internal use by the Reporting Team.

r/w z_metadbuser_cornell user account

local_derived



This schema is for internal use by the Reporting Team. These tables are created by a script that runs nightly on the Metadb server. The script runs queries in the local_derived directory on cul-folio-analytics. 

r/o z_metadbuser_cornell user account

r/w reporting team user accounts

local_digpresThis schema is used by the HathiTrust team.

r/w z_metadbuser_cornell user account

local_eusageThis schema is used for EBSCO consolidation report data.

r/o z_metadbuser_cornell user account

r/w z_slm5, z_vp25

local_hathitrustThis schema is used internally by the HathiTrust team.

r/w z_metadbuser_cornell user account

local_openThis schema is a sandbox for all users who want to publish a file to a local schema.

r/w z_metadbuser_cornell user account

local_protectedThis schema is used to store tables with protected data that is used internally by the Reporting Team.

r/o reporting team user accounts

r/w z_slm5, z_jl41

local_static



This schema is used to store local tables that are in queries used by all reporting users. All users can read the files here, but only reporting team members can post files here.

r/o z_metadbuser_cornell user account

r/w reporting team user accounts 

local_statisticsThis schema is for internal use by the Assessment and Planning team. 

r/o z_metadbuser_cornell user account

r/w z_lm15slm5, z_slm5, z_vp25 _vp25 


Reporting Team Members and the Local Static Schema

Reporting Team members create files in the local_static schema that are used by report queries to show additional information in the query results, such as Cornell-specific bibliographic format, library location names, etc. To create these files, reporting team members use their z_netid user accounts because these accounts have "read-write" permissions to create files in the local_static schema. General reporting users are connecting to the Metadb reporting database with the z_metadbuser_cornell user account, which has "read-only" permissions to the files in the local_static schema. This means that queries that use the tables that reporting team members publish to the local_static schema, such as "folio_physical_material_formats" and "adc_location_translation_table," will allow z_metadbuser_cornell account users to "read" the data in those tables. There is no need to assign permissions to the z_metadbuser_cornell account to see these tables as they are published because the read-only permission for z_metadbuser_cornell is part of the design of the local_static schema.

How to Set Permissions on files used in Local Schemas

...

ALTER DEFAULT PRIVILEGES for user z_slm5 IN SCHEMA local_statistics GRANT SELECT ON TABLES TO z_lm15, z_vp25;
ALTER DEFAULT PRIVILEGES for user z_slm5 IN SCHEMA local_statistics GRANT SELECT, INSERT, UPDATE, DELETE ON TABLES TO z_lm15, z_vp25;
ALTER DEFAULT PRIVILEGES for user z_slm5 IN SCHEMA local_statistics GRANT USAGE ON SEQUENCES TO z_lm15, z_vp25;
ALTER DEFAULT PRIVILEGES for user z_slm5 IN SCHEMA local_statistics GRANT SELECT ON TABLES TO z_metadbuser_cornell;

Reporting Team Members and the Local Static Schema

Reporting Team members create files in the local_static schema that are used by report queries to show additional information in the query results, such as Cornell-specific bibliographic format, library location names, etc. To create these files, reporting team members use their z_netid user accounts because these accounts have "read-write" permissions to create files in the local_static schema. General reporting users are connecting to the Metadb reporting database with the z_metadbuser_cornell user account, which has "read-only" permissions to the files in the local_static schema. This means that queries that use the tables that reporting team members publish to the local_static schema, such as "folio_physical_material_formats" and "adc_location_translation_table," will allow z_metadbuser_cornell account users to "read" the data in those tables. There is no need to assign permissions to the z_metadbuser_cornell account to see these tables as they are published because the read-only permission for z_metadbuser_cornell is part of the design of the local_static schema.