Feature #3364
New communication tool: "Course wall"
0%
Description
The idea is that users subscribed to a course post messages in a "Course wall".
The same feature that exists in Facebook/Ohloh but for Chamilo courses.
We can also show there if there are new elements in the course like exercises, documents, announcements, etc.
Like a "history of the course".
Files
Related issues
History
Updated by
Updated by Julio Montoya over 7 years ago
Updated by - File notifications.png notifications.png added
I was thinking something more like this:
Updated by Marko Kastelic over 7 years ago
that's it. personally, i like redmine's activity view, or something like http://www.projectpier.org/files/u16/dashboard_overview.gif which is basically the same as journal above. .. and nothing like Moodle's default course home. Then, rss for thus wall would be welcome
Updated by Julio Montoya over 7 years ago
Updated by Juan Carlos Raña Trabado over 7 years ago
Updated by Veo esta funcionalidad más dentro de la red social que dentro de un curso.
Sorry Marco, in English: I see this functionality better in social network that inside a course
Updated by Marko Kastelic over 7 years ago
agree, single course does not need (another?) such tool, but in the session, specially when combined from several courses, can be useful; as for grouping (and organizing, maybe controlled by personal filter) info from several sources, that are relevant for students /teachers/
Updated by Juan Carlos Raña Trabado over 7 years ago
Good idea. Moreover, any user could have a wall where appeared what it do their friends (if they want ). Moreover, the network needed a place where each user can enter by way like microblog (if there is something similar within the network groups but not for one user); the user can write and comment and his friends too.
Updated by Julio Montoya over 7 years ago
- SCRUM pts - complexity changed from 40 to 100
Great ideas! So every "identity" should have a "wall": sessions, courses and users.
So the idea is for example if something is published in the course wall, the session's wall will be updated (if you want to). Well, there are a lot of conditions, validations, settings that we can add.
Here's my "easy" way to implement this feature (in a first version)
An "owner" of an "identity" publishes some "content". This "content" can be public or private for other users. Can be deleted but not modified.
The owners can add/delete their content:
Session => session admin / coaches
Course => teachers
User => user
Updated by Yannick Warnier about 6 years ago
Updated by 
- Target version set to 2.0
We've received requests (still waiting for validation) for this from several customers, but we should start small to avoid overwhelming users with too much information. Why not just start with the users "entity", then extend to other things?
There is quite a lot of room in the social network to place a block with the latest messages.
Updated by Julio Montoya almost 6 years ago
- Status changed from New to Needs more info
Yannick Warnier wrote:
We've received requests (still waiting for validation) for this from several customers, but we should start small to avoid overwhelming users with too much information. Why not just start with the users "entity", then extend to other things?
There is quite a lot of room in the social network to place a block with the latest messages.
I think that we need time to stabilize the code (due the recent changes) in order to integrate doctrine2, symfony components(form, session, request), tests (phpunit) into the core in order to have a more usable code ...
Updated by Yannick Warnier almost 6 years ago
Julio Montoya wrote:
I think that we need time to stabilize the code (due the recent changes) in order to integrate doctrine2, symfony components(form, session, request), tests (phpunit) into the core in order to have a more usable code ...
We might not have the opportunity to "wait" for that before developing this feature (I'm waiting for confirmation, but it might be necessary very shortly).
This being said, adding a "wall" is just adding a message type. There is no requirement to make any database change to add the feature.