# airtable planning 20230801
## 20230801
* task base - tasks for ll full time staff base, dani manages
* so domain specific zone-
* jk makes missions base or whatever she wants for llufs
* sc/cc make a media work base for mpas etc
* work base -
* update base -
## 20230802
* from daily doc
* key record types
* events
* works
* updates/stories
* tasks
* already working (?)
* projects
* tools
* media/forms/types
[airtable dani started drafting-ish in](https://airtable.com/appxWOSediZAFCwmc/tbl7X29kx8OlJPAvR/viwh5KUCF1A9e2CG3?blocks=hide)
## 23-24 Bases
- LL Central Hub
- Members/users
- Tools
- Forms
- Tags?
- SlackUserIDs
- SlackChannelIDs
- SlackEmojis
- _PEOPLE
- term
- ProjectType
- LL Index (All Time Gallery? Or do this separately?)
- Projects 23-24
- Projects
- ProjectNames
- _TERM
- Metaproject
- Users
- AV/Studio/Equipment 23-24
- Events 23-24
- Do Your Work Base 23-24
- many of the tables from tasks
- Show Your Work Base 23-24
- everything made
- for now let's put everything in (including from previous years)
- updates
- stories (reports, social)
- Staff work bases
- MDFs
- LLUFs
- Ingest/media work/requests (if different from AV)
## to do
* start with...
* dani copies and preps projects-23-24
* dani prototypes ll-index (or all-time-gallery) with projects 22-23 and 23-24 (maybe even 21-22 etc?)
* mk and dani prioritize
* ll-event-base-23-24
* events
* sync from gcal table (at least ll-plan)
* users/attendees
* resources/rooms
* ll-do-your-work-base-23-24
* ll-show-your-work-base-23-24
* next
* ll-studio-bot-base-23-24 (mk does this)
* ll-moment-base-23.08 (mk does this)
* other experimental
## project launch lifecycle
* we get an email from a faculty member.
* they request a consultation.
* dani adds an appointment to the calendar.
* dani creates a metaproject and project in ll-projects-23-24
* dani needs to link the faculty member, so either they are already in _PEOPLE, or dani goes to bok whitepages. if they are there but not tagged as "LL", add LL. if they are not there, add their people record to the whitepages
* before the meeting/as emails come in, MW adds to [correspondance log](https://drive.google.com/drive/folders/1J-wLFU1VR1a1ezlPuqRl9DMxIAL68ot5).
* dani creates a notes by day doc for the meeting with linked correspondance log
* during the meeting, dani takes notes in that doc. if they want to schedule something, dani schedules in google calendar. if it's a workshop, dani adds a new project in ll-projects-23-24 and then goes to the task base to add the related projects (ie. workshop and assign it to someone, resource development, student video recordings, etc.)
* once a workshop is scheduled, we want a workshop plan doc to be made.
* we also want the notes by day moved over to the correspondance log
* we also want a metaproject folder to be made in [LL_CENTRAL_Projects](https://drive.google.com/drive/folders/1z-7U7xUWP73HhQ7QFw5-d7IFsk7FSFot) which then should be pasted in the "AssociatedMetaprojectFolder" in the Projects Table in the Projects base
* dani/madeleine scans calendar ahead 2 weeks to make sure we are sending check in emails before workshops
* then for these meetings, we create Meeting notes in [notes by day](https://drive.google.com/drive/folders/1VWJSvCfn2ywvuANlDobleLXRxDtCP0Sr). after the check ins, madeleine moves notes over the correspondance log
*where can we automate? where can we make smoother? where can dani get mw's help with some of these things?*