Meeting Collection

Contents

Meeting Collection#

As described in Meetings Overview, meetings can be grouped in folders of documentClass == NF_MeetingCollection.

The full datastructure of such a folder is given below:

Attribute Name

Attribute Type

Comments

id

String

The globally Unique ID of the object

documentClass

String

“NF_MeetingCollection”

type

String

“collection”

version

String

Current version of the object

path

String

Path of the object, starting with

downloadProhibited

Boolean

true / false

title

String

Title of the object

name

String

Name of the object

creationDate

DateTime

Creation Date of the Object, HWDateTimeFormat

modificationDate

DateTime

Modification Date of the Object, HWDateTimeFormat

author

String

Author of the object

writeAccess

Boolean

Whether this user has write access (true) or not (false)

subDocs

String(int)

Int as string, usually “0”

Example#

{
    "type": "collection",
    "id": "ID-29855.6518164830335-1",
    "path": "/imdatag/meetings/Aufsichtsrat",
    "documentClass": "NF_MeetingCollection",
    "version": "",
    "downloadProhibited": false,
    "title": "Aufsichtsrat",
    "name": "Aufsichtsrat",
    "creationDate": "2020/06/12 07:15:18 +0000",
    "modificationDate": "2020/06/12 07:15:18 +0000",
    "author": "   ",
    "writeAccess": true,
    "subDocs": "0"
}

Children#

A Meeting Collection can only have other Meeting Collections and/or Meeting as children. There is no limit on the number of such children except for limits set by the back-end.

Contents