[Proposal] Extend facility entity

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

[Proposal] Extend facility entity

Vaibhav Jain
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,
[hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Jacques Le Roux
Administrator
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,
> [hidden email]
>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Michael Brohl-3
+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,
>> [hidden email]
>>
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Pierre Smits
In reply to this post by Vaibhav Jain
Hi All,

The facility entity should not have the openedDate and closedDate fields,
as these:

   1. can't be enough for all the moments a facility can be open or closed;
   2. not in line with startDate and thruDate fields (datetime type) used
   throughout numerous other entities to determine the lifespan of the facility

The openingDateTime and closedDate time can vary from
year/quarter/month/week/day to year/quarter/month/week/day for any kind of
facility in relation to any kind of target audience (e.g. supplier vs
customer). This is commonly related as scheduling, or calendaring.

For this (basic) functionalities (screens, services and entities) are
already in place in OFBiz.. See as a starting point: the work effort
component, or even better the asset management component.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project

On Sat, Nov 25, 2017 at 11:06 AM, Vaibhav Jain <
[hidden email]> wrote:

> 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,
> [hidden email]
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

pierre.gaudin
In reply to this post by Michael Brohl-3
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,
>>> [hidden email]
>>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Jacques Le Roux
Administrator
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,
>>>> [hidden email]
>>>>
>>>
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Pierre Smits
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>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://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 <
[hidden email]> 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,
>>>>> [hidden email]
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Jacques Le Roux
Administrator
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>
> OFBiz based solutions & services
>
> OEM - The OFBiz Extensions Marketplace1
> http://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 <
> [hidden email]> 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,
>>>>>> [hidden email]
>>>>>>
>>>>>>
>>>>
>>>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Pierre Smits
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>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://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 <
[hidden email]> 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>
>>
>> OFBiz based solutions & services
>>
>> OEM - The OFBiz Extensions Marketplace1
>> http://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 <
>> [hidden email]> 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,
>>>>>>> [hidden email]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

pierre.gaudin
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>
> OFBiz based solutions & services
>
> OEM - The OFBiz Extensions Marketplace1
> http://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 <
> [hidden email]> 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>
>>>
>>> OFBiz based solutions & services
>>>
>>> OEM - The OFBiz Extensions Marketplace1
>>> http://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 <
>>> [hidden email]> 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,
>>>>>>>> [hidden email]
>>>>>>>>
>>>>>>>>
>>>>>>>>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Pierre Smits
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 <[hidden email]> 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>
> > OFBiz based solutions & services
> >
> > OEM - The OFBiz Extensions Marketplace1
> > http://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 <
> > [hidden email]> 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>
> >>>
> >>> OFBiz based solutions & services
> >>>
> >>> OEM - The OFBiz Extensions Marketplace1
> >>> http://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 <
> >>> [hidden email]> 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,
> >>>>>>>> [hidden email]
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
>
> --
Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

pierre-29
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 [hidden email] 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>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://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 <
[hidden email]> 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>

OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://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 <
[hidden email]> 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,
[hidden email]



--
Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project


--
logoNrd
Pierre GAUDIN
Consultant Fonctionnel Apache-OFBiz, ERP en logiciel Libre
[hidden email]

8 rue des Déportés 37000 TOURS
Std: 02 47 50 30 54 - mob: 06 08 40 25 70

réseau LE

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Arun Patidar-2
+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 <[hidden email]> 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 <[hidden email]> <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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,[hidden email]
>
>
>  --
>
> 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
> [hidden email]
> 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/>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Deepak Dixit-3
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 <
[hidden email]> 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 <[hidden email]> 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 <[hidden email]> <
> [hidden email]> 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 <
> [hidden email]> 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 <
> [hidden email]> 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,[hidden email]
> >
> >
> >  --
> >
> > 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
> > [hidden email]
> > 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/>
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Jacques Le Roux
Administrator
Hi Deepak,

Seems to me that FacilityCalendar would be easier

My 2cts

Jacques


Le 27/11/2017 à 07:00, Deepak Dixit a écrit :

> 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 <
> [hidden email]> 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 <[hidden email]> 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 <[hidden email]> <
>> [hidden email]> 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 <
>> [hidden email]> 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 <
>> [hidden email]> 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,[hidden email]
>>>
>>>
>>>   --
>>>
>>> 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
>>> [hidden email]
>>> 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/>
>>>
>>>

Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Vaibhav Jain
Hello all,

Sorry for late reply as I was out of town.

Thank you very much to all of you for sharing this valuable information.

As we can conclude this conversation here.

I will create a new entity facilityCalendar which will create the
one-to-many relationship between facility and calendar. Here are the entity
attributes:

   1. facilityId*
   2. calendarId*
   3. fromDate*
   4. thruDate

A calendar will be used to store *openingTime*, *closingTime*, working
weekdays and all this type of stuff.

If this looks good to everyone then I will raise a JIRA for this.

Thanks & Regards

Vaibhav Jain
Hotwax Systems,
[hidden email]

On Mon, Nov 27, 2017 at 1:42 PM, Jacques Le Roux <
[hidden email]> wrote:

> Hi Deepak,
>
> Seems to me that FacilityCalendar would be easier
>
> My 2cts
>
> Jacques
>
>
>
> Le 27/11/2017 à 07:00, Deepak Dixit a écrit :
>
>> 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 <
>> [hidden email]> 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 <[hidden email]>
>>> 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 <[hidden email]> <
>>>>
>>> [hidden email]> 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 <
>>>>
>>> [hidden email]> 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 <
>>>>
>>> [hidden email]> 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,[hidden email]
>>>>
>>>>
>>>>   --
>>>>
>>>> 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
>>>> [hidden email]
>>>> 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/>
>>>>
>>>>
>>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: [Proposal] Extend facility entity

Vaibhav Jain
Hello all,

Here is the link to ticket OFBIZ-10040
<https://issues.apache.org/jira/browse/OFBIZ-10040> raised on JIRA.

Thanks & Regards,

Vaibhav Jain
Hotwax Systems,
[hidden email]

On Fri, Dec 1, 2017 at 10:42 AM, Vaibhav Jain <
[hidden email]> wrote:

> Hello all,
>
> Sorry for late reply as I was out of town.
>
> Thank you very much to all of you for sharing this valuable information.
>
> As we can conclude this conversation here.
>
> I will create a new entity facilityCalendar which will create the
> one-to-many relationship between facility and calendar. Here are the entity
> attributes:
>
>    1. facilityId*
>    2. calendarId*
>    3. fromDate*
>    4. thruDate
>
> A calendar will be used to store *openingTime*, *closingTime*, working
> weekdays and all this type of stuff.
>
> If this looks good to everyone then I will raise a JIRA for this.
>
> Thanks & Regards
>
> Vaibhav Jain
> Hotwax Systems,
> [hidden email]
>
> On Mon, Nov 27, 2017 at 1:42 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Hi Deepak,
>>
>> Seems to me that FacilityCalendar would be easier
>>
>> My 2cts
>>
>> Jacques
>>
>>
>>
>> Le 27/11/2017 à 07:00, Deepak Dixit a écrit :
>>
>>> 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 <
>>> [hidden email]> 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 <[hidden email]>
>>>> 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 <[hidden email]>
>>>>> <
>>>>>
>>>> [hidden email]> 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 <
>>>>>
>>>> [hidden email]> 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 <
>>>>>
>>>> [hidden email]> 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,[hidden email]
>>>>>
>>>>>
>>>>>   --
>>>>>
>>>>> 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
>>>>> [hidden email]
>>>>> 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/>
>>>>>
>>>>>
>>>>>
>>
>