New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

use Airtable to store studio data #3

Open

kapil1garg opened this issue Jan 18, 2022 · 2 comments

Labels

Contributor

kapil1garg commented Jan 18, 2022

Will be easier to maintain versus MongoDB rn, and won't require mode code to develop editing interfaces.

kapil1garg added the enhancement label

Contributor Author

kapil1garg commented Jan 18, 2022 •

edited

a lot of the fetching code can be lifted from dtr-mdb2airtable

Contributor Author

kapil1garg commented Feb 6, 2022

some tables that we should have:

Social structures
- People: names, roles, project(s) they are on, sig membership
- SIGs
- Committees: include head and members
Venues
- SIGs
- Mysore/Office Hours (need to support different office hour times for each proj)
- Studio
Tools
- Sprint log
- Research canvases
- LIP signup
- Pair Research
Processes/events
- Status Updates: dates + projects/people signed up (in the future, we can use this to schedule it during the first DTR class)
- Sprints
- Events: things like open house, interview day, etc.

kapil1garg mentioned this issue

update fixtures for W2022 #11

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment