Contact person: Business Client

Phone:Show

Email:Show

Location: Casablanca, Morocco

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Please first analyze my request and give me a correct bid, as my budget is limited, before we can move on. This is so I can see if we can provide that or not. If you have any more questions, please private message me.

1. Let's say we have only one user with an account, and let's call it "owner" for example for now. He is the only one allowed to control the app.

2. Let's assume too that we have many professors all over the country or the world. Their lessons are, in most cases, static (meaning the planning almost doesn't change once the data of the locations where they will be and when it will start is set). Example of the data structure:
* Prof1: Monday: PlaceA (regionName must be in the database but will not be shown here): After 5pm, Tuesday: off, etc., Sunday: PlaceZ: After 6pm, etc.
* Prof2: Monday: PlaceZ: After 6pm, Tuesday: PlaceR: After 5pm, etc.
* etc.

3. So, an option that allows us to manage the professors must, of course, be available.

4. A button in each professor's profile must be available which allows the owner to disable the current program planning without deleting it from the database at any time. So if people visit that profile, they will see that the professor is absent until he activates it again. The owner can enable it too whenever we want, of course, which will allow everyone to see again that he is back, with the program not changed, of course.

5. When this button is disabled, we must show two date-time zones that will allow us to pick from when to when this professor will be absent (for a vacation or any other reasons which we don't care about).

6. So, if the button is disabled while the re-enabling time was set (using option 5), then the program must stay the same and be shown to anyone who visits its profile, but with "off" instead of the program for all the periods in which he will not be there. Otherwise (using option 4 only without specifying a returning period), the whole program must be shown in gray with a notification for the users that says that the prof will be absent for an unknown period.

7. So, of course, if I, as the owner, go to a profile, I will be able to update it, while the other visitors will see it without being able to update anything.

8. A button that allows me to enable or disable each day's program for each professor must also be available (in case I want to disable only one course for one prof for a reason like sickness that doesn't matter also).

9. The profile will look like this:
* A profile picture around in the middle.
* Name of the prof under the picture
* Program: (this in the left and flexed with we will have in the right Present/Absent (this is the same button from option 4 and 5; as mentioned, we can update as owners directly from this page).
* Monday: PlaceA: After 5pm
* HERE BELOW WILL BE THE MAP that must link the location mentioned after "monday :". By default here, so people can see them on the map (this must be set and configured automatically when we set the location as owner). BUT, this map will not load before you click on the previous line (monday : PlaceA : After 5pm) to use fewer resources while loading that page, you know.
* Present)Absent (in the right)
* Tuesday: off
* etc.,
* Sunday: PlaceZ: After 6pm,
* HERE BELOW WILL BE THE MAP that must link the location mentioned after "sunday"...
* Present/Absent

10. The index page will show the list of all profs with the possibility of filtering by city or region with today's programs, like this:
* Prof1: PlaceZ: After 6pm,
* Prof2: PlaceA: After 5pm,
* etc.
If you click on a location, then the map is loaded under the prof name to see where the location of the course is. But if you click on the prof name, then it will send you to its profile mentioned before in point '9'.

OF COURSE, I don't think I have to mention that each location used will be stored once in the database in a separate locations table with an id column and the location names. We don't have to set them again and again each time we want to link a prof with a location. (Do the same for time and other options)." (client-provided description)