Finding the right name for a new component
Locked
Finding the right name for a new component
 
|
Dear all,
We have to develop an application based on OFBiz. In this application, there will be a system for clocking in/out for the employees.Once this new feature will be created, it will be submitted to the community. So I just want to give the right name to the entities, to be sure it is understandable for everyone. We were thinking of : * ClockingEntry (one entry) * ClockingAnomaly (one anomaly) * ClockingGroup (a group of rules) If those names are Ok for you, then we will keep with them. If you've got a better idea, don't hesitate to tell me ! Cheers, -- - Erwan - |
Re: Finding the right name for a new component
|
|
Hello,
In Belgium we call this functionality "ticking". regards, Heidi 2009/5/4 Erwan de FERRIERES <[hidden email]> > Dear all, > > We have to develop an application based on OFBiz. In this application, > there will be a system for clocking in/out for the employees.Once this new > feature will be created, it will be submitted to the community. > > So I just want to give the right name to the entities, to be sure it is > understandable for everyone. > > We were thinking of : > * ClockingEntry (one entry) > * ClockingAnomaly (one anomaly) > * ClockingGroup (a group of rules) > > If those names are Ok for you, then we will keep with them. If you've got a > better idea, don't hesitate to tell me ! > > Cheers, > > -- > - Erwan - > |
Re: Finding the right name for a new component
|
In reply to this post by Erwan de FERRIERES-3
In ofbiz always look what can be re-used before you create new....
clocking in and out looks like a workeffort with a start and end date/time? please also explain what anomaly and group should do? On Mon, 2009-05-04 at 15:58 +0200, Erwan de FERRIERES wrote: > Dear all, > > We have to develop an application based on OFBiz. In this application, > there will be a system for clocking in/out for the employees.Once this > new feature will be created, it will be submitted to the community. > > So I just want to give the right name to the entities, to be sure it is > understandable for everyone. > > We were thinking of : > * ClockingEntry (one entry) > * ClockingAnomaly (one anomaly) > * ClockingGroup (a group of rules) > > If those names are Ok for you, then we will keep with them. If you've > got a better idea, don't hesitate to tell me ! > > Cheers, > Antwebsystems.com: Quality OFBiz services for competitive rates |
Re: Finding the right name for a new component
|
|
Don't worry Hans, we've been looking before. One of the goals is also to
keep entities together, and be sure that we will try to reuse a lot. But for this new feature, we need to create specific entities, like * ClockingGroup (an employee belongs to a group. A group is a set of rules) * ClockingAnomaly which is an error in the clocking. For example, an employee is missing, so we have to keep this information, the person who validates the absence, the time of noticing, the reason, etc... * PartyClockingGroup which will keep "sums" of working time by weeks or months Hope that will clarify the needs ! Hans Bakker a écrit : > In ofbiz always look what can be re-used before you create new.... > > clocking in and out looks like a workeffort with a start and end > date/time? > > please also explain what anomaly and group should do? > > On Mon, 2009-05-04 at 15:58 +0200, Erwan de FERRIERES wrote: >> Dear all, >> >> We have to develop an application based on OFBiz. In this application, >> there will be a system for clocking in/out for the employees.Once this >> new feature will be created, it will be submitted to the community. >> >> So I just want to give the right name to the entities, to be sure it is >> understandable for everyone. >> >> We were thinking of : >> * ClockingEntry (one entry) >> * ClockingAnomaly (one anomaly) >> * ClockingGroup (a group of rules) >> >> If those names are Ok for you, then we will keep with them. If you've >> got a better idea, don't hesitate to tell me ! >> >> Cheers, >> -- - Erwan - |
Re: Finding the right name for a new component
|
|
In reply to this post by hans_bakker
sounds like a timekeeping function
Erwan de FERRIERES sent the following on 5/4/2009 7:54 AM: > Don't worry Hans, we've been looking before. One of the goals is also to > keep entities together, and be sure that we will try to reuse a lot. > > But for this new feature, we need to create specific entities, like > * ClockingGroup (an employee belongs to a group. A group is a set of rules) > * ClockingAnomaly which is an error in the clocking. For example, an > employee is missing, so we have to keep this information, the person who > validates the absence, the time of noticing, the reason, etc... > * PartyClockingGroup which will keep "sums" of working time by weeks or > months > > Hope that will clarify the needs ! > > Hans Bakker a écrit : >> In ofbiz always look what can be re-used before you create new.... >> >> clocking in and out looks like a workeffort with a start and end >> date/time? >> >> please also explain what anomaly and group should do? >> >> On Mon, 2009-05-04 at 15:58 +0200, Erwan de FERRIERES wrote: >>> Dear all, >>> >>> We have to develop an application based on OFBiz. In this >>> application, there will be a system for clocking in/out for the >>> employees.Once this new feature will be created, it will be submitted >>> to the community. >>> >>> So I just want to give the right name to the entities, to be sure it >>> is understandable for everyone. >>> >>> We were thinking of : >>> * ClockingEntry (one entry) >>> * ClockingAnomaly (one anomaly) >>> * ClockingGroup (a group of rules) >>> >>> If those names are Ok for you, then we will keep with them. If you've >>> got a better idea, don't hesitate to tell me ! >>> >>> Cheers, >>> > -- BJ Freeman http://www.businessesnetwork.com/automation http://bjfreeman.elance.com http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro Systems Integrator. |
Re: Finding the right name for a new component
|
|
Yeah, kind of like the existing Timesheet and TimeEntry entities (which related to WorkEffort, InvoiceItem, etc). -David On May 4, 2009, at 9:22 AM, BJ Freeman wrote: > sounds like a timekeeping function > > Erwan de FERRIERES sent the following on 5/4/2009 7:54 AM: >> Don't worry Hans, we've been looking before. One of the goals is >> also to >> keep entities together, and be sure that we will try to reuse a lot. >> >> But for this new feature, we need to create specific entities, like >> * ClockingGroup (an employee belongs to a group. A group is a set >> of rules) >> * ClockingAnomaly which is an error in the clocking. For example, an >> employee is missing, so we have to keep this information, the >> person who >> validates the absence, the time of noticing, the reason, etc... >> * PartyClockingGroup which will keep "sums" of working time by >> weeks or >> months >> >> Hope that will clarify the needs ! >> >> Hans Bakker a écrit : >>> In ofbiz always look what can be re-used before you create new.... >>> >>> clocking in and out looks like a workeffort with a start and end >>> date/time? >>> >>> please also explain what anomaly and group should do? >>> >>> On Mon, 2009-05-04 at 15:58 +0200, Erwan de FERRIERES wrote: >>>> Dear all, >>>> >>>> We have to develop an application based on OFBiz. In this >>>> application, there will be a system for clocking in/out for the >>>> employees.Once this new feature will be created, it will be >>>> submitted >>>> to the community. >>>> >>>> So I just want to give the right name to the entities, to be sure >>>> it >>>> is understandable for everyone. >>>> >>>> We were thinking of : >>>> * ClockingEntry (one entry) >>>> * ClockingAnomaly (one anomaly) >>>> * ClockingGroup (a group of rules) >>>> >>>> If those names are Ok for you, then we will keep with them. If >>>> you've >>>> got a better idea, don't hesitate to tell me ! >>>> >>>> Cheers, >>>> >> > > -- > BJ Freeman > http://www.businessesnetwork.com/automation > http://bjfreeman.elance.com > http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro > Systems Integrator. > |
Re: Finding the right name for a new component
|
|
In reply to this post by Erwan de FERRIERES-3
Read the Work Effort chapter in The Data Model Resource Book. It
discusses employee timekeeping. -Adrian Erwan de FERRIERES wrote: > Dear all, > > We have to develop an application based on OFBiz. In this application, > there will be a system for clocking in/out for the employees.Once this > new feature will be created, it will be submitted to the community. > > So I just want to give the right name to the entities, to be sure it is > understandable for everyone. > > We were thinking of : > * ClockingEntry (one entry) > * ClockingAnomaly (one anomaly) > * ClockingGroup (a group of rules) > > If those names are Ok for you, then we will keep with them. If you've > got a better idea, don't hesitate to tell me ! > > Cheers, > |
Re: Finding the right name for a new component
|
|
Yes it's some kind of timekeeping application.
I don't have the book yet (ordered 2 weeks ago, but amazon had no more in stock at this time...), so I will wait to update my entity names ! Adrian Crum a écrit : > Read the Work Effort chapter in The Data Model Resource Book. It > discusses employee timekeeping. > > -Adrian > > Erwan de FERRIERES wrote: >> Dear all, >> >> We have to develop an application based on OFBiz. In this application, >> there will be a system for clocking in/out for the employees.Once this >> new feature will be created, it will be submitted to the community. >> >> So I just want to give the right name to the entities, to be sure it >> is understandable for everyone. >> >> We were thinking of : >> * ClockingEntry (one entry) >> * ClockingAnomaly (one anomaly) >> * ClockingGroup (a group of rules) >> >> If those names are Ok for you, then we will keep with them. If you've >> got a better idea, don't hesitate to tell me ! >> >> Cheers, >> > -- - Erwan - |
Re: Finding the right name for a new component
|
|
In reply to this post by Erwan de FERRIERES-3
however it does not discuss the a lot of the functions you have described.
I can see yours being part of the HR component, as well, under Performance review item and the Item type. Also Performance Notes we have some components that have -ext added. maybe you can pick one of the components that closes fits your functions an make a folder with -ext. Adrian Crum sent the following on 5/4/2009 8:34 AM: > Read the Work Effort chapter in The Data Model Resource Book. It > discusses employee timekeeping. > > -Adrian > > Erwan de FERRIERES wrote: >> Dear all, >> >> We have to develop an application based on OFBiz. In this application, >> there will be a system for clocking in/out for the employees.Once this >> new feature will be created, it will be submitted to the community. >> >> So I just want to give the right name to the entities, to be sure it >> is understandable for everyone. >> >> We were thinking of : >> * ClockingEntry (one entry) >> * ClockingAnomaly (one anomaly) >> * ClockingGroup (a group of rules) >> >> If those names are Ok for you, then we will keep with them. If you've >> got a better idea, don't hesitate to tell me ! >> >> Cheers, >> > -- BJ Freeman http://www.businessesnetwork.com/automation http://bjfreeman.elance.com http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro Systems Integrator. |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |