added a py file to audit the folder reorganization and help us fix the files we couldnt parse
This commit is contained in:
@@ -24,6 +24,7 @@ Extracts and organizes documents from FileCabinet CS (Thomson Reuters) using GUI
|
||||
| `fccs_verify.py` | Step 4 (optional): Compare manifests against exported files |
|
||||
| `fccs_check.py` | Utility: Interactively check if specific drawers exported completely |
|
||||
| `fccs_report.py` | Utility: Generate a clean client-facing HTML progress report (issues only) |
|
||||
| `fccs_report_reorganize.py` | Utility: Console report of `_unparsed` leftovers after reorganizing, with suggested missing folder templates |
|
||||
| `fccs_dump_controls.py` | Utility: Dump control identifiers of an on-screen dialog |
|
||||
|
||||
## Setup Per Engagement
|
||||
@@ -100,6 +101,14 @@ Files that can't be fully parsed still keep their client: the drawer ID and clie
|
||||
|
||||
Folder names are sanitized for Windows before use — trailing spaces and periods are stripped from each path component, since Windows can't create a directory ending in a space or dot (e.g. a client named `FARR GROUP, P.L.` becomes `FARR GROUP, P.L`). Reorganization is also resilient per file: if one file can't be placed for any reason, the error is logged and counted (reported as `errored` in the summary) and the run continues with the rest rather than aborting.
|
||||
|
||||
**Checking for folder template gaps:** After a reorganize run, get a quick internal summary of what didn't parse:
|
||||
|
||||
```
|
||||
python fccs_report_reorganize.py
|
||||
```
|
||||
|
||||
This walks `output_dir`, lists every client that has an `_unparsed` subfolder (plus the top-level `_unparsed`), and — because unparsed files keep their original export filename — recovers the folder field from each name and aggregates them into **suggested template lines** (years generalized to `YYYY`) that can be pasted into `fccs_folders.txt`. Add the missing templates and re-run `fccs_reorganize.py`. Console-only output; unparsed files with no recoverable folder field are counted separately (oddball names, not template gaps).
|
||||
|
||||
### Step 4 (optional): Verify Export Completeness
|
||||
|
||||
During export, each drawer's document list is captured from the FCCS dialog and saved as a manifest (in `manifest_dir`). These tools compare the manifests against the files actually in the export folder to confirm nothing was missed.
|
||||
|
||||
Reference in New Issue
Block a user