*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
These are guidelines for using the Local Schemas on the Cornell Metadb reporting database.
What Local Schemas are available
| Schema Name | Schema Description |
|---|---|
| local_automation | This schema is for internal use by the Automation Team. |
| local_core | This schema is for internal use by the Reporting Team. |
| local_digpres | This schema is used by the HathiTrust team. |
| local_hathitrust | This schema is used internally by the HathiTrust team. |
| local_shared | 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. |
| local_statistics | This schema is for internal use by the Assessment and Planning team. |
How to Set Permissions on files used in Local Schemas
To give other users permission to see and use a table you have imported or created in a local schema in Metadb, you need to grant that user access to the new table. To do so, you can issue a command to alter the table permissions as a query in a DBeaver session connected to Metadb. Here is an example:
...