How lehcimhdz/registros_public_version works
Project Type & Purpose
• Type: A batch-oriented document-generation and processing tool written in Python (evidenced by código.ipynb).
• Purpose: Automate creation of registry documents (“acuerdos”, “oficios”) from CSV inputs to reduce manual work for victim assistance staff.
File Structure
• Top-level data sources:
• data_registro.csv, Oficios_Informe.csv
• Template directories:
• Word_Oficios/ (Word-format letter templates)
• Acuerdos_Víctimas_Python/ (Python-ready “acuerdo” templates? possibly scripts or ancillary files)
• PDF_Oficios/ and PDF_Acuerdos_Víctimas_Python/ (output or intermediate PDFs)
• Key management:
• Llaves/ (likely cryptographic keys or credentials for signing)
• Processing logic:
• código.ipynb (Jupyter notebook orchestrating the pipeline)
Main Components
a. Data Ingestion Layer
– Sources: CSV files (data_registro.csv, Oficios_Informe.csv)
b. Template Storage
– Word_Oficios (letter .docx templates)
– Acuerdos_Víctimas_Python (agreement templates or helper scripts)
c. Processing Engine
– código.ipynb (Python runtime)
– External libraries: python-docx, reportlab/PyPDF2 (for PDF generation), pandas
– Key Store: Llaves (used by the engine to sign/embed keys into PDFs)
d. Output Storage
– PDF_Oficios (generated official letters)
– PDF_Acuerdos_Víctimas_Python (generated agreements)
e. (Optional) Logging/Monitoring
Relationships & Data Flows
• CSV Data → Processing Engine
• Template Storage → Processing Engine
• Llaves (Key Store) → Processing Engine
• Processing Engine → Output Storage (two targets: PDF_Oficios, PDF_Acuerdos)
• (If relevant) Processing Engine → Logs
Architectural Patterns & Design Principles
• Batch pipeline: all inputs are processed in discrete runs.
• Separation of concerns:
• Data layer (CSV storage)
• Template layer (Word & agreement templates)
• Processing layer (notebook/script)
• Key management (cryptographic isolation)
• Output layer (PDF directories)
• Use of external libs for document manipulation and signing.