+1 for a timetable entity and linking it to facilityThis will give us much more flexibility and avoids adding more and more fields to the facility table.
Thanks, Michael Am 25.11.17 um 11:39 schrieb Jacques Le Roux:
Hi Vaibhav,That sounds reasonable to me. I notably like this feature when Googling for a *physical* store to go buying things.Then you should maybe consider having a new Timetable Entity and link it from Facility.I had a look at what already exists in the Data Model, notably Timesheet and TimeEntry, but they don't really fit here.Jacques Le 25/11/2017 à 11:06, Vaibhav Jain a écrit :Hello all, *Facility* entity has attributes for *openedDate* and *closedDate* which specify that facility opening date and closing date if the facility is closed i.e. not in-use. All facilities are not open on all weekdays. We can have an attribute to record this. A retail store is also a facility and we should record *openingTime* and *closingTime* in facility entity. *openingTime* and *closingTime* may be different for some of the weekdays as well. Please share your thoughts on this. -- Thanks and Regards, Vaibhav Jain Hotwax Systems, vaibhav.j...@hotwaxsystems.com
smime.p7s
Description: S/MIME Cryptographic Signature