Meta Configuration in DVID

NeuTu also relies on some configuration in the target DVID node to tune its behavior.

neutu_config

neutu_config is a keyvalue that stores the following keys:

user_status

It defines roles of some users. Currently it is mainly used for defining admin users:

{
  "admin": ["user1", "user2"]
}

body_status_v2

Its value is a JSON object that defines body statuses used by body annotation. The main field of the JSON object is "status" that maps to an array, in which each element is a JSON object that defines one status:

Schema for a status object
{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "type": "object",
  "properties": {
    "name": {
      "description": "name of the status",
      "type": "string"
    },
    "protection": {
      "description": "protection level",
      "type": "integer"
    },
    "priority": {
      "description": "status with higher priority overwrites the lower one in merging",
      "type": "integer"
    },
    "final": {
      "description": "final status, which cannot be changed by non-admin",
      "type": "boolean"
    },
    "admin_level": {
      "description": "0 means nothing special and 1 means it can only be added by admin",
      "type": "integer"
    }
  },
  "required": [
    "name"
  ]
}

Protection level:

0: can be added or changed by anyone

4-6 (obsolete): can only be added by admin, but changed by anyone. It is obsolete and should use "admin_level": 1 instead for this purpose.

7-8: can only be added or changed by admin

>=9: can only be changed

Last updated

Was this helpful?