#SharedCalendars

[saasboxy]

𝐁𝐨𝐨𝐬𝐭 𝐓𝐞𝐚𝐦 𝐂𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐨𝐧 𝐰𝐢𝐭𝐡 𝐓𝐢𝐝𝐲𝐂𝐚𝐥 🤝 Need to coordinate meetings with multiple participants? TidyCal's group booking feature lets you set up sessions for several attendees effortlessly. Perfect for webinars, classes, or team meetings. You can also specify the maximum number of participants per time slot and manage bookings efficiently. Streamline Your Group Scheduling with TidyCal's Features: ⭕ Shared Calendars: Create shared calendars to keep your team on the same page. ⭕ Availability Insights: View team members' availability at a glance. ⭕ Integrated Communication: Connect with TidyCal and get seamless meeting coordination. 🥁 Ready to enhance your team's productivity? Start using TidyCal today and experience effortless scheduling!

#TeamScheduling #SaaSboxy #ProductivityBoost #TidyCal #EffortlessMeetings #SharedCalendars #AvailabilityInsights #IntegratedCommunication

[museummixtape]

I’m not mad I just thought you said you’d be home earlier. - since ca 1640s! #tefaf #parkavenuearmory #sword #olivebranch #communication #sharedcalendar #sittingup (at Park Avenue Armory) https://www.instagram.com/p/B4iQD60F3Xr/?igshid=1o1ucl1gvdf2t

[black7375]

이게 맞나 하는 생각

// https://dbdiagram.io/d // Use DBML to define your database structure // Docs: https://dbml.dbdiagram.io/docs Table User { id varchar [pk] // UUID username varchar [not null] } Table Calendar { id varchar [pk] name varchar [not null] author varchar [not null, ref: > User.id] } Table SharedCalendar { id varchar [ref: > Calendar.id] user varchar [ref: > User.id] Indexes { (id, user) [pk] } } Table Event { id varchar [pk] // UUID title varchar [not null] calendar varchar [not null, ref: > Calendar.id] start datetime [not null] end datetime [not null] dday tinyint [not null] // 0: "NONE", 1: "LEFT", 2: "PASSED" location multipoint [null] service varchar [not null, ref: > EventService.id] } Table Repeat { id varchar [pk, ref: - Event.id] every int [not null] units tinyint [not null] // "DAY", "WEEK", "MONTH", "YEAR" condition tinyint [not null] // "NONE", "DAY", "WEEK" end datetime [null] end_count int [null] } Table RepeatMonth { id varchar [ref: > Event.id] month tinyint [not null] Indexes { (id, month) [pk] } } Table RepeatWeek { id varchar [ref: > Event.id] nth tinyint [not null] // MONTH_WEEK: 1~6 day tinyint [not null] // WEEK[number]: 1~7 Indexes { (id, nth, day) [pk] } } Table RepeatDay { id varchar [ref: > Event.id] day tinyint [not null] // MONTH_DAY: 1~31 Indexes { (id, day) [pk] } } Table RepeatException { id varchar [ref: > Event.id] date datetime [not null] Indexes { (id, date) [pk] } } Table EventService { id varchar [pk] icon varchar [not null] // Path or url name varchar [not null] title varchar [not null] }

에서 unique한 이름을 가진 컬럼 이름을 가지라는데...

Table User { userKey varchar [pk] // UUID userName varchar [not null] } Table Calendar { calendarKey varchar [pk] calendarName varchar [not null] calendarAuthor varchar [not null, ref: > User.userKey] } Table SharedCalendar { sharedCalendarKey varchar [ref: > Calendar.calendarKey] userKey varchar [ref: > User.userKey] Indexes { (sharedCalendarKey, userKey) [pk] } } Table Event { eventKey varchar [pk] // UUID eventName varchar [not null] calendarKey varchar [not null, ref: > Calendar.calendarKey] eventStart datetime [not null] eventEnd datetime [not null] eventDday tinyint [not null] // 0: "NONE", 1: "LEFT", 2: "PASSED" eventLocation multipoint [null] eventService varchar [not null, ref: > EventService.eventServiceKey] } Table Repeat { repeatKey varchar [pk, ref: - Event.eventKey] repeatEvery int [not null] repeatUnits tinyint [not null] // "DAY", "WEEK", "MONTH", "YEAR" repeatCondition tinyint [not null] // "NONE", "DAY", "WEEK" repeatEndDate datetime [null] repeatEndCount int [null] } Table RepeatMonth { repeatMonthKey varchar [ref: > Event.eventKey] repeatMonthValue tinyint [not null] Indexes { (repeatMonthKey, repeatMonthValue) [pk] } } Table RepeatWeek { repeatWeekKey varchar [ref: > Event.eventKey] repeatWeekNth tinyint [not null] // MONTH_WEEK: 1~6 repeatWeekDay tinyint [not null] // WEEK[number]: 1~7 Indexes { (repeatWeekKey, repeatWeekNth, repeatWeekDay) [pk] } } Table RepeatDay { repeatDayKey varchar [ref: > Event.eventKey] repeatDayValue tinyint [not null] // MONTH_DAY: 1~31 Indexes { (repeatDayKey, repeatDayValue) [pk] } } Table RepeatException { repeatExceptionKey varchar [ref: > Event.eventKey] repeatExceptionDate datetime [not null] Indexes { (repeatExceptionKey, repeatExceptionDate) [pk] } } Table EventService { // Each service eventServiceKey varchar [pk] eventServiceIcon varchar [not null] // Path or url eventServiceName varchar [not null] eventServiceTitle varchar [not null] }

네이밍 컨벤션을 맞추기 위해 따라가지만 이게 맞나..싶긴하다.

[elivio]

From Health&Wellness, Personal Finance Management, Education, HomeManagement, myEspace, Recipes, SharedCalendar...ELIVIO is an ALL-FUNCTION FAMILY APP. Get Elivio today!