A Django application to manage user Datebook
Django datebook is.. a datebook !
This aims to manage user datebooks by months. A datebook contain day entries where you can add details, start and stop working hours, vacation, etc..
This does not aims to reproduce some advanced apps like Google calendar or alike, datebook is simple and will have a particular workflow for our needs at Emencia.
Add it to your installed apps in settings :
INSTALLED_APPS = ( ... 'datebook', ... )
Finally mount its urls in your main urls.py :
urlpatterns = patterns('', ... (r'^datebook/', include('datebook.urls', namespace='datebook')), ... )
Datebooks are monthly so each datebook object represents a unique month for a specific year. And datebook contains day entries where you can fill start and stop time, eventually the pause time and some optional text content to describe day activities.
For day entries, start and stop time represents times for starting and ending work, they will determine the worked time for the day.
Pause time represents the time that was not worked between start/stop time and so will be substracted from the total worked time.
Overtime represents the extra time that is over the working hours, it does not affect the worked time.
Day entries can be marked as vacation, vacated days will never be used to calculate the total worked time for the month and their content is hided if any.
At least to access to datebook views, users have to be logged in, there is no anonymous access.
Basic users can see all datebooks and can read their day entries, but they can’t add or edit datebooks that they don’t own and quite naturally they can’t add/edit day entries only on their own datebooks.
For admin management there is some available permissions :
- ‘Can add datebook’ : used to create datebook for any user;
- ‘Can change datebook’ : used to edit datebook for any user;
- ‘Can add day entry’ : used to create day entries for any user’s datebook;
- ‘Can change day entry’ : used to change day entries for any user’s datebook;
Permission level object (like with django-guardian) is not planned because the goal is not to share datebook between users. Only datebook owner should edit its entry and all datebook are visible for any logged users, because a team should be aware of everyone datebooks.
Often you would need to repeatedly fill your days with the approximately same content and so to avoid this there is Day models.
You can create a Day model from an existing day in your calendars, its content will be saved as a model and then you can use it to fill any another days in your calendar.
You can have multiple models, but they are allways for an unique user, models are not shareable through other users.
To fill days with a model, just go into a month calendar, open the models menu, select the day to fill, select the model to use and submit, existing days will be overwrited with model contents and empty selected days will be created with the model contents.