remarks

Header data of the text notes on folders, registers, documents and portfolios: one row per note, with the assignment to the object, the colour and audit fields.

The note text is not held in this table. Depending on the storage mode it is either a text file in the file system or a row in osremarktext.

Note links to other DMS objects are not held here either; they live in hyplnk.

1. Columns

Name Type Length Description

id

int

—

System-wide unique note ID. Corresponds to RemIdent in std.GetRemark, std.StoreRemark and std.DeleteRemark, and to remark_id in the XML import.

parent

int

—

ID of the DMS object the note is attached to.

parenttype

int

—

Object-type ID of that object (object-type ID).

medium

int

—

Medium ID of the NOTE system medium in medien holding the note file. Under database storage NULL — the query output carries 0 in the same place, so WHERE medium = 0 does not find the row.

type

int

—

Colour of the note: 1 = white, 2 = yellow, 3 = green, 4 = blue.

stamp1

int

—

Creation timestamp (UNIX time).

user1

int

—

User ID of the creator.

stamp2

int

—

Timestamp of the last change (UNIX time).

user2

int

—

User ID of the last modifier.

textid

nvarchar

32

Under database storage the key of the note text in osremarktext, under file-system storage NULL.

The textid column is missing from the table description in the vendor manual. The mapping to osremarktext.textid was measured against enaio® server 12.0.

Under file-system storage std.DeleteRemark removes only the note file and leaves the row here in place. The note keeps being delivered afterwards, with an empty <Text>, and can no longer be repaired through UPDATE_TEXT. Only dms.XMLUpdate with <RemarkText action="DELETE"> removes it completely.