This is the place for the data that only the moderator needs, sees and/ or controls. It is separated from the core data structures to facilitate locking, access rights etc.
Note: Some data for which the moderator may need to maintain - for instance Text Placeholders - is to be found in . If in doubt, check there. The overview looks like this:
The discussion of the various tables, as well as tips for working with them are included below. But first we need to check if you’re a known coda user. This is what we see: Anonymous User
You need to login to an existing account or to mange the data here properly. No worries, it’s free, and you don’t have to give credit card details! In typical coda manner, you can , play with the data, break stuff and look under the hood at some of the functionality. Current Workshop:
Change the selection here: 🧬 Workshop Details
Create/ select the Workshop
Note: The selection below effects both the display of workshop-specific data across the entire document, as well as the assignment of dynamic and newly-created data to a specific workshop. If you add a new row to the table below, it will not be displayed until you change the selection to the title of the new entry.
👉 Select Current Workshop: Assemble Workshop Materials
Gather appropriate supporting material for use before, during or after the workshop.
This list will be automatically incorporated into each participant’s Dashboard, with completed assignments showing in the Assigned Tasks list.
Manage Workshop eMail Texts
The texts created here (Subject and Content) are used to assemble the eMail messages associated with each Participant (see table below). The eMail Type Other allows multiple entries for an individual workshop. Note however, that it is always the last text (coda last()) that will be sent via the eMail Other button.
Assemble Workshop Deliverables
Gather appropriate supporting material for use before, during or after the workshop.
This list will be automatically populated in each participant’s Dashboard, in the Delve into the Deliverables section. Note: You might consider how long this material should be available after the workshop has concluded and adjust your data cleansing schedule accordingly.
And in case you haven’t notice, we’ve provided some template pages ( and ) as well as a survey form. They need to be completed and linked to from here. Manage Workshop Meta Data
The following tables serve as lookups for various tables above and may be extended as required.
Note: Deleting entries here may effect functionality across the doc.
🧑🤝🧑 Manage Participants
Adding a participant is easy: select the appropriate workshop, add the person and select a role. If - for whatever reason - a person needs to have multiple roles in a workshop, then you need multiple entries in this table.
[Have you noticed the semantic error here? The Participants table includes everyone involved in the exercise, including those with roles other than Participant. We’ll put that on the To-Do List 🚴]
The Participant column is a coda People column, which has specific characteristics. Adding any old person here, won’t quite work. However, the selection dialogue allows you to Invite People, which is a neat way of making those people known to coda, and giving them access to this document.
The functional buttons are added automatically and can be triggered from this table. In addition, roles and tasks can be assigned by the users themselves - subject to specific constraints, as documented - in the appropriate Dashboards.
📋 Manage and Assign Tasks
This section of the data model addresses three areas: Meta Data supporting the functionality relating to task management; a master list of tasks and the actual tasks assigned to each participant.
Let’s look at each in turn.
Task Meta Data
The following tables are self-explanatory. The content serves as lookups for various tables through the doc and is used to drive (sometime quite complicated) task-related functionality. We suggest you before making changes here.
Note: Deleting entries here will effect functionality across the doc. Manage The Master Task List
Here too, the principle is easy: add a Task, determine the role to whom it applies and the time slot when it should be completed. Use the # column to determine the display sequence within the time slot.
Use the Detailed Steps columns (a coda Canvas) to add all the detail - including links, images and even buttons - needed to support the task. The clever bit is that the information you provide here is available to the user from within their personal Tasks Assigned view. Write once, use often - what’s not to like about it? 🤩
Managing Assigned Tasks
The title is slightly exaggerated - there’s not a lot of managing to be done!
But the Assigned Tasks need to be stored someplace and this is where.
The task assignment is driven through two mechanisms:
🏆 Voting & Promotion
Disclaimer: This doc was created on a tight schedule, with a hard deadline 📆. As a result, there is some structural sloppiness here, as the Voting & Promotion data are stored where they are used () and not here.
Now, what’s the plural of mea culpa ? 💬 Conversations & Contributions
Again, this is data that does not need to be specifically managed.
Entries are made in a (hopefully) controlled manner through various buttons. The various Dashboards provide a personal view of the conversations and contributions. [Do we detect some semantic sloppiness creeping in here? 🚴]
Those contributions that do need managing relate to the Suggested additions and Workshop additions in the Creative Workspace and are managed directly here: 🎵 A Note about the Workshop Review
The allows you to gather feedback on any or all aspects of the workshop. You should definitely include this link () to the online version of the survey in your list of . Note: This review is separate from - and serves a different purpose to - the , which is more concerned with the doc functionality, quality etc. Where is the data? The survey data (aka responses) are stored on . This page is normally hidden from view, but can be accessed from the 3-dot Menu of the + New Page entry at the bottom of the page list.