Storing the Reviewer workspace in an enterprise geodatabase (Aviation)

The following process outlines the steps for setting up a Reviewer workspace when working with enterprise geodatabases. Since access to the database tables is controlled by database permissions, it will be necessary to initialize the Reviewer workspace as the database owner and grant privileges to the appropriate database users so they can access and work with Reviewer sessions.

Step 1: Create a Reviewer workspace in the enterprise geodatabase

The geodatabase administrator user must start a new Reviewer session in the enterprise geodatabase where the Reviewer dataset and tables will be stored.

When you want to start a Reviewer session, you are prompted to choose a workspace, which is a geodatabase that can contain the data you want to review or be a separate database that only contains the Reviewer dataset information, depending on your organization's workflow. By default, the user name is the Windows login name for the current user. You can also provide a custom name for the current Reviewer session.

The first time a database is used to store Reviewer information, a new dataset and tables are added to your database to accommodate the individual Reviewer sessions. All future sessions write to these same tables.

Caution:

Directly editing the contents of the Reviewer workspace can corrupt the relationships between the tables and affect the overall workspace. It is recommended that you work with the user interface to modify table contents.

Steps:

1. Start ArcMap.
2. On the main menu, click Customize > Toolbars > Data Reviewer.
3. Click the Reviewer Session Manager button on the Data Reviewer toolbar.

   The Reviewer Session Manager dialog box appears.
4. Click Browse in the Reviewer Workspace area.

   The Reviewer Workspace dialog box appears.

5. Navigate to the geodatabase in which the Reviewer dataset is going to be stored.
6. Click Add.
7. Click New to start a new Reviewer session.

   The Reviewer Workspace Properties dialog box appears.
8. Choose an option for the spatial reference.
   • Use Default Spatial Reference (WGS-84)—Sets the Reviewer dataset's spatial reference to GCS_WGS_1984. This is the default spatial reference for ArcMap.
     Note:

     In most cases when using ArcGIS for Aviation, choosing the Use Default Spatial Reference (WGS-84) option is suggested.

   • Use Active Data Frame Spatial Reference—The Reviewer dataset's spatial reference matches that of the active data frame.
   • Browse To Spatial Reference—Sets the Reviewer dataset's spatial reference to one you choose.
     Note:

     If you choose Browse To Spatial Reference, the New Spatial Reference wizard appears so you can choose the spatial reference you want to use with the Reviewer dataset.

   Note:

   The spatial reference selected for the Reviewer dataset should match the spatial reference of the data you are validating. This allows the error geometry to be stored in the feature classes within the Reviewer dataset.

9. If necessary, choose the Use configuration keyword option in the Select Configuration Keyword area to choose a different configuration keyword for the database.
10. Click the Use configuration keyword drop-down arrow and choose a configuration keyword.

    The keywords available in the list are dependent on what the database administrator has specified in the DBTUNE table as configuration keywords.

11. Click OK.

    The ID and Name text boxes are automatically populated in the Session area.

12. If necessary, type a custom name for the current Reviewer session in the Name text box.

    By default, the name matches the ID.

13. Click the Reviewer Dataset Version drop-down arrow and choose the geodatabase version to be used.

    The geodatabase version you choose from the list is the one in which the Reviewer table records are going to be stored.

14. Click Start Session.

    The button name changes to End Session.

15. Click Close.

Step 2: Set the dataset and tables as versioned

The geodatabase administrator must set the following as versioned in ArcCatalog:

• RevDataset (feature dataset)
• RevBatchRunTable table
• RevCheckRunTable
• RevTableConfig table
• RevTableLocation table
• RevTableMain table

Learn more about registering data as versioned

Caution:

Directly editing the contents of the Reviewer workspace can corrupt the relationships between the tables and affect the overall workspace. It is recommended that you work with the user interface to modify table contents.

Step 3: Grant permissions to the dataset and tables

The geodatabase administrator must grant SELECT, UPDATE, INSERT, and DELETE privileges to the following for all users that will be accessing the Reviewer workspace:

• GDB_RevAdminLocation
• GDB_RevSessionTable
• RevBatchRunTable
• RevCheckRunTable
• RevDataset (feature dataset)
• RevTableConfig
• RevTableGUIProperties
• RevTableLocation
• RevTableMain

Learn more about user permissions for geodatabases in Oracle

Learn more about user privileges for geodatabases in SQL Server

Learn more about granting and revoking privileges on datasets

Step 4: Grant select permissions for the remaining Reviewer tables

The geodatabase administrator must grant SELECT privileges to the following tables for all geodatabase users that will be accessing the Reviewer workspace:

• RevAdminCustomFields
• RevAdminDescriptions

Tips for granting permissions

• Only grant a geodatabase user SELECT, UPDATE, INSERT, and DELETE privileges to the RevAdminCustomFields table if the geodatabase user has privileges to modify the database schema.
• Only grant a geodatabase user SELECT, UPDATE, INSERT, and DELETE privileges to the RevAdminDescriptions table if you want the geodatabase user to be able to add customized error descriptions. Note that all other geodatabase users accessing the Reviewer dataset will see the customized error descriptions.

Learn more about user permissions for geodatabases in Oracle

Learn more about user privileges for geodatabases in SQL Server

Learn more about granting and revoking privileges on datasets

Step 5: Configure cache tables for users

For enterprise geodatabases (Oracle and SQL Server) that create cache tables to store feature selections in ArcMap that are greater than 100, the geodatabase administrator must create the cache table for each geodatabase user.

Steps:

1. Grant CREATE TABLE permissions to the user.

   • For a geodatabase in Oracle, this is the Geodatabase Administrator user.
   • For a geodatabase in SQL Server, this is the Data Creator user

2. If necessary, copy a feature class with more than 100 features into the Reviewer workspace.
3. In ArcMap, load the feature class.
4. Select more than 100 features.

   This automatically creates the cache table.

5. Remove CREATE TABLE permissions as appropriate.

Once this process is complete, you have created a Reviewer workspace that can be used by the appropriate people in your organization who are working with enterprise data.