Team Pulse - Employee Hub

• 

  Availability Page

• 

  Reassignment Page

• 

  Task Utilization Page

• 

  Events Page

• 

  Timeline Page

• 

  Normalized Data Page

• 

  Actions Page

Inspiration

When viewing the different problems provided for the Hackathon, my team decided to select the third problem that has to do with making a hub that can contain availability status and utilization by taking in data from multiple different calendar sources. We like the idea of creating a solution to this problem more than the other and so we decided to try and implement a solution.

What it does

Our app takes in an employee database and multiple generated calendars that are in the format of Google and Microsoft calendars. The data from the calendars are normalized to show the employee id, event, and the time they will be busy. This normalized information is then used to update a list that shows available employees, which can be seen as boxes of information on the front end. Task utilization is also implemented in a way where each employee has a certain amount of max tasks they can do. When comparing that to the current tasks they are doing, they get a task utilization score.

How we built it

We used Python to create the backend logic. The employee database and dummy data formatted in the Google and Microsoft templates are stored as json files. They are looped through in order to normalize the data and then that new normalized data is also stored a json. From this point Claude was used in implementing the front end of the project. It was able to connect the backend to the front, showing who is available and their task availability.

Challenges we ran into

When trying to take calendar data from Microsoft, we realized it would be difficult to obtain an API key in time in order to be authorized to access the data we needed. We decided to create dummy data in roder to replicate what it would be like if we did have the authorization and then create the normalized data from that.

Accomplishments that we're proud of

We are proud that we were able to come together and solve the problem at hand even though it may not be completely finished. Being able to connect the back end and front end of the application with Claude was probably one of the biggest accomplishments we did.

What we learned

We learned more about how calendar API data is stored and how different calendars store their data differently. We also learned what it was like to use Claude and how prompting is important in order to get the result you are looking for.

What's next for Centralized Availability and Task Hub

In the near future we plan on truly implementing the ability to get data from real calendars after obtaining the correct authorization.

Built With

• html
• python