Create Table: user_availability

[fyliu]

Dependency

• Update Table: recurring_event (rename to event) #173
• Epic: Redesign event schema #88
  Completing the event table will give us more information on how we will be reading and writing day of week information.

Overview

We need to create the user_availability table so that we can update a shared data store across hackforla.org, vrms, civictechjobs, and tables (onboarding) project.

Details

A table and a model are the same thing

Action Items

• identify and document table description (see spreadsheet under Resources)
  • if not, reach out to PD leads
• compare and check off the data fields (below) against the ERD. Note any fields in the ERD that's missing from the list. (see Resources)
• compare the check off associated tables (below) against the ERD. Note any associated tables in the ERD that's missing from the list (see Resources)
• create a single model in Django (defining schema)
• write a test for the relationships this model will have with other models (e.g., creating a user and assigning them a set of permissions on a project).
• write an API end point
• write API unit tests
• document the endpoint

Resources/Instructions

• See People Depot Resources wiki page for links
  • ERD
  • Table and Field Definitions
  • API Endpoint
• See the wiki page for instructions.

Description

Users availability to attend team meetings

Data Fields

1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)
   • (PK) id - int
   • (FK) user_id - int
   • day_of_week - enum
   • start - time
   • duration - int
2. In ERD only (having items here indicates a mismatch, which requires a review)
   • None

Associated Tables

1. Copied from spreadsheet and checked off according to ERD. (unchecked items indicate a mismatch between ERD and spreadsheet, which requires a review)

   • user (many-to-one)

2. In ERD only (having items here indicates a mismatch, which requires a review)

   • None

[fyliu]

Problem:

1. Missing data fields in spreadsheet
   1. I added the 5 fields to the spreadsheet

[joshuayhwu]

class User_Availability(AbstractBaseModel):
	"""
	user availability
	"""
	id = models.IntegerField(primary_key=True)
	user_int = models.ForeignKey(User, on_delete=models.CASCADE)
	day_int = models.ForeignKey(Day_Of_Week, on_delete=models.CASCADE)
	time = models.timeField()
	duration = models.IntegerField()

	def __str__(self): 
		return f"{self.name}" 

[fyliu]

We should wait until we decide what to do about day_of_week table. We could be looking at deleting it and replacing that with an emumeration type field here.

[Neecolaa]

The data fields have been updated for this table. However, we're making this table dependent on the creation of the event table. The event table is higher priority, and figuring out how we're dealing with then days of the week in events will show us how we'll deal with them in this table.