atsid / gcal-leave-scraper Goto Github PK

Setup to run on a schedule

The new react-calendar-render has been added and is functional. However, some of the CSS that was brought over doesn't quite work as it should inside of the material-ui view area. The CSS needs to be fixed to display the actual days in the calendar as a proper grid and make sure the tables properly fill the space in the calendar view.

Need to mock the service calls so we don't require secret.json file. The cert info has been moved to config/local.coffee but is not present in the build.

This would be a hash that allows us to remove/hide some contacts from the Google API that are not relevant, such as admin accounts and conference rooms.

Requires mongo database to store custom
UI updates
New service endbpoint

We need to be able to determine the number of working days in a date range. Write a method to do this.

Parameters

• startDate - date to start the calculation (inclusive)
• endDate - date to end the calculation (inclusive)
• targetMonth / targetYear - Month and year to limit the date range by.

We need to trim the date range down to a specific month because some leave events will span month boundaries. We need to be able to isolate leave requests on a per-month basis.

Examples:
Friday Dec 4 2015-Monday Dec 7 2015 => 2 working days
Monday Nov 30 2015-Friday Dec 4 2015 with month set to November => 1 working day
Monday Nov 30 2015-Friday Dec 4 2015 with month set to December => 4 working days

Will need to update service and ui to handle configurable date filters.

One of the current plans is to have a high-level heat map view of the year at a glance view (default view). Once the react calendar plugin has been pulled in, this should be a simple renderer that we can add to do this.

Currently the mock UI has summary information for each month. A service should be created that returns this summary information for a specific date range (inclusive). This will allow a user to drill down and get more specific data. This is needed for #1.

Should just be something rounding not correctly.

In the calendar summary view that is displayed when logging in, the calendars can still be moved. Flags have been passed to the react grid layout component to disable this, but for some reason they don't seem to be honored.

This should be investigated and corrected as we don't need these calendars to be movable.

The current UI only shows blank boxes. We need to use something nicer. James Davis started a react-calendar-render project ATS on GitHub.

This might not be needed just documenting it as an enhancement.

Currently the UI is only a mock UI. We need to modify UI to read from leave events stored in Mongo.

Requires mongo database to store custom
UI updates
New service endbpoint

Write method to determine unique users in a set of leave events in order to support #1.

Right now, the groups are actual lists of contact data. If 'all' is selected, the Google Contacts API is correctly queried and used to provide the list of users. Otherwise, the group data stored in JSON files is returned directly. This JSON data should only be used to map into and subset fresh Google Contacts data. Beyond that, this data should be db-driven so the project is applicable to other organizations outside of ATS that might like a tool such as this.

Currently the user list is stored in MongoDB. We need to pull the list of users from Google Apps and sync it with the Mongo DB.

If its friday its showing sat as the first day.

filter by text in title and summary, also filter by user.