Database/Table Configuration
Change the following parameters in the DigaSystem Administrator to customize basic functions in the Content Manager and enable features with the available licenses. See Notation in the Learn and Explore section to understand the parameter notation.
Database/Table related configuration
Following configuration settings are applied on Database/Table level and are valid for Database Manager and used also from Content Manager.
Functionality | Description | |
---|---|---|
Auto Refresh | An auto refresh can be defined for every database by setting the key ...|Digas|Database|[dsn]|UpdateTime. The value 0 deactivates the function. Furthermore, the refresh interval cannot be under 2000 ms, every value below 2000 is replaced by 2000. | |
Maximum Number of Displayed entries | Set the key ...|Digas|Database|[dsn]|[table]|MaxResults to define the number of displayed entries. | |
Table Color | Set the key ...|Digas|Database|[dsn]|[table]|TableColor to define a color for tables. Tables with a lower color number are displayed before tables with higher (or no color) number. Tables with the same color are ordered alphabetically. If no color then a transparent color is applied and table gets ordered at last if ascending sorting applied to the color column. The default table colors can be overwritten using the UI theming. | |
Table Order | Set the key ...|Digas|Database|[dsn]|[table]|Order to define an order for tables. Tables with a lower order are displayed before tables with higher (or no order). Tables with the same order are ordered alphabetically. | |
Table Groups | Assign each table to one or more table groups by specifying list of table group names in key ...|Digas|Database|[dsn]|[table]|MemberInGroups=[Table Group Name1],[Table Group Name2],... . Be aware to set also the respective application-specific key (see below). | |
Full-text search | Determines whether Full-text search is available in a table or database. Per default, it is not. Full-text search is realized via Elasticsearch which is a based on the Lucene library. To enable Full-text search: Create a key ...|Digas|Database|[dsn]|Elasticsearch=True (for the entire databases) or in ...|Digas|Database|[dsn]|[Table]|Elasticsearch=True (for a dedicated table). Be aware when having a mixed system with DigaSQL.dll and DPE Services based endpoints, that all DigaSQL.dll based endpoints properly configured for Elasticsearch based full-text index. | |
ElasticsearchAsDefault | Determines if Full-text search should be used as a default search mode in CM when searching content in Digas database. The property will only work for tables that have Full-text search configured/enabled. | |
Facetsearch | Set ...|Digas|Database|[dsn]|[table]|FacetSearch to:
| |
ContentFacets | Allows to configure the Content Manager facet search per table (and user). Set ...|Digas|Database|[dsn]|ContentFacets for all tables inside a database Set ...|Digas|Database|[dsn]|[table]|ContentFacets for a specific table The value syntax is identical to the values used in web.config, see Configuring web.config Files Example value: "General|N=Author|O=A,Modified,State,Class,Ready,Perfect,Invalid" Available since DPE 2.12.x and NanoServices 1.1.x | |
Filter Configuration | To define Table specific filter configuration: Set ...|Digas|Database|[dsn]|[table]|ContentManagerFilters to: An ordered comma-separated value of Filter folder names located under ContentManager|Filter. e.g. SoftDeleted, All=Default, AudioOnly, LoudnessAnalyzed where Softdeleted filter will appear on top, LoudnessAnalyzed in the bottom and All will be the default filter. For more information, see Filter Configuration | |
Column Configuration | To define Table specific column configuration: Set ...|Digas|Database|[dsn]|[table]|ContentManagerColumns to: An ordered comma-separated value of column folder names located under ContentManager|Columns with optional width e.g. Group=48,Class=48,State,AudioPlayer=70,Title=350,Duration=80,Created=120,Author=100,Editor=100 where Group column will get a width of 48 pixels, State column will get a default width of 90 pixels. Group column will appear on the leftmost position, Editor on the rightmost position. For more information, see Column Configuration | |
Default values for Entry Metadata Configuration | For each table you can define some default values which are automatically assigned when creating new database entries. The defaults must be listed in a subkey to the table with name "Default". Set a key inside ...|Digas|Database|[dsn]|[table]|Default folder to define default value for a metadata field. The Key Name is the binding name for the metadata. Please see Available Bindings and Values in Content Manager for binding names. Content Manager allows setting default values to following fields:
| |
Mandatory (= Essential) Fields | For each table you can define mandatory fields which have to be filled out when adding a new entry. Specify a comma-separated list of mandatory fields inside the key de ...|Digas|Database|[dsn]|[table]|EssentialFields. Possible Values:
The following extended feature allows to make more fields and also custom fields mandatory: Add a folder: ...|Digas|Database|[dsn]|[table]|EssentialFieldsEx.
Note: currently Content Manager is not validating the entries when copying from one table to another. Also see Validation of User Input | |
Calculated Duration | To define Table specific Calculated Duration: Set ...|Digas|Database|[dsn]|[table]|DisplayOfDuration to:
The Calculated Duration can be configured as a column for the table, see Column Configuration. | |
Allowed Classes | You can specify classes to restrict the content of the Table. For example to only allow entries of Class Audio and Music set ...|Digas|Database|[dsn]|[table]|AllowedClasses to: Audio,Music For reference on classes, see Understanding Classes. | |
Allowed File Extensions | Set ...|Digas|Database|[dsn]|[table]|AllowedExtensions to:
| |
Allowed Audio Templates | You can specify audio templates to restrict the table to certain audio formats. When you copying or uploading audio files to this table and the audio does not match the specified formats the audio files will be converted. For example set ...|Digas|Database|[dsn]|[table]|AudioTemplates|Allowed to MyAudioTemplate1,MyAudioTemplate2 ...|Digas|Database|[dsn]|[table]|AudioTemplates|Default to MyAudioTemplate1 where MyAudioTemplate1 and MyAudioTemplate2 must be specified audio templates under ...|AudioTemplates | |
Hide a table - or make available only in CM or DBM | Set ...|Digas|Database|[dsn ]|[table]|Enable to:
DPE/ContentManager evaluates this field using PREFER_USER, DigaSQL/DBM uses PREFER_LOCAL | |
ResetTimeOnCopy | Set ...|Digas|Database|[dsn ]|[table]|ResetTimeOnCopy to: Reset the create date+time when something is copied to this table This parameter must be set on GLOBAL level it cannot be set on COMPUTER or USER level. | |
Audio resolution | You can specify the audio resolution for all audio players when playing entries of a given table. Set the key ...|Digas|Database|[dsn]|[table]|WebPreListenQuality to :
Any other value will be ignored and raise a warning log. Beware that the table configuration overwrites the ContentManager audio resolution specified at ...|ContentManager|HiResPreListen. Note that if no audio resolution is configured at both levels, the default is low audio resolution. | |
Audio waveform | The audio player can display the audio waveform if...
The audio player will not request a waveform if no waveform exists and ...|Digas|Database|[dsn]|[table]|OnTheFlyWaveformDisabled is set to true | |
CheckFlagsOnCopy | If specified flags are not set in an entry ContentManager or DBM cannot copy this entry. If more than one flag is defined here, each flag must be set before entry can be copied. If parameter contains 'READYPERFECT' the flag 'READY' or the flag 'PERFECT' must be set. |
Content Manager specific configuration
Functionality | Description | |
---|---|---|
Table Groups | Add the names of the Table Groups separated to …|ContentManager|TableGroups=[Table Group 1 Name, Table Group 2 Name] Note: Currently only one group can be defined in this key and displayed in the Content Manager! To show another group this key has to be changed accordingly! When a Table Group is selected in Content Manager, only tables being a member of that group are shown. The Table Group feature is activated if a Table Group exists. |