VSN 445 : Finalizing a first ready usable version of the preparation database.

Overview

This merge request introduces the Passenger Preparation module, focusing on defining and organizing entities related to prepared passengers, their contacts, addresses, representatives, and associated transport schedules. It also includes several refactors and documentation updates.

---

1. New Features

1.1 Core Prepared Entities

• Prepared Passenger

  • Introduced the main prepared entity representing passengers during the preparation phase.
  • Cleaned up older, obsolete prepared entities.
  • Added a colorCode attribute for enhanced passenger representation.
  • Included a departmentId field to link passengers with their respective departments.

• Prepared Representative

  • Defined a refined representative entity to accurately represent the passenger’s representative.
  • Established necessary entity relationships.

• Prepared Contact

  • Added a new entity to handle contact details related to prepared passengers and their representatives.
  • Set up entity mappings for proper association handling.

• Prepared Address

  • Introduced the prepared address entity, linked with the representative and passenger entities to store address-related data.

---

1.2 Schedule Management

Two main categories of schedules were introduced:

• Schedule 0: Transport Schedules

  • Defined PreparedDayScheduleEstablishment to represent transport schedules associated with establishments.
  • Built necessary entity relationships between passengers and their corresponding transport schedules.

• Schedule 1: Representative & Trajectories Schedules

  • Added PreparedDayScheduleRepresentative entity to manage schedules related to passenger representatives and their trajectory planning.
  • Established inter-entity relationships for coherent data flow between passengers, representatives, and schedules.

---

1.3 Relationship Mapping

• Created relationships between:

  • Passengers ↔ Representatives
  • Representatives ↔ Contacts / Addresses / Schedules
  • Passengers ↔ Transport Schedules

This ensures a consistent and connected data model across all prepared entities.

---

2. Refactoring

• Passenger Entity Update: Added colorCode field for improved UI representation.
• Imports Cleanup: Removed unused imports from all newly introduced entities to enhance code readability and maintainability.

---

3. Documentation

• Updated the changelog markdown file to reflect:

  • The introduction of new prepared entities.
  • The addition of scheduling structures.
  • Relationship mappings and refactors applied to the module.

---

4. Impact

This merge creates a structured data foundation for passenger preparation, ensuring scalability for future scheduling, transport planning, and passenger management features. It also improves maintainability through better entity design and documentation consistency.

---