Add smart institution name cleaning to handle OCR artifacts like trailing CMA codes that cause false negative matches. Problem: - PDF "重庆市财政局..._pages3-6.pdf" extracted institution with trailing CMA code - "四川合泰与必摩适检测有限公司430334" vs "四川合泰与必摩适检测有限公司" - Similarity: 70.0% → incorrectly classified as "no_match" - The core institution name is actually identical Solution: - Add clean_institution_name() function to remove trailing artifacts: * Remove 6+ digit numbers (CMA codes) * Remove 11+ digit numbers (full CMA codes) * Remove trailing punctuation and whitespace - Enhance classify_match() with field_type parameter - Apply cleaning for institution field comparisons Results for test case: - Before: 70.0% similarity, edit distance 6 → "no_match" - After: 100.0% similarity, edit distance 0 → "exact" This fix improves accuracy for cases where OCR accidentally captures CMA codes or other numbers as part of the institution name. Co-Authored-By: Claude Code <noreply@anthropic.com> |
||
|---|---|---|
| data | ||
| report_viz | ||
| scripts | ||
| src | ||
| temp_classpath | ||
| .gitignore | ||
| BUILD_REPORT.md | ||
| COMPREHENSIVE_REPORT.md | ||
| DJL_UPGRADE_ATTEMPT_REPORT.md | ||
| IMPLEMENTATION_SUMMARY.md | ||
| INTEGRATION_GUIDE.md | ||
| INTEGRATION_TEST_REPORT.md | ||
| ManualTest.java | ||
| PADDLEOCRVL_INTEGRATION.md | ||
| README.md | ||
| cma_extraction_template_primary.py | ||
| jar_paths.txt | ||
| pom.xml | ||
| reply.md | ||
| res.json | ||
| run_reference_test.bat | ||
| run_test.bat | ||
| run_test_v2.bat | ||
| run_viz_report.bat | ||
| settings.xml | ||
| test_accuracy_batch_full.py | ||
| test_paddleocr_vl_quick.py | ||
| v_verify_logic.py | ||
| 测试结果汇总.txt | ||
README.md
Report Detection Backend
Java-based backend system for automated report validation and comparison using OCR.
Technology Stack
- Core: Java 8 (Spring Boot 2.7.18)
- Security: Sa-Token (RBAC, Session Management)
- OCR Engine: PaddleOCR (via DJL - Deep Java Library)
- Database: PostgreSQL (with Dynamic Datasource support)
- Build Tool: Maven
Features
- RBAC Implementation: Multi-role support (ADMIN, AUDITOR, USER) with uppercase standardization.
- Sa-Token Security: Annotation-based permission checks and secure login.
- Auditor Context Switch: Specialized feature for Auditors to switch between institutional views.
- PDF Processing: Automatic conversion of PDF reports to images for OCR analysis.
- Automated Verification: Integration tests using H2 in-memory database.
Getting Started
Prerequisites
- JDK 8 or 17
- Maven 3.6+
- PostgreSQL (optional for local dev if using H2 profile)
Run the Application
mvn clean package
java -jar target/report-detect-backend-1.0.0.jar
Run Tests
mvn test -Dtest=SecurityRBACVerificationTest
Security Configuration
Default accounts created on initialization:
admin/123456(ADMIN)auditor/123456(AUDITOR)user/123456(USER)