Hi,
I am quite new to coda and try to create a workflow in a way I know it from other tools, though I have the feeling it doesn’t make sense in coda. So maybe you can confirm my plan.
So I am going to do 2 things.
Tell what is my goal
Describe my own plan
In advance, thank you for your help
I want to create a workshop schedule for multiple workshops. Which are overlapping, so e.g. ws1: 1. January - 10. January; ws2: 5. Jan - 15. Jan; ws3: 9. Jan - 19. Jan.
Every workshop has 5 modules with varying times spent on every one module.
At the end I want have a timeline(Gantt) of all the workshops.
BTW: I already created all the dynamic elements, like starting time of one module depending on ending time of the previous one, so 2.A of the following plan is mostly done.
My plan:
A. Create template of a workshop
B. Create tables for every workshop based on the workshop template
C. Create one table(view?) with all workshop tables
D. Create timeline of the one table/ view created in C
Does it make sense?
Is there a better way to do it?
Personally, I’d avoid to create a table for every Workflowinstance. Rather creating one table Workflow Instances, specular to the Workflow Template, and identified by an ID (a name or whatever).
This way you can have dynamic views that can be filtered by name, having a single coherent structure for all the workflows - also for statistical/reporting and visualization purposes.
I have an idea, but I am not sure how to do that exactly in coda. I am used to python & SQL and Coda is somehow different so I believe I am still on my way to get the general logic.
It would be nice if you would go a little bit more in detail, since I really like to create my applications according to single source of truth idea and avoid redundancy.
Shape it according to your needs.
It can be simplified: Workshops and Workshops Instances reference tables are not necessary, but they allow an overall stronger consistency and enable an easier way to extrapolate stats.
Thank you so much!
Not all clear yet, but from my experience it can take time to understand new approaches. So I’ll keep going the way I can think of and will take a look at your proposal from time to time.
I prefer the MVP approach anyway, so it is OK not to find the perfect solution from the beginning on.
Maybe one little thing.
In the ‘3. Workshop Helper [name and workshop are mandatory]’, the ‘create instance’ pill is a button?
In my own way I’ve got to a point when I have a gantt chart for every workshop but I need one with all together.
I was wondering if there is a way to calculate and display only businessdays?
So, I took a look on your example again. I would like to confirm my understanding:
By using the ‘Create Instance’ button in ‘3. Workshop Helper’ I create a copy of the ‘2. Workshop Templates’ or do you mean something else by ‘“generates” the full set of activities from a template’?
Are these ‘None’ and ''clear pills in ‘6. Select Instances:’ some kind of filter components?
I don’t know what to say…thank you so much for your help and also the speed
But then they have to be in the same page/ subpage? Because it this point I have every workshop in a sole subpage but want to have the timeline of multiple subpages together.
This was easy. Now I have a ‘container’ page with instances of my template inside every row. Which is basically the same as duplicating the page using the 3-dot menu. Maybe you mean a different action that the ‘duplicate page’?
Not at all. In Coda you can put any view in any page of the doc.
Not sure I fully understood this one.
The advantage of using a data-only template is that you don’t need to duplicate/clone any unstructured data (the page itself) plus changing filters to the - still duplicated - view.
Practically speaking you would have just one page and one table (that you can reference anywhere else) instead of multiple pages each one with a manually filtered view.
But, please tell me if I correctly got your point.
My pleasure for the first one. Not always able to be that reactive for the second
