How lehcimhdz/notificaciones_registro works
Project Type and Purpose
• This is a small, standalone automation tool (a script/notebook) rather than a full-stack or microservices application.
• Its purpose is to read a list of pending victim‐registration cases from a CSV, use stored account credentials (“Llaves”), and send notifications (via WhatsApp or similar) so that staff no longer have to process each document manually.
File‐Structure Analysis
• Top level:
• auto_notificaciones.ipynb – the Jupyter notebook driving the process
• notificaciones.csv – input data (victims to notify)
• PyWhatKit_DB.txt – likely credentials or serialized API tokens for PyWhatKit
• Llaves/ – directory holding key files (API keys, certificates, etc.)
• README.md – high‐level project purpose
• No backend/frontend split, no external database—just local CSV and key files.
Key Components
a. Data Source
• notificaciones.csv – CSV file listing user/contact info and notification state
b. Credentials Store
• Llaves/ directory + PyWhatKit_DB.txt
• Holds API keys or authentication tokens for the messaging service
c. Notification Engine
• auto_notificaciones.ipynb (or underlying Python scripts/libraries)
• Reads CSV, loads keys, formats messages, and invokes PyWhatKit (or similar)
d. External Service
• WhatsApp Web API (via PyWhatKit) or SMTP if email is used—represents message delivery
e. Operator/Trigger
• A human or scheduler that launches the notebook or Python script
Architectural Patterns & Principles
• Single‐responsibility: separation between data (CSV), credentials (Llaves), and logic (notebook)
• Simple pipeline: Extract (CSV) → Transform (format message) → Load/Send (external API)
• Extensibility: additional channels (email/SMS) could be added by swapping out the PyWhatKit calls