DMS settings
The DMS heading under Setting is one menu entry that opens the dms_reference module. dms_reference.php includes modules/dms_reference/<modref>.php for the screen chosen on the left; the list of screens and their labels is the dms_reference group in Base.php. Most are plain code-and-description lists, scoped by project.
How this page was verified
Written from master on 2026-09-06 and compared with the big five the same day. No earlier page existed. Every screen was mapped to its table; the per-fork table below comes from listing the folder in each repository.
The screens
| Label | modref | Table | Feeds |
|---|---|---|---|
| Area Number | areanumber | ts_area_number | MDR |
| Well Site | well_site | ts_well_site | MDR |
| Discipline | discipline | ts_docdiscipline | MDR, document numbering |
| Document Type | doctype | ts_doctype | MDR |
| Document Subtype | subtype | ts_subtype (per discipline) | MDR |
| Document Category | doccat | ts_doccat | MDR |
| Drawing Category | drawing_category | ts_drawing_category | MDR |
| Contract / PO Number | contract_no | ts_contract_no | MDR |
| Progress Gate | progress_gate | ts_progress_gate: Sequence, Gate Code, Submission % (submission_progress), Completion % (percentage) | the order of the issued statuses and the two progress credits, see MDR Report, Submission % and Completion % |
| Issued Status | issued | ts_issued_status (per progress gate) | MDR, transmittals |
| Review Time | workingdays | ts_workingdays (per issued status) | routing due dates |
| Return Code | document_result_code | ts_doc_resultcode | Return |
| Routing Type | routing_type | ts_ref_routing_type | routing templates |
| Library Index Reference | docindex | ts_doc_library | the Document Library tree and its group privileges |
| System Code | system_code | ts_system | MDR |
| Document Classification | doc_classification | ts_doc_classifications | MDR, auto numbering |
| Function Code | function_code | ts_function_codes | MDR |
Four more screens are in the folder and reached from the same left list, but are settings rather than lists:
| Screen | Table | What it sets |
|---|---|---|
| Watermark settings | ts_watermarks, ts_watermark_settings | the text, font size, opacity and rotation stamped on downloads |
| Retention | ts_doc_retention_settings | how long documents are kept, per resource |
| Auto document numbering | ts_doc_auto_numbering_settings | the number pattern per classification |
| Auto folder creation | ts_auto_creation_folder_settings | see Auto Folder Creation |
multi_project_setting.inc.php and its two handlers are included by the dispatcher itself and carry the project selector at the top of every screen.
What still runs on the legacy helper
The seven newest screens (system_code, doc_classification, function_code and the four settings screens) are fully on $pdo. The older lists have one to four legacy calls each, usually the delete or the reorder path. Two are heavier: docindex (41 legacy calls, the library tree and privilege editor) and routing_type (14). Expect the grid to load and an edit to fail on those where the helper throws.
Gotchas
- Everything is per project. A code that "disappeared" was usually entered under another project. The selector at the top decides what the grid shows.
- Subtype hangs off discipline, issued status off progress gate, review time off issued status. Deleting the parent orphans the children; the grids do not cascade.
docindexedits the samets_doc_librarytable as the library itself. Renaming an index here renames the folder for everyone.
Instance differences
Checked on 2026-09-06 by listing modules/dms_reference/ in each repository.
| Instance | Missing from master's list | Added |
|---|---|---|
| Jadestone | Well Site | Field Code (field_code), Group Code (group_code) |
| Medco | — | Business Unit, Location, Region, Sub Discipline, SDRL Code, Vendor Package, Code Package Identifier, File Name Setting |
| JOTRE | Well Site, Auto folder creation | — |
| Timas | Well Site, System Code, Document Classification, Function Code, Watermark, Retention, Auto numbering, Auto folder creation | — |
| Tomori | System Code, Document Classification, Function Code, Auto folder creation | Classification, Contractor, Division, Element, Project Name, Subcat |
| KTP | the same eight as Timas | — |
On JOTRE and Timas nearly every shared screen also differs in content (19 and 16 files), because their forks predate the PDO rewrite of these lists.
Related
- Projects and MDR settings: the per-project switches that decide which of these lists the MDR form shows.
- Auto Folder Creation.