118 reputation
6
bio website
location
age 37
visits member for 1 year, 10 months
seen Apr 17 at 0:15

Sep
25
comment Intuitive way to present chained 1-N relationships
A twist of your idea would be setting the Workers/Resource for the workOrder as now (screenshot2) but ignore that list when reporting activities (allowing to chose any Worker available, not just the assigned to the WorkOrder). The advantage would be more flexibility for the user, and that now the data between both popups is not related (in a DB meaning). The disavantage will be that, for every Activity added, the user will be offered a longer pick list. I will ask the project functionals, thanks.
Sep
25
comment Intuitive way to present chained 1-N relationships
Do you mean getting away with the pick list in screenshot 2 and just allowing any worker to be used for new activities? The trouble is that when a workOrder is created, the resource (worker) is assigned, then a printed notice passed to him/them, and after the workOrder has been fulfilled then the activities are recorded. So, I need to add resources to WorkOrders without activities.
Sep
25
comment Intuitive way to present chained 1-N relationships
@LorenRogers no, each ticket has N workOrders, each workOrders N resources/workers, each worker N activities. I agree that maybe the question is too long, I'll think about reworking it.
Sep
25
awarded  Editor
Sep
25
revised Intuitive way to present chained 1-N relationships
added 1691 characters in body
Sep
16
awarded  Teacher
Aug
24
awarded  Tumbleweed
Aug
17
comment Designing price list for suppliers
For what I see I would go for some FOSS solution already packaged; I do not know of something like that but I bet there are some alterntives. In the end it is you who must select the application who better fits your needs and experience.
Aug
17
answered Designing price list for suppliers
Aug
17
asked Intuitive way to present chained 1-N relationships
Jun
4
comment Very simple Welcome page/menu vs functionality
Principally the issue is context info ("hey, you are in the maintenance app, not in accounting"). Some help is always useful, though in this case the app is so simple that it will be minimal (but there will be some, we have some computer-handicapped users). Also, my thought was that (in case of no welcome), sending the user to one page (search / create) and having them look for the button that redirects to the page they really want in a page with lots of other controls might not be optimal.
Jun
4
awarded  Supporter
Jun
4
awarded  Scholar
Jun
4
accepted Very simple Welcome page/menu vs functionality
Jun
4
awarded  Student
Jun
4
asked Very simple Welcome page/menu vs functionality