The output will be two files. One is the CSV file with the `.ics` extension, the other is a `event_uids.json` containing the unique identifier of each event line.
This will make updating the events via the CSV file easier.
# Key Features:
- UID Persistence:
Event UIDs are stored in a JSON file (event_uids.json).
If the event key (based on description, date, start time, and location) exists, the same UID is reused.
- LAST-MODIFIED Field:
The last_modified timestamp is added to each event, ensuring updates are detected by calendar applications.
- Resilience to Changes:
If an event's details are modified in the CSV, the application recognizes it as an update due to the persistent UID.
# Benefits:
Consistent Updates: Calendar applications update events with matching UIDs rather than creating duplicates.
Persistence: Even if the script is rerun, previously assigned UIDs remain consistent.