I think we can use TemporalExpression to manage this data. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co
On Mon, Nov 27, 2017 at 9:46 AM, Arun Patidar < arun.pati...@hotwaxsystems.com> wrote: > +1 for FacilityCalendar entity with purpose. > > -- > Thanks & Regards > --- > Arun Patidar > Manager, Enterprise Software Development > > HotWax Systems Pvt Ltd. > > www.hotwaxsystems.com > > > On Sun, Nov 26, 2017 at 3:31 AM, pierre <pierre.gau...@nereide.biz> wrote: > > > Hi Pierre, > > > > The "primary" pattern is often used such in productCategory or > > productStore entity. > > It can simplify acces for simple use. > > > > Thanks > > > > Pierre G > > > > > > > > On 25/11/2017 22:26, Pierre Smits wrote: > > > > Why would a new field called primaryCalendarId be required when this > could > > be resolved through you proposed FacilityCalendar entity? > > If there is only one it is the primary. And if multiple are required then > > one can have facilityCalendarPurposeId = > > primary/default/whatever-your-Definition-for-that-is. > > > > Best regards, > > > > Pierre > > > > > > On Sat, 25 Nov 2017 at 21:59 pierre.gaudin <pierre.gau...@nereide.fr> < > pierre.gau...@nereide.fr> wrote: > > > > > > Can we set a primaryCalendarId field on Facility entity and add a join > > entity FacilityCalendar with fields facilityId, caldendarId, > > facilityCalendarPurposeId, description for complex use ? > > > > Pierre > > > > > > On 25/11/2017 19:18, Pierre Smits wrote: > > > > Hi Jacques, All, > > > > Consider following scenarios: > > > > 1. A business with a facility in a city center, where city government > > has placed restrictions on the access of the city center for trucks, > > > > and > > > > other set of restrictions of opening hours for customers: > > 1. a calendar for suppliers and other logistics service providers > > 2. a calendar for customers > > 2. A hospital with multiple child facilities: > > 1. The warehouse: a calendar for suppliers and other logistics > > service providers > > 2. The outpatient clinic: a calendar for the opening hours > > 3. The nursing departments: a calendar regarding visiting hours > > > > Plus , for any kind of legal entity: one or more calendars regarding > > working hours of staff. I feel confident that you and others can dream up > > other scenarios too. > > > > Best regards, > > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> <http://www.orrtiz.com> > > OFBiz based solutions & services > > > > OEM - The OFBiz Extensions Marketplace1http://oem.ofbizci.net/oci-2/ > > 1 not affiliated to (and not endorsed by) the OFBiz project > > > > On Sat, Nov 25, 2017 at 5:32 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > > > > Hi Pierre, > > > > Actually I was answering to Pierre Gaudin :) > > > > More than one calendar for a facility? Do you have an example? > > > > Jacques > > > > > > Le 25/11/2017 à 15:53, Pierre Smits a écrit : > > > > > > Hey Jacques, > > > > You're welcome. > > > > {quote} > > Anyway, so Vaibhav, I think we can now put directly <field > > name="calendarId" type="value" /> in Facility > > {quote} > > > > Are you sure? Is there no scenario possible where a facility would > > > > need to > > > > apply more than 1 calendar? > > > > Best regards, > > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> <http://www.orrtiz.com> > > > > OFBiz based solutions & services > > > > OEM - The OFBiz Extensions Marketplace1http://oem.ofbizci.net/oci-2/ > > 1 not affiliated to (and not endorsed by) the OFBiz project > > > > On Sat, Nov 25, 2017 at 3:24 PM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > > Thanks for the info Pierre, > > > > Exactly the right answer! > > > > I thought there was something in workeffort data model, I know less > > manufacturing :) > > > > BTW, I wonder why TechDataCalendar is in manufacturing rather than in > > workeffort where IMO it would better fit since it's more general > > > > there. > > > > Anyway, so Vaibhav, I think we can now put directly <field > > name="calendarId" type="value" /> in Facility > > > > Jacques > > > > > > > > Le 25/11/2017 à 13:47, pierre.gaudin a écrit : > > > > Hi, > > > > Recently we had to store opening and closing hours for stores. To do > > > > so > > > > we have linked techDataCalendar with facility > > > > <extend-entity entity-name="Facility"> > > > > <field name="calendarId" type="value" /> > > </extend-entity> > > > > Thanks > > > > Pierre > > On 25/11/2017 11:53, Michael Brohl wrote: > > > > +1 for a timetable entity and linking it to facility > > > > This 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 > > > > > > -- > > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> <http://www.orrtiz.com> > > OFBiz based solutions & services > > > > OEM - The OFBiz Extensions Marketplace1http://oem.ofbizci.net/oci-2/ > > 1 not affiliated to (and not endorsed by) the OFBiz project > > > > > > > > -- > > [image: logoNrd] <http://nereide.fr/> > > Pierre GAUDIN > > Consultant Fonctionnel Apache-OFBiz, ERP en logiciel Libre > > informat...@nereide.fr > > 8 rue des Déportés 37000 TOURS > > Std: 02 47 50 30 54 - mob: 06 08 40 25 70 > > réseau LE <http://www.libre-entreprise.org/> > > > > >
