Page History
...
| RPDO_TABLE_REQUEST PARAMETERS | DATA TABLE Values |
|---|---|
| TABLE_REQUEST_ID | auto generated incremental value, corresponding to each concept in the data table. Unique for each concept example: 1282,1283, 1284 |
| TABLE_INSTANCE_ID | unique for each Data table ( same value for all the concepts underneath) example: 17 |
| TABLE_INSTANCE_NAME | Data table definition name |
| USER_ID | logged in user |
| GROUP_ID | project id |
| SET_INDEX | auto incremented for each concept name for the table instance |
| C_FACTTABLECOLUMN | |
| C_TABLENAME | |
| COLUMN_NAME | |
| C_FULLPATH | |
| C_COLUMNNAME | |
| C_COLUMNDATATYPE | |
| C_OPERATOR | |
| C_DIMCODE | |
| AGG_TYPE | |
| CONSTRAIN_BY_DATE_TO | |
| CONSTRAIN_BY_DATE_TO | |
| CONSTRAIN_BY_DATE_FROM | |
| CONSTRAIN_BY_VALUE_OPERATOR | |
| CONSTRAIN_BY_VALUE_CONSTRAINT | |
| CONSTRAIN_BY_VALUE_UNIT_OF_MEASURE | |
| CONSTRAIN_BY_VALUE_TYPE | |
| CREATE_DATE | |
| SHARED | Y (for project and system shared table definitions); N (User table definition) |
| DELETE_FLAG | Y or N |
| C_VISUALATTRIBUTES | values are LA or LH (based on visibility table definitions panel) |
Example:
QT_QUERY_RESULT_TYPE
The data table definition is logged as breakdown a breakdown type in the QT_QUERY_RESULT_TYPE table . The rows are inserted when the user saves the data table definition.
...
| RESULT_TYPE_ID | NAME | DESCRIPTION | DISPLAYTYPE_ID | VISUAL_ATTRIBUTE_TYPE_ID | USER_ROLE_CD | CLASSNAME |
Auto generated number example : 144 | RPDO_<TABLE_INSTANCE_ID> example: RPDO_17 | User-created <Table_Name>Request | CATNUM | LU (user tables) LP (Project shared tables) | DATA_LDS | edu.harvard.i2b2.crc.dao.setfinder.QueryResultPatientRequest |
Example:
| Info |
|---|
We recommend data requests be limited to DATA_LDS users and data exports be limited to MANAGER users. The user role determines if exports/requests are visible and runnable. Refer to section on User Roles and Actions |
...
