Repository navigation
Events
Fang Yi Liu edited this page Sep 18, 2026
·
1 revision
- Also referred to as parent event, because EventOccurrences are generated from Event entries.
- Event can be recurring and contains rrule(s)
- Individual event that's generated from the associated potentially recurring parent event object.
- Future
EventOccurrences need to be regenerated if the parentEvent's timing changes. If thestart_timeof the new occurrence matches an old one, any changes from the old occurrence will be transferred to the new occurrence before the old one is deleted. -
eventandstart_timefields are used for syncing/reconnecting newEventOccurrenceobjects/rows to existingEventOccurrenceChanges when they're regenerated from the parentEvent. The correspondingEventOccurrenceChangeobject has the same fields.
- Contains user-modified event data fields for an
EventOccurrencethat correspond to the parentEvent's fields. Unchanged fields will be null. -
eventandstart_timeare special fields used for syncing/reconnecting these changes to new EventOccurrence objects/rows when they're regenerated from the parent Event. The corresponding EventOccurrence object has the same fields.
Click Pages above to see ALL Wiki documentation in alphabetic order.
The following list organizes the documentation and excludes some less critical documentation.
- Project History
- Stakeholders that will use PeopleDepot☑️
- How Knowledgebase will use People Depot - draft
- Joining the repository team
- Software Project Documentation in MkDocs
⚠️ Planning area for software system- Technical onboarding info for Developers☑️
- Requirements for PeopleDepot V1☑️
- PeopleDepot ERD, Tables and Fields☑️
- PeopleDepot @ Figma
- Quick Roadmap☑️
- [Decision Records]Decision-Records/Decision-Records)☑️