Skip to main content
Skip table of contents

Configuring Tables

 

Table Info

You can open the Table Info with a right click on any table in the Table List.

Parameter

ShowSizeTableInfo

Path

| DBM |

Possible Values

TRUE, YES, FALSE, NO

Description

Activates the field Size that calculates the size of all entries in this table in MB.

Default Table Sort Order

The configuration can be spread across USER, LOCAL and GLOBAL registries.

Any parameters set in USER will take precedence over LOCAL and GLOBAL. Parameters in LOCAL will take precedence over GLOBAL.

Per Table

ParameterDefaultSorting
Path| Digas | Database | [myDSN] | [myTable]
Possible Values

The value for a specific column is either one of the ones documented below (paragraph Column Identifiers) or a custom field, which is specified by the database field name.

Description

Defines which database column is to be applied to sort the table content which is shown in DBM's main table until the user clicks another column header to change the sorting.

This sorting is applied each time another table is selected for displaying.

Additionally a specifier for sorting ascending (ASC) or descending (DESC) can be provided to overwrite DBM's default (e.g. "FileSize DESC").

On tables for which this setting is missing, a sorting definition for specific database tables is applied (see TableDefaultSorting).

Examples
  • "DefaultSorting = Author" will sort ascending author and apply DBM. Default for this field is ASC
  • "DefaultSorting = Author ASC" will sort ascending author A -> Z
  • "DefaultSorting = Title DESC" will sort descending title Z -> A
  • "DefaultSorting = CreateDate" will sort descending by date and time (newest on top). Default for this field is DESC and time is implicit the secondary sort field.

For all Tables

ParameterTableDefaultSorting
Path| DBM |
Possible ValuesThe value for a specific column is either one of the ones documented below (paragraph Column Identifiers) or a custom field, which is specified by the database field name.
Description

Defines which database column is to be applied to sort a specific database table content which is shown in DBM's main table until the user clicks another column header to change the sorting.

This sorting is applied each time the selected table for displaying changes.

Additionally a specifier for sorting ascending (ASC) or descending (DESC) can be provided to overwrite DBM's default (e.g. "FileSize DESC").

This settings is overwritten by a database table's setting DefaultSorting, if existing (see DefaultSorting).

The default for this parameter is 2, meaning the created date being followed by created time and then followed by the RefNr.

Examples
  • "DefaultSorting = Author" will sort ascending author and apply DBM. Default for this field is ASC
  • "DefaultSorting = Author ASC" will sort ascending author A -> Z
  • "DefaultSorting = Title DESC" will sort descending title Z -> A
  • "DefaultSorting = CreateDate" will sort descending by date and time (newest on top). Default for this field is DESC and time is implicit the secondary sort field.

Column Identifiers

A default Table Sort Order as defined for a specific tables or overall is specified by a column name or a numeric column id value as described below. Additionally a specifier for sorting ascending or descending can be provided to overwrite DBM's default (e.g. "FileSize DESC").

The numeric values are in range 0 - 99. They are written to parameters below key <USER>\DBM\MainScreen with the Settings dialog's columns configuration. There you find a list of ContentX parameters, where X is the position of the visible column (numbering begins with 0!); the value there specifies the column id or name.

Name

(for configuration)

Numeric

DBM Column

(English UI)

DBM Column

(German UI)

Class0ClassKlasse
Title1TitleTitel
CreateDate2DateDatum

3TimeZeit
Duration4DurationDauer

5FlagsFlags
Author6AuthorAutor
Editor7EditorBearbeiter
Source8SourceQuelle
Ressort9DepartmentRessort
SubRessort10SubdepartmentSubressort
Program11ProgramProgramm
Broadcast12ShowSendung
BroadcastDate13Broadcast dateSendedatum
Registration14RegistrationKennziffer
MediumCode15MediumMedium
Number16Reference numberReferenznummer
Filename17Filename/URLDateiname/URL
Priority18In-/Out PriorityEin-/Ausgabe Priorität
Identifier19IdentifierIdent
Language20LanguageSprache
FirstUseDate21First use dateErste Verwendung
LastUseDate22Last use dateLetzte Verwendung
DeleteDate23DeletedateLöschdatum
Label24LabelLabel
Motive25Theme / motiveThema / Motiv
SpotLength26SpotlengthSpot-Länge
Customer27CustomerKunde
Product28ProductProdukt
ProductGroup29ProductgroupProduktgruppe
GenericTitle30Generic titleAllg. Bezeichnung
Singer31SingerSänger
Composer32ComposerKomponist
Performer33ArtistInterpret
Album34AlbumAlbum
Correspondent35CorrespondentKorrespondent
MusicId36Music IDMusik-ID
FileSize37FilesizeDateigröße
Orderer38OrdererBesteller
Distribution39DistributionVerteiler
ChangeUser40Change userGeändert durch
ChangeDate41Change dateÄnderungsdatum

42Change timeÄnderungszeit
Type43TypeTyp

44TableTabelle
Recordplace45Record LocationAufnahmeort
ReplFlags46Indexer FlagsIndexer Flags

47Number of broadcastsAnzahl Sendungen
MarkIn48MarkInMarkIn
MarkOut49MarkOutMarkOut
AudioMode50SurroundSurround
Story51GroupGruppe

52CartCart
Sort53SortSort

54Number of collectionsAnzahl Sammelmappen

55ThumbnailVorschaubild
Category56CategoryKategorie
LastWords57Last words / outcueLetzte Worte / Outcue
FirstWords58First wordsErste Worte
Presenter59PresenterModerator
Keywords60KeywordsStichworte
Intensity61IntensityIntensität
Project62ProjectProjekt
Speaker63SpeakerSprecher
PlayOutGain64GainGain (Verstärkung)
Mood65MoodStimmung
Tempo66TempoTempo
Endcode67Fading at end / endFading am Ende / Ende
LinkOut68LinkOutLinkOut
Style69StyleStil
Era70EraÄra
Publisher71PublisherVerlag

Hiding a Table

In order to hide a table to users set the following parameter:

Parameter

Enable

Path

| Digas | Database | [myDSN] | [myTable]

Possible Values

TRUE, YES, FALSE, NO, CM, DBM

Description

As default all tables are enabled. Set FALSE/NO to disable a table in DBM and ContentManager.

Use CM to make a table visible in Content Manager only,

Use DBM to make a table visible in Database Manager only.

DPE ContentManager evaluates this field using PREFER_USER, DigaSQL/DBM uses PREFER_LOCAL

Full-text Search

To tell DBM (and Content Manager) that full-text search can be used for a certain table, set the following value:

ParameterElasticsearch
Path

GLOBAL | Digas | Database | [myDSN] | [myTable]

GLOBAL | Digas | Database | [myDSN]

Possible ValuesTRUE, YES, FALSE, NO
DescriptionFull-text search must be configured for each table separately.

You must repeat this step for each full-text search enabled table.

Avoid duplicates in entry titles

To prevent users to give the same title to multiple table entries use the following parameter.

Parameter

AvoidDuplicateTitle

Path

| DBM |

Possible Values

TRUE, YES, FALSE, NO

Description

If set to TRUE/YES, every entry title has to be unique. This parameter can be defined in the |DBM key to affect all tables or in Digas|Database|...|...| to affect certain tables only

Default Class for New Entries

When a new entry is created in a table, it is assigned a class by default. You can define this default class by the parameters described here.

ParameterClass
Path

| Digas | Database | [myDSN] | [myTable] | Default

Possible ValuesNews, Cart, Music, Commercial, Audio, Magazine, Video, Story, Graphic, VideoProject, Sequoia, VideoBatch, Zip, DigaCutMT, DigaCutST
Description

The default class for all new entries, possibly except for groups and stories (see below).

To force the class to always have this value, append an exclamation mark ("!") to the class name.

ParameterClassGroup
Path

| Digas | Database | [myDSN] | [myTable] | Default

Possible ValuesNews, Cart, Music, Commercial, Audio, Magazine, Video, Story, Graphic, VideoProject, Sequoia, VideoBatch, Zip, DigaCutMT, DigaCutST
Description

The default class for new group entries.

If this parameter is missing, the class for new groups is taken from the "Class" parameter.


ParameterClassStory
Path

| Digas | Database | [myDSN] | [myTable] | Default

Possible ValuesNews, Cart, Music, Commercial, Audio, Magazine, Video, Story, Graphic, VideoProject, Sequoia, VideoBatch, Zip, DigaCutMT, DigaCutST
Description

The default class for new story entries.

If this parameter is missing, the class for new stories is taken from the "Class" parameter.

Configuring the "Groups" Filter

ParameterGroupFilterActivated
Path

| Digas | Database | [myDSN] | [myTable]

| DBM |

Possible Values

True enables the "groups" filter.

A global default for all tables can be provided in the DBM configuration folder.

It is read according USER / LOCAL / GLOBAL hierarchy

DescriptionThe "groups" filter has one of three states: "no filter", "only groups", or "no groups".

GroupFilterDefault is configured in the same way as GroupFilterActivated

ParameterGroupFilterDefault
Path

| Digas | Database | [myDSN] | [myTable]

| DBM |

Possible Values"OnlyGroups", "NoGroups" or "All"
Description

 The parameter determines which state is selected initially when you switch to a table.

 Of course this is only relevant if the "groups" filter is available for this table.

Enable Creation of Groups and Stories

Starting with DBM version 5.6.8149.0, this parameter controls whether users are allowed to create groups, stories, both, or neither.

ParameterCreateStoryGroup
Path| Digas | Database | [myDSN]
Possible ValuesNone, Group, Story, StoryAndGroup
DescriptionDefines whether the user can create groups, stories, both, or neither in a table of this database.

Usage of Distribution field

ParameterDisableDistributionFields
Path

| Digas | Database | [myDSN] | [myTable]

Possible Values

True disables the "distribution" field. Default is False

Description

If this parameter is set to "True", the "distribution" field of the "transfer" page is greyed out so that users can only read, but not modify its content. The In/Out page is not affected by this parameter

Needed when using StoryConnect functionality and wanting users to focus on StoryConnect and ignore DigaReplicator distribution targets.

Overrules | DBM | HideDistribution parameter.

Record functions

Deactivate recordings in DBM

In the DBM settings (menu "Program") the tab Local offers a field named "Playback only". Setting the check mark deactivates all record functions of DBM.
On parameter basis, add the value "Playback" to the parameter Local Settings|DBM|Recorder. Since the value is generally set to MULT the parameter should look like this: Recorder=MULTPlayback.

Record Table

If a record table is existing, DBM will automatically switch to this table, when creating a new record (new entry). That way all new records are saved in that record table, instead of any table.

Parameter

RecordTable

Path

User  | DBM |

Possible Values

Ask, [ODBC NAME] \[TABLE NAME]

Description

Only valid in the User Settings. Enter the ODBC connection\ Table (e.g. "LocalDigas\Local") DBM will switch to, when creating a new entry. If the value is Ask, a dialog will let the user select a table for recording. Combine both (e.g. "Ask, LocalDigas\Local"), the select table dialog will still appear, but suggest the entered table as default

Show record tab first in new recordings

Parameter

RecordMaskAlwaysFirst

Path

| DBM |

Possible Values

TRUE, YES, FALSE, NO

Description

With this value you can force the DBM to show the record tab as first sub mask for all new audio recordings independent of the settings for the classes.

Define automatic table Refresh

Parameter

UpdateTime

Path

| Digas | Database | [myDSN] | [myTable]

Possible Values

0, 1, …

Description

If you specify a value UpdateTime (Integer) which is different from 0, the Database Manager takes this number as interval in milliseconds to look for changes in the table currently displayed.

Archive Tables (outdated feature, not recommended)

Outdated feature: This feature has been designed to access older medium types, such as MODs, CDs or JAZ drives. Therefore, it is not recommended for newer DigaSystem installations, because this feature does not offer any advantages, compared to up-to-date tables being used as an archive.

Archive Tables technically work like ordinary tables, but the slightly different configuration makes them not appear in the table list. Instead, they are only accessible by the launch button 

 in the DBM toolbar and only on work stations that are defined as "Archive work station" via a parameter.
The following description shows how to set up archive tables in a basic configuration and how to make them accessible on certain work stations. Several more parameters allow a more detailed configuration to certain needs, such as:

  • Define multiple paths for an archive table
  • Define paths for read-only media

To do so, please consult the DIGPARAM.RTF file that is delivered with DigaSystem and can be opened with the F1 key in the DigaSystem Administrator (search for the archive paths as mentioned below).

  • In DigaSystem Administrator: Create a new table manually or using the table wizard (as described in the DigaSystem_InstallationManual_ENG/DE in chapter Table Administration.
  • Then, remove the parameter Global/Local Settings|Digas|Database|…|…|Sound
  • Instead, create the new sub folders
    • Global/Local Settings|Digas|Database|…|…|Archive|
    • Global/Local Settings|Digas|Database|…|…|Writepath|
  • Enter the parameter Global/Local Settings|Digas|Database|…|…|Writepath|Path1=<path for media files>
  • To allow a work station to access the archive tables, set the parameter:
    Local Settings|DBM|ArchiveEnabled=TRUE

The defined archive tables are now accessible in DBM via the 

 icon.

Deletion Routine

Although a deletion routine using DigAlign/DigErase is recommended, this parameter can fulfill some basic deletion tasks.

Parameter

DBMAutoDelete

Path

| Digas | Database | [myDSN] | [myTable]

Possible Values

[ENTRIES]n[AGE]n[DELETEDATE]+n[FREESPACE]n[SOFTDELETED]n

Since DBM version 5.6.8123.0: [ENTRIES]n[AGE]n[DELETEDATE]+n[FREESPACE]n[SOFTDELETED]n[DATE]datetype

Description

This parameter instructs the Database Manager to automatically delete entries from the table every time a new entry is created (affects normal and soft deleted entries). There are 4 possible criteria:

  • "[ENTRIES]n" is a maximum amount of n entries in the table.
  • "[AGE]n" is a maximum age of the entries of n days. 
  • "[DELETEDATE]n" is the number of elapsed days since the delete date was reached. By default only soft-deleted entries are deleted. If you precede the number of days by a '' also normal entries are deleted. 
  • "[FREESPACE]n" is a minimum free disk space of n MB on the corresponding media path.
  • "[DATE]datetype" is either "CREATE" or "CHANGE". If this specification is missing or datetype is not one of these values, then "CREATE" is assumed. It defines which date/time (creation or change) is used when [AGE] is specified, and when entries must be auto deleted, defines the order of deletion (oldest by creation or by change date/time first). The [DATE] specification is new with version 5.6.8123.0; older versions always assume [DATE]CREATE.
  • "[SOFTDELETED]n" deletes soft deleted entries that have not been changed during the past n days (n=1 means: have not been changed today, but n=0 means all soft deleted entries). This option is only available since DBM version 5.3.7896.0.

Specify a string with 1-5 sections. 

Example: "[ENTRIES]50[AGE]100[FREESPACE]500[DELETEDATE]0". Hint: The Database Manager cannot delete personal entries, so they shouldn't be used in this context. The logged in user must have the rights "Delete" and "Erase".

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.