GoMeddo Data Model

Owned by Tim Schuitemaker

Last updated: Jul 26, 2023

2 min read

https://app.diagrams.net/#G1AHNzaFTLtvEPNoDWS78Btmo61dPGj_bV
https://lucid.app/lucidchart/d8b21abf-9c7e-475f-889d-205a887e7fba/edit?invitationId=inv_70d39142-5695-49a1-903c-e3c58c9d84a5&page=XVOBKPu7aP4u7#

Object	Standard/Custom	Description

Object	Standard/Custom	Description
Reservation	Custom	Our main object, a reservation represents an event/booking/reservation occurring between two specific dates/times. A reservation is displayed in our calendars.
Contact	Standard	The standard Contact object
Account	Standard	The standard Account object
Reservation Contact	Custom	The junction between Contact and Reservation allows you to add multiple "attendees" to a reservation.
Reservation Type	Custom	A Reservation Type determines the specific type of reservation, which, in turn, dictates the displayed fields on the reservation form and the related records associated with this reservation type.
Reservation Status	Custom	A Reservation Status determines the status of a reservation, which allows you to configure its colours on the calendars. Often times this is used to trigger logic when a reservation status changes.
Conflict	Custom	When a soft conflict occurs, a Conflict record is stored in this object, explaining why the Reservation conflicts. The conflict may be due to availability, double booking, or capacity issues.
Recurring Reservation	Custom	Holds details on the recurrence of a Reservation
Reservation Template	Custom	A templated reservation, holds specific details which can be activated as actual Reservations based on a pattern defined in the Schedule
Schedule	Custom	An abstract schedule / pattern (e.g. Monday to Friday) which can be activated to create actual Reservations
Staff	Custom	Our Staff object this can optionally be associated with either a Contact or a User. Additionally, instead of using the Staff object, you have the flexibility to utilize any existing Standard or Custom object in your organization that contains this type of information. For instance, consider a scenario where you already have an object that stores staff or employee data (i.e. anyone you want to book). For this situation, please refer to this article.
Resource	Custom	A resource in the system (e.g. Room 1 or Building 1) follows the Resource Type hierarchy. Alternatively, instead of using the Resource object, you can utilise any existing Standard or Custom object in your organisation that holds bookable information. For example, if you already have an object containing cars, apartments, boats (i.e. anything you want to book). For this situation, please refer to this article.
Resource Type	Custom	The resource type, whether it's a building, room, etc., is created in a hierarchy of resource types.
Availability	Custom	Determines the opening/closing times for the 'bookable' Dimension (Resource, Staff, or custom).
Service	Custom	A service that can be booked within a reservation. Such as, F&B, staff services, AV equipment etc.
Service Type	Custom	A type of a Service (e.g. F&B or AV)
Service Availability	Custom	Determines the conditions for using or purchasing a service within a reservation. E.g. only between two dates this service is available.