Rex Dri issueshttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues2019-02-21T17:56:19Zhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/48Remove custom REST API behavior2019-02-21T17:56:19ZFlorent ChehabRemove custom REST API behaviorRemove the custom behavior of the REST API that returns an object instead of a list.
It was handy, but let's stay with the standard behavior.Remove the custom behavior of the REST API that returns an object instead of a list.
It was handy, but let's stay with the standard behavior.Pre start PRFlorent ChehabFlorent Chehabhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/44Switch from flake8 to Black2019-02-08T10:36:00ZFlorent ChehabSwitch from flake8 to BlackPre start PRhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/192Stats explorer2020-06-14T19:16:22ZFlorent ChehabStats explorerFollowup to #184
We are close to having the following data collected everyday on REX-DRI:
1. How many users connected to the plateforme, with a 24h granularity.
2. Information about exchange related contributions with a 24h granulari...Followup to #184
We are close to having the following data collected everyday on REX-DRI:
1. How many users connected to the plateforme, with a 24h granularity.
2. Information about exchange related contributions with a 24h granularity.
## Example data
Here is a preview how what the two tables might contain:
1. ex:
| *id* | date | nb_connections |
| ---- | ------------------------- | -------------- |
| 1 | 2020-05-01T00:00:00:0001Z | 5 |
| 2 | 2020-05-02T00:00:00:0001Z | 10 |
| 3 | 2020-05-03T00:00:00:0001Z | 3 |
2. ex:
| *id* | date | major | minor | exhange_semester | university | nb_contributions |
| ---- | ------------------------- | ----- | ----- | ---------------- | ---------- | ---------------- |
| 1 | 2020-05-01T00:00:00:0001Z | IM | CMI | P2020 | EPFL | 2 |
| 2 | 2020-05-01T00:00:00:0001Z | IM | MAT | A2020 | EPFL | 1 |
| 3 | 2020-05-03T00:00:00:0001Z | GI | FDD | A2020 | Tokyo | 1 |
*N.B. 'university' will actually be a foreign key to the univ model in the database.*
## Objectives
Those tables enable us to answer the following questions:
1. Questions:
* How many user connected to the site in the last 30 days?
* How many user connected to the site between date1 and date2?
* Can we plot the number of user that connected to site between date1 and date2?
* Etc.
2. Questions (here there are a lot of possibilities -- plus either count or plot):
* How many exchange related contributions between date1 and date2?
* What is the distribution of contributions between majors?
* ... between minors inside a major?
* etc. etc. etc.
## Technical feasibility
### Request
In the frontend, we want to:
* Be able to plot data or display it as a table,
* Be able to export tables as CSV,
* Be able to filter data,
* Be able to "groupby" data,
* Be able to combine the last two settings in whatever configuration,
* Be able to share a reproductible page (filter, groupby, etc.) only with a URL.
### Constraints
* There are a lot of filtering/groupby possibilities, our tool has to be generic enough to cover every possibility.
* The solution should be highly maintainable.
* We must have a strict control about what query is performed in the database.
* We can assume that the end user has some data wrangling knowledge.
* It should be implementable under ~2 weeks.
### Conclusion
How to do it?PR-P20Estelle VeisemburgerEstelle Veisemburgerhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/188Update back and front deps2020-05-17T11:29:19ZFlorent ChehabUpdate back and front deps* [ ] back deps
* [ ] front deps
Will need to rebuild docker images too.* [ ] back deps
* [ ] front deps
Will need to rebuild docker images too.PR-P20https://gitlab.utc.fr/rex-dri/rex-dri/-/issues/187Dramatically ease the process of adding missing destinations2020-05-31T12:39:13ZFlorent ChehabDramatically ease the process of adding missing destinations:warning: to be tackled after #137 !
In REX-DRI, there is a difference between a UTC university partner and a University (for REX-DRI).
This is because:
* There are duplicates in the UTC database,
* We want to add Metadata to the Unive...:warning: to be tackled after #137 !
In REX-DRI, there is a difference between a UTC university partner and a University (for REX-DRI).
This is because:
* There are duplicates in the UTC database,
* We want to add Metadata to the University (the location of their campus, etc.)
As a result we have the [`Partner` model](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/backend_app/models/partner.py) which is automatically filled.
And then, we need to either:
* Be able to link this partner to an existing university at REX-DRI,
* Create a new University at REX-DRI.
After #137 is tackled, it should be straightforward to do it. Document the process (using the django admin).
You might also want to update this view https://rex.dri.utc.fr/app/about/unlinked-partners/ to provide the id in the database to ease the process.PR-P20Maxime EmschwillerMaxime Emschwillerhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/184Add stats regarding feedback completion2020-06-14T13:25:19ZFlorent ChehabAdd stats regarding feedback completionCompute basics statistics (dayly) regarding what is the percentage of exchange with feedbacks, how many new feedbacks, etc.Compute basics statistics (dayly) regarding what is the percentage of exchange with feedbacks, how many new feedbacks, etc.PR-P20Maxime EmschwillerMaxime Emschwillerhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/177Filter: give more suggestions & merge IM, GSM, GM ?2020-05-24T18:53:21ZFlorent ChehabFilter: give more suggestions & merge IM, GSM, GM ?> Dans la recherche, si je commence à taper « IM » dans le filtre par branche, seules quelques filières apparaissent. Je ne trouve pas « IM-CMI ». Il faut taper CMI pour faire apparaître IM-CMI et GSM-CMI (nécessité de garder les deux ?)> Dans la recherche, si je commence à taper « IM » dans le filtre par branche, seules quelques filières apparaissent. Je ne trouve pas « IM-CMI ». Il faut taper CMI pour faire apparaître IM-CMI et GSM-CMI (nécessité de garder les deux ?)PR-P20Estelle VeisemburgerEstelle Veisemburgerhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/174Keep track of the latest contributions, add it to the front home page.2020-06-07T12:26:23ZFlorent ChehabKeep track of the latest contributions, add it to the front home page.* Track the latest contributions to the website (in the backend),
* On the front page, display something like:
```
Dernières contributions
---
Le 20/04 : Université ...
Université ...
Le 19/04: Toto ...
```
Or something ...* Track the latest contributions to the website (in the backend),
* On the front page, display something like:
```
Dernières contributions
---
Le 20/04 : Université ...
Université ...
Le 19/04: Toto ...
```
Or something else.
The main point here is to show how lively the website is.PR-P20Gautier DauresGautier Daureshttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/153Investigate missing Gzip compression in Prod2020-04-22T18:52:25ZFlorent ChehabInvestigate missing Gzip compression in ProdGzip compression seems to be disable in prod (Json and statics are not gziped)Gzip compression seems to be disable in prod (Json and statics are not gziped)PR-P20https://gitlab.utc.fr/rex-dri/rex-dri/-/issues/149Last visited universities2020-06-07T12:16:19ZFlorent ChehabLast visited universitieshttps://gitlab.utc.fr/rex-dri/rex-dri/issues/149
Backend:
1. Create an intermediate model (LastVisitedUniversity) between the user and university models
* This model contains 3 fields : one for user (foreign key) , one for universi...https://gitlab.utc.fr/rex-dri/rex-dri/issues/149
Backend:
1. Create an intermediate model (LastVisitedUniversity) between the user and university models
* This model contains 3 fields : one for user (foreign key) , one for university (foreign key) and one for lastClickOnUniversity (DateTimeField: auto_now = True)
2. Create a viewset to update the previous model when a user looks at a university (get inspired by https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/backend_app/viewsets.py#L316).
Endpoint: /lastVisitedUniversities
req POST endpoint/<pk_univ> => Create LastVisitedUniversity(user=req.user, university=University.get(pk=<pk_univ>), ~~ts=now()~~)
req GET endpoint => return List[LastVisitedUniversity.where(user=req.user).orderby(ts DESC).first(5)] (list[int] === List[<pk_univ>])
SQL:
```sql
SELECT university, max(ts) as ts
FROM LastVisitedUniversity
WHERE
USER = <req.user.pk>
GROUP BY university
ORDER BY ts DESC
LIMIT 5;
```
other => Return 404
Frontend:
1. When visiting university: make POST request (https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/frontend/src/components/recommendation/view/View.jsx#L676 use the useApiCreate() hook)
2. Create component to show last visited univ (and mention REX-DRI private)
PR-P20Imane MisrarImane Misrarhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/148Filter only on currently available destinations2020-05-17T15:54:44ZFlorent ChehabFilter only on currently available destinations## Objective
* Being able to filter only on open destinations, [on the map and search pages (it's the same component)](https://rex.dri.utc.fr/app/map/)
## Context
### Back
* Every night, the UTC DRI data are copied from the DSI to RE...## Objective
* Being able to filter only on open destinations, [on the map and search pages (it's the same component)](https://rex.dri.utc.fr/app/map/)
## Context
### Back
* Every night, the UTC DRI data are copied from the DSI to REX-DRI [source](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/cron_tasks.py#L38)
* You should be able to plug yourself in the [`__import_opened_destinations` method](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/external_data/management/commands/utils.py#L199) and the [`update` method](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/external_data/management/commands/utils.py#L76), to track which partners are "open" on the UTC ENT.
* You should also know (and maybe use -- it's up to you) that some denormalized data is updated every night on the [`University` model](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/backend/backend_app/models/university.py#L72). This is the data that is used for filtering.
### Front
* The filter Component is [here][https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/frontend/src/components/filter/Filter.jsx)
* The filtering itself is handled within the [`FilteringService` class](https://gitlab.utc.fr/rex-dri/rex-dri/-/blob/dev/frontend/src/services/FilterService.js)
Have fun :tada:
Bonus point if you throw some [transaction](https://docs.djangoproject.com/fr/2.2/topics/db/transactions/#controlling-transactions-explicitly) somewhere :rolling_eyes: PR-P20Imane MisrarImane Misrarhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/138Add reminder to contribute for previous exchanges2020-05-06T18:57:09ZFlorent ChehabAdd reminder to contribute for previous exchanges**We should do our best to encourage students to contribute to the platform.**
Under the following constraints:
* There is no way for us to know for sure that a student has contributed for each of his or her real exchanges.
* We only kn...**We should do our best to encourage students to contribute to the platform.**
Under the following constraints:
* There is no way for us to know for sure that a student has contributed for each of his or her real exchanges.
* We only know about the student exchanges that he or she has given authorization to the DSI to share with REX-DRI.
So creating a smart / deterministic reminder might be too complicated.
*Sending reminder by emails, is out of the scope of this project.*
One possibility would be recurring notification, that show up once every few weeks / months after the last time the person has clicked on the popup.
PR-P20https://gitlab.utc.fr/rex-dri/rex-dri/-/issues/137Drop the city and campus model to simplify things a bit2020-06-19T14:20:56ZFlorent ChehabDrop the city and campus model to simplify things a bitAs you can see here https://rex-dri.gitlab.utc.fr/rex-dri/documentation/generated/architecture.svg the backend models architecture is a bit complicated.
To simplify things a bit, we want to:
* [ ] Drop the city model
* [ ] Drop the c...As you can see here https://rex-dri.gitlab.utc.fr/rex-dri/documentation/generated/architecture.svg the backend models architecture is a bit complicated.
To simplify things a bit, we want to:
* [ ] Drop the city model
* [ ] Drop the campus model
* [ ] All these information should be moved back to the `University`.
* [ ] There are also big changes to perform to the frontend.
This will be a big help for #187
How to do it?
1. Create a migration to add the missing columns to the University model,
2. Create a script to transfer the data from the city / campus models in the new columns,
-----
3. Update the backend serializers and viewsets,
5. Update the frontend.
-----
4. Delete the old models.PR-P20Gautier DauresGautier Daureshttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/132Drop camel case from endpoints routes2020-03-21T17:41:31ZFlorent ChehabDrop camel case from endpoints routesswitxh to dash caseswitxh to dash casePR-P20https://gitlab.utc.fr/rex-dri/rex-dri/-/issues/119Check on_delete values in models2019-07-01T18:42:30ZFlorent ChehabCheck on_delete values in modelsBefore going in productionhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/118Check allowed HTTP method allowed on the API2019-05-25T13:22:57ZFlorent ChehabCheck allowed HTTP method allowed on the APIAllow only GET, POST, PUT and DELETE.Allow only GET, POST, PUT and DELETE.Before going in productionFlorent ChehabFlorent Chehabhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/96Review permissions on viewsets2019-07-01T18:42:30ZFlorent ChehabReview permissions on viewsetsDo this before going to prod.Do this before going to prod.Before going in productionhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/34Recommendation list2019-06-22T12:03:38ZFlorent ChehabRecommendation listEnable the user to create list of universities.
:warning: The backend architecture might need an update. I would highly recommend starting by building the frontend for this. :warning:
- A user can create multiple lists of universities...Enable the user to create list of universities.
:warning: The backend architecture might need an update. I would highly recommend starting by building the frontend for this. :warning:
- A user can create multiple lists of universities,
- Each list can contain each university at most once,
- For each university, the user can add a markdown comment and "grades" (to determine),
- Users can reorder the list,
- Users can add "block" of markdown comment.
- The list can either be private or public (shareable -> useful for teachers). Therefore, some backend checks will be needed to verify that a user as read access to the list.
You can think of a list as something close to a Jupyter Notebook with "university blocks" and "comment blocks".PR nowSolene AboudSolene Aboudhttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/33Take account language from courses when filtering.2019-06-02T18:50:19ZFlorent ChehabTake account language from courses when filtering.#31 #32
To ease the computation, think of it as a data warehouse: don't recompute it on the backend everytime but store the information in the university model too. Update it when a course is added.
Run a full update once every day to ...#31 #32
To ease the computation, think of it as a data warehouse: don't recompute it on the backend everytime but store the information in the university model too. Update it when a course is added.
Run a full update once every day to make sure the data is coherent. (see #28 )PR nexthttps://gitlab.utc.fr/rex-dri/rex-dri/-/issues/32Ask the student to give the information of the course language when evaluating2019-06-27T20:03:58ZFlorent ChehabAsk the student to give the information of the course language when evaluatingAllow up to two languages per course (one might be null).
Following #29
This information might be used to search universities by teaching language at some point.
Linked to #116
Allow up to two languages per course (one might be null).
Following #29
This information might be used to search universities by teaching language at some point.
Linked to #116
PR nextSegolene BrisemeurSegolene Brisemeur