General Roadmap Summary #13
Description
Activities Calendars
The Calendar of the Lessions and of other activities is the primary and most urgent feature to implement. These activities that are fundamentally calendars entry with a date, a start time and a end time, share unique the resources they use: Teachers, Recipients, Classrooms. The resource are unique, so that a Recipient or a Teacher or a Classroom CANNOT be assigned to another calendar entry that have the same date and time. This constraint is fundamental and mandatory.
The calendar management must have a smart import/input system for Lessions date so that:
- importing existing lession dates (of the same Course) will update instead of add as new
- inserting manually or importing with the import function will check if the resorces (Recipients, Teachers and Classrooms) are already occupied for that date and time.
Also the user can create and manage Classrooms where the activities are carried out.
Another functionality for the user is to generate valid course Lession dates, given the teacher and the total hours of that Course.
Furthermore an export function that exports in an excel file template the calendar of one given Course.
Task
- calendar mandatory "fields":
- date
- start time
- end time
- teacher
- recipients
- classroom
- every lession refers to:
- a course
- a project
Every lession must not overlap for the same date/time the following resources (fields):
- teacher
- recipients
- classroom
Projects
The Project is the top level container of all the entities. With a kanban column view, the user is able to manage the details of each Project like the following:
- deadlines dates with Alerts calculated with the Call rules
- fund and Call assignment
- general details (title, project code, partners, project applicant, recipients, etc)
- economic details (budgets, down-payments, etc)
- activities details summary, like a list of Courses and the total sum of the hours of all the Courses
- file attachments
- phases of execution:
- draft: the project is still to be submitted to the fund;
- submitted: the project details has been decided, it now can have a submission date
- active: the project submission has been accepted, it now can have a start date
- completed: all the course activities hours have been done, so that the sum of all the hours of each course are equal to the amount specified in the draft phase. The completion date can have a deferral over the default calculated date, that is given by the Call rules, defined at creation time
- accounted: the project can now have an "accounted" date record, also other Attachments will be added in this phase
- closed: the project is officially closed and not editable
Task
Create the general details of a project:
- title
- project code (user given)
- total financing amount of the project (user given)
- total course lesson hours (user given)
- submission date
- admittance date
- partner list
- courses list
Contacts
It has to render as a kanban that contain the persons (so Students, Teachers and Operators) and the Companies (these can be project partners or project applicants).
Other than the single entity general details, the contact dialog has to show in which Projects one contact has been involved.
Also it has to include individual views smart enchancements, like "validity" for the person Contact Identification N., or specific attachment fields for Companies, like statements and other official documents, all of these based on the type of the contact.
Students Teachers Operators
A Contact can be either a Student, a Teacher or a Operator, these roles are not exclusive. It must have:
- General individual details: name, residency address, birth date, birthplace
- Job details: employment status, related company
- if he/she is a teacher, topics of teaching that he/she can deliver
- if he/she is an operator, the list of the assigned projects and the sum of the hours done as operator in that project
- if he/she is a student, the list of the project courses attended
- an attachment section with all the related documents
Companies
A company may have the same details as company in the res.partner Odoo standard. It must have:
- an attachment section with all the related documents
- the list of the project it has been involved, like partner of like applicant
Attachments
Entities can have Attachments that other than the file must have
- a proper description
- a category
- a validity date
- and the file attachment
The chosen entities to have Attachments are: - Projects
- Contacts
- Courses
- Classrooms
Alerts
Users must have an "alert system" that shows the deadlines of all the active projects.
This could be a dashboard or a notification system.
It must shows if these deadlines are distant in time or approacing near. The deadlines are calculated based on what fund call a Project is assigned, so it's the Call that have the rules for the deadlines. The Call rules are always specified by the user.
The deadlines are:
- complete project deadline: it's the date within a certain amout (in %) of the project courses hours must be done. In details this means that the nn% of course hours (as specified in the Call) of the project must be done before this date, that is calculated by adding X days (as specified in the Call) to the project start date (specified by the user in the project details) PLUS a given specified deferral (also specified by the user).
- down-payment requests: depending on which Call is a project, there can be a deadline to submit each down-payment request. These request deadlines are calculated in days from the project start date.