django-notifications Documentation

django-notifications is a GitHub notification alike app for Django, it was derived from django-activity-stream

The major difference between django-notifications and django-activity-stream:

• django-notifications is for building something like Github "Notifications"
• While django-activity-stream is for building Github "News Feed"

Notifications are actually actions events, which are categorized by four main components.

• Actor. The object that performed the activity.
• Verb. The verb phrase that identifies the action of the activity.
• Action Object. (Optional) The object linked to the action itself.
• Target. (Optional) The object to which the activity was performed.

Actor, Action Object and Target are GenericForeignKeys to any arbitrary Django object. An action is a description of an action that was performed (Verb) at some instant in time by some Actor on some optional Target that results in an Action Object getting created/updated/deleted.

For example: justquick (actor) closed (verb) issue 2 (object) on activity-stream (target) 12 hours ago

Nomenclature of this specification is based on the Activity Streams Spec: http://activitystrea.ms/specs/atom/1.0/

Installation

Installation is easy using pip and will install all required libraries.

$ pip install django-notifications-hq

or get it from source

$ git clone https://github.com/django-notifications/django-notifications
$ cd django-notifications
$ python setup.py install

Note that django-model-utils will be installed: this is required for the pass-through QuerySet manager.

Then to add the Django Notifications to your project add the app notifications to your INSTALLED_APPS and urlconf.

The app should go somewhere after all the apps that are going to be generating notifications like django.contrib.auth:

INSTALLED_APPS = (
    'django.contrib.auth',
    ...
    'notifications',
    ...
)

Add the notifications urls to your urlconf:

import notifications

urlpatterns = patterns('',
    ...
    url('^inbox/notifications/', include(notifications.urls)),
    ...
)

The method of installing these urls, importing rather than using 'notifications.urls', is required to ensure that the urls are installed in the notifications namespace.

How to migrate schema

For Django 1.4~1.6

django-south support is shipped with django-notifications.

1. Install latest version (>=1.0) django-south
2. Execute manage.py migrate notifications to migrate django-notifications schema

Note: If you use a custom user model in your application, you may want to check reverse dependencies of South to run your migrations in the correct order.

For Django 1.7

Django 1.7 has built-in support for migrations. No need to install django-south.

1. Execute manage.py migrate notifications

Generating Notifications

Generating notifications is probably best done in a separate signal.

from django.db.models.signals import post_save
from notifications import notify
from myapp.models import MyModel

def my_handler(sender, instance, created, **kwargs):
    notify.send(instance, verb='was saved')

post_save.connect(my_handler, sender=MyModel)

To generate an notification anywhere in your code, simply import the notify signal and send it with your actor, recipient, verb, and target.

from notifications import notify

notify.send(user, recipient=user, verb='you reached level 10')

notify.send(comment.user, recipient=user, verb=u'replied', action_object=comment,
            description=comment.comment, target=comment.content_object)

notify.send(follow_instance.user, recipient=follow_instance.follow_object, verb=u'has followed you',
            action_object=instance, description=u'', target=follow_instance.follow_object, level='success')

Extra data

You can attach arbitrary data to your notifications by doing the following:

• Add to your settings.py: NOTIFICATIONS_USE_JSONFIELD=True

Then, any extra arguments you pass to notify.send(...) will be attached to the .data attribute of the notification object. These will be serialised using the JSONField's serialiser, so you may need to take that into account: using only objects that will be serialised is a good idea.

Soft delete

By default, delete/(?P<slug>\d+)/ deletes specified notification record from DB. You can change this behaviour to "mark Notification.deleted field as True" by:

• Add to your settings.py: NOTIFICATIONS_SOFT_DELETE=True

With this option, QuerySet methods unread and read contain one more filter: deleted=False. Meanwhile, QuerySet methods deleted, active, mark_all_as_deleted, mark_all_as_active are turned on. See more details in QuerySet methods section.

API

QuerySet methods

Using django-model-utils, we get the ability to add queryset methods to not only the manager, but to all querysets that will be used, including related objects. This enables us to do things like:

Notification.objects.unread()

which returns all unread notifications. To do this for a single user, we can do:

user = User.objects.get(pk=pk)
user.notifications.unread()

There are some other QuerySet methods, too.

qs.unread()

Return all of the unread notifications, filtering the current queryset. When NOTIFICATIONS_SOFT_DELETE=True, this filter contains deleted=False.

qs.read()

Return all of the read notifications, filtering the current queryset. When NOTIFICATIONS_SOFT_DELETE=True, this filter contains deleted=False.

qs.mark_all_as_read() | qs.mark_all_as_read(recipient)

Mark all of the unread notifications in the queryset (optionally also filtered by recipient) as read.

qs.mark_all_as_unread() | qs.mark_all_as_unread(recipient)

Mark all of the read notifications in the queryset (optionally also filtered by recipient) as unread.

qs.deleted()

Return all notifications that have deleted=True, filtering the current queryset. Must be used with NOTIFICATIONS_SOFT_DELETE=True.

qs.active()

Return all notifications that have deleted=False, filtering the current queryset. Must be used with NOTIFICATIONS_SOFT_DELETE=True.

qs.mark_all_as_deleted() | qs.mark_all_as_deleted(recipient)

Mark all notifications in the queryset (optionally also filtered by recipient) as deleted=True. Must be used with NOTIFICATIONS_SOFT_DELETE=True.

qs.mark_all_as_active() | qs.mark_all_as_active(recipient)

Mark all notifications in the queryset (optionally also filtered by recipient) as deleted=False. Must be used with NOTIFICATIONS_SOFT_DELETE=True.

Model methods

obj.timesince([datetime])

A wrapper for Django's timesince function.

obj.mark_as_read()

Mark the current object as read.

Template tags

Put {% load notifications_tags %} in the template before you actually use notification tags.

notifications_unread

{% notifications_unread %}

Give the number of unread notifications for a user, or nothing (an empty string) for an anonymous user.

Storing the count in a variable for further processing is advised, such as:

{% notifications_unread as unread_count %}
...
{% if unread_count %}
    You have <strong>{{ unread_count }}</strong> unread notifications.
{% endif %}

Live-updater API

To ensure users always have the most up-to-date notfications, django-notifications includes a simple javascript API for updating specific fields within a django template.

There are two possible API calls that can be made:

1. api/unread_count/ that returns a javascript object with 1 key: unread_count eg:

   {"unread_count":1}
   

2. api/unread_list/ that returns a javascript object with 2 keys: unread_count and unread_list eg:

   {
    "unread_count":1,
    "unread_list":[--list of json representations of notifications--]
   }
   

   Representations of notifications are based on the django method: model_to_dict

How to use:

1. Put {% load notifications_tags %} in the template before you actually use notification tags.

2. In the area where you are loading javascript resources add the following tags in the order below:

   <script src="{% static 'notifications/notify.js' %}" type="text/javascript"></script>
   {% register_notify_callbacks callbacks='fill_notification_list,fill_notification_badge' %}
   

register_notify_callbacks takes the following arguments:

1. badge_id (default live_notify_badge) - The id attribute of the element to show the unread count, that will be periodically updated.
2. menu_id (default live_notify_list) - The id attribute of the element to insert a list of unread items, that will be periodically updated.
3. refresh_period (default 15) - How often to fetch unread items from the server (integer in seconds).
4. callbacks (default <empty string>) - A comma-separated list of javascript functions to call each period.
5. api_url_name (default list) - The name of the API to call (this can be either list or count).

3. To insert a live-updating unread count, use the following template:

   {% live_notify_badge %}
   

live_notify_badge takes the following arguments:

1. badge_id (default live_notify_badge) - The id attribute for the <span> element that will be created to show the unread count.
2. classes (default <empty string>) - A string used to populate the class attribute of the above element.

4. To insert a live-updating unread count, use the following template:

   {% live_notify_list %}
   

live_notify_list takes the following arguments:

1. list_id (default live_notify_list) - The id attribute for the <ul> element that will be created to insert the list of notifications into.
2. classes (default <empty string>) - A string used to populate the class attribute of the above element.

Using the live-updater with bootstrap

The Live-updater can be incorporated into bootstrap with minimal code.

To create a live-updating bootstrap badge containing the unread count, simply use the template tag:

{% live_notify_badge classes="badge" %}

To create a live-updating bootstrap dropdown menu containing a selection of recent unread notifications, simply use the template tag:

{% live_notify_list classes="dropdown-menu" %}

Customising the display of notifications using javascript callbacks

While the live notifier for unread counts should suit most use cases, users may wish to alter how unread notifications are shown.

The callbacks argument of the register_notify_callbacks dictates which javascript functions are called when the unread api call is made.

To add a custom javascript callback, simply add this to the list, like so:

{% register_notify_callbacks callbacks='fill_notification_badge,my_special_notification_callback' %}

The above would cause the callback to update the unread count badge, and would call the custom function my_special_notification_callback. All callback functions are passed a single argument by convention called data, which contains the entire result from the API.

For example, the below function would get the recent list of unread messages and log them to the console:

function my_special_notification_callback(data) {
    for (var i=0; i < data.unread_list.length; i++) {
        msg = data.unread_list[i];
        console.log(msg);
    }
}

django-notifications Team

Core contributors (in alphabetical order):

• Samuel Spencer
• Yang Yubo
• Zhongyuan Zhang