Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Rex Dri Rex Dri
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Rappel : l'instance GitLab de l'UTC n'est pas destinée au stockage de fichiers volumineux (images/vidéos/documents). Pensez également à ne pas pousser avec votre code les dépendances ou résultats des builds/exécutions (préférer la génération d'artifacts par la CI). Merci.

  • Rex Dri
  • Rex DriRex Dri
  • Issues
  • #29
Closed
Open
Issue created Jan 22, 2019 by Florent Chehab@chehabflOwner

Handle feedback on courses.

Backend

⚠ Review/update the backend structure for this matter. ⚠

Currently we have the following architecture:

Screenshot_from_2019-02-24_21-27-57

Several notes:

  • One possible design to do (or not to do) is to create a model that contains the feedback for one course and that is link to an exchange.
    • If you do so don't forget to modify your queryset to prefetch all the feedback (ask @chehabfl) for better performances.
    • If you do so, you can put the general feedback of the user on the exchange model (aka PreviousDeparture)
  • The other possibility, is to stick to JSON, but I think the one above is better to start with.

You have to keep in mind that:

  • The courses followed by a student will automatically created (and updated) given the data from the UTC database.

Some questions have to be resolved for this issue:

  • What do you grade on each course (for now: adequation and quality; I don't recall why I chose "integration")
  • #59 (closed)

Of course, don't forget about security:

  • the info should be readable by everyone, but editable only by the user (and eventually a moderator (and above level)).
  • For now, you can use a versioned model (that will automatically compress the successive version by the user, but will allow to keep track if an admin modify something).

Frontend

Well, then you need to build the front for this.

First display information, then add the possibility to edit. You might want to wait for #51 (closed) to be fixed first, but that's not necessary.

Edited Feb 24, 2019 by Florent Chehab
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking