Open source cms for mobile and desktop websites

nive_datastore application

Nive Datastore example

The Nive DataStore is a highlevel storage with a focus on build in functional extensions like form renderer, workflow integration, hierarchical data structures, flexible renderer and a web api.

Sqllite or Mysql are used as data backend so the goal is not replace database systems but to provide a flexible, easy and convenient way to store data items.

Database connection and basic datastore application configuration

from nive.definitions import AppConf, DatabaseConf

app = AppConf("",
              id = "storage",
              title = "My Data Storage",
              maxStoreItems = 20,
              maxBatchNumber = 100,
              search = {"default": {
                           "type": "bookmark", 
                           "container": False,
                           "fields": ["id", "link", "comment", "pool_changedby"],
                           "parameter": {"share": True}
              subtree = {"default": {
                             "levels": 0,              # the number of levels to include, 0=include all
                             "descent": (IContainer,), # item types or interfaces to descent into subtree
                             "fields": {},             # if empty uses type definition toJson defaults
                             "parameter": {"pool_state": 1}
              defaultSubtree = "all"
dbConfiguration = DatabaseConf(


Item data field definitions are registered as typed collections. Each collection has a unique type id, a custom set of data fields and many other options. Use nive.definitions.ObjectConf as configuration class to define a new collection.

A simple example. Stores a bookmark and comment:

bookmark = ObjectConf(
    id = "bookmark",
    name = _(u"Bookmarks"),
    dbparam = "bookmarks",
    data = (
      FieldConf(id="link",     datatype="url",  size=500,   default=u"",  name=u"Link url"),
      FieldConf(id="share",    datatype="bool", size=2,     default=False,name=u"Share link"),
      FieldConf(id="comment",  datatype="text", size=50000, default=u"",  name=u"Comment")
    forms = {
      "newItem": {"fields": ("link", "share", "comment") }, 
      "setItem": {"fields": ("link", "share", "comment") }
    toJson = ("link", "share", "comment", "id", "pool_create", "pool_change"),
    template = "",
app.modules.append(bookmark)  # app is the AppConf() defined in the previous example 

Groups and permissions

configuration.acl and configuration.groups

Permissions: read, search, add, edit, delete, webform, tojson, toxml, render, action

Groups: group:reader, group:manager, group:admin

By default groups and permissions are set up to reflect simple content management workflows with four different roles. Groups can be used for both: view permissions and workflow execution.

The data storage has no workflow activated by default. So by reassigning permissions in configuration.acl the predefined groups can simply be customized.


The systems provides a build in form renderer. Form configurations are included in the collection definition (configuration.form) and support by default create and edit modes.


Workflow processes can be added to the system to build a event system or extend the functionality. You can define and use multiple workflow processes and assign a process to an item as needed (or define defaults). A workflow process is organized in states and transitions. A transition can take one or multiple callbacks to be executed with the transition.

By default the workflow is disabled. See nive.definitions.AppConf.workflowEnabled and nive.definitions.ObjectConf.workflowID

Meta data

The system automatically tracks create and change information in a shared meta table (shared by all items). This table also stores the items globally unique id. To define database fields used for all collections use nive.definitions.AppConf.meta.


the main cms application class

© 2013 Nive GmbH