Due to a recent issue found with the scraper, there are some course units shared between 2 or more courses that do not appear on one of those courses.
There are ways to circumvent this (like selecting course units from a different course) but this is not ideal. Furthermore, users have no way of knowing when that is the case or if those issues apply to their specific case.
This issue proposes adding a way for system administrators to issue warnings that should be shown to users when they use the platform. These warnings could inform users of cases like the one depicted above.
Regarding implementation details, this issue needs to be separated between frontend and backend development since there is no direct way for us (NIAEFEUP) to issue those warnings directly to the users' browser clients.
For the backend portion of this issue, we could accept WebSocket connections from frontend clients through which we send the warnings that are supposed to appear. After this, we could open a Unix socket through which we (NIAEFEUP) send the warnings that are supposed to be sent to clients. There should be some sort of way for warnings generated prior to a client connecting to be sent eitherway. This requires more thorough discussion. For generating warnings, a new custom made tool could be made in order to aid in this.
Due to a recent issue found with the scraper, there are some course units shared between 2 or more courses that do not appear on one of those courses.
There are ways to circumvent this (like selecting course units from a different course) but this is not ideal. Furthermore, users have no way of knowing when that is the case or if those issues apply to their specific case.
This issue proposes adding a way for system administrators to issue warnings that should be shown to users when they use the platform. These warnings could inform users of cases like the one depicted above.
Regarding implementation details, this issue needs to be separated between frontend and backend development since there is no direct way for us (NIAEFEUP) to issue those warnings directly to the users' browser clients. For the backend portion of this issue, we could accept WebSocket connections from frontend clients through which we send the warnings that are supposed to appear. After this, we could open a Unix socket through which we (NIAEFEUP) send the warnings that are supposed to be sent to clients. There should be some sort of way for warnings generated prior to a client connecting to be sent eitherway. This requires more thorough discussion. For generating warnings, a new custom made tool could be made in order to aid in this.