Feature Wiki

Information about planned and released features

Tabs

Blog RSS Feed and Notification

1 Description

It should be possible
  • to get notifications about new postings in a monitored blog (implemented already for 4.2)
  • to subscribe to an ILIAS blog via RSS and read the postings without being inside ILIAS.

2 Status

3 Additional Information

  • If you want to know more about this feature, its implementation or funding, please contact: ilias(at)phtg.ch or Klaus Vorkauf / vorkauf (at) rus.uni-stuttgart.de

4 Discussion

Alex 25 Oct 2011: The HS Bremen starts to use the feature and also realized, that a notification feature is missing. There scenarios include students working on blogs, without using exercises assignments. Besides RSS feeds, mail notifications would also be desirable for
  • New and changed blog postings and
  • New comments
I think mail notification and RSS feed are not interchangable, means they work different and both options are needed.
 
@Matthias: We have to decide whether these features are new features (4.3) or if they are that important that they can be considered being usability fixes (4.2).

jluetzen 26 Oct 2011: Notifications for blog postings and comments are implemented for 4.2.1.

Matthias Kunkel, 06 Nov 2011: Notifications about new blog postings are very helpful, but ...
  • In the current implementation a notification is sent after adding the first text paragraph (adding only a posting is ignored). This means, other users are already notified when the user is still writing the posting. This could cause misunderstandings because the message of the entire posting is not readable.
  • Possible solution: The postings writer has to define a posting as "final" (or "publish") to trigger the notification. Before a posting has not been set final it is only visible for the writer itself (draft status).

JF 7 Nov 2011: The Page Service "Activation" feature should be used to implement the "Draft"/"Final" setting - and must be extended to use different texts for the actions links. An ilUtil info message should appear, when the status is "draft" that explains the user to click the action/final item to publish the posting. The side block of all postings should be extended: for all draft items a "Draft" text should be added (write permission). Draft items should not appear for users with read permission only. Notifications should be sent, when the status us set to final.

ILIAS_LM, 2017-09-06:
As we don't have the option to activate RSS in blogs, I missed something in the administration, I guess. What do I have to activate there? I've seen the option on https://www.ilias.de/test52. So I know where it should be in the blog's settings.

2017-09-08 Mela, Alix [ILIAS_LM]
Thanks to Ulrike Wilkens I found the setting. It's not the "News and Webfeeds" section, but in main administration  "Anonymous Access"  > "Enable User Content Publishing"
I didn't expect it there because it says "If enabled, users can publish their profiles, workspace objects and portfolios on the Web.". So this doesn't seem to affect blogs in repository, only in workspace.

I'll add some pictures for the next clueless person...

5 Implementation

JL 31 Aug 2012: RSS feeds are optionally available. The rest (notifications, draft/publish) has already been implemented for 4.2.

If this is activated, the rss-settings in the blog itself appear

6 Follow up

Ulrike Wilkens, 2nd Oct 2012:
 
I’d propose to augment the notification solution for blog entries a little bit.
 
It is now implemented in the following way (I guess…):
Users, who activated the blog-notification, get a mail, immediately after the status of an entry has been changed from “draft” to “published”.
Changes in “draft”-entries do not trigger the mail-sending routine.
Authors should set the status of an existing entry to “draft” in order to correct the text or make additions
 
This works well for attentive, thoughtful, concentrated…authors.
But: Authors (like me...), who sometimes forget to set an entry back to “draft” before editing, mass-produce (spam-)mails with every “save text”-operation through the editing process.
So I’d propose to implement the  „3-hour-break“-solution for notification for blogs (in the way  as it is implemented for the wiki notification.)
 
Please let me know arguments, which contradict this to be a better solution than the status quo.

Last edited: 17. Apr 2025, 15:05, Kunkel, Matthias [mkunkel]