Credit Database Functions

This function is used to test if a specified credit is known by the Combined Credits Editor's credit database. It can also be used to add or remove user defined credits.

All text fields may contain any of the escape sequences described in Escape Sequences.

The function is only executed once per set of files while executing stepwise.

The following functions are supported: Lookup Credit, Add Credits, Remove Credits, Set Alias. If you want to get a full or partial list of credits in the database, you can use a Get Info statement's Filtered List of Credit Roles function.

Lookup Credit

The action test state is set to true if the specified credit is known, otherwise it is set to false. See the ~ code below for a possible partial match. Three special named variables are also set:

Lookup Credit Alias

If the known credit is an alias of another, it will be specified here. The named variable will be cleared otherwise.

Lookup Credit Name

Credit names are case insensitive. This named variable will contain the credit's name as specified in the known credits list.

Lookup Credit Status

Information on the known credit will be returned as a sequence of characters in this named variable. The following case sensitive codes may appear:

D

The credit is a known Discogs credit.

B

The credit is a known MusicBrainz credit.

R

The credit is a known Roon credit.

U

The credit is user defined.

~

The supplied credit is only matched if its [qualifier] is removed.

I

The credit has a default mapping to the Involved People field.

M

The credit has a default mapping to the Musician Credits field.

c

The credit is marked as being mapped to the Conductor field.

C

The credit is marked as being mapped to the Composer field.

L

The credit is marked as being mapped to the Lyricist field.

X

The credit is marked as being mapped to the Remixer field.

Add Credits

One or more user defined credits may be added. The Credits field (after unescaping) is considered a list of items delimited by the default list delimiter (\~).

The added credits may be mapped to Musician Credits or Involved People. The Mapping field is designed such that the field association can be specified when the statement is created or at runtime via an escape sequence. The field is interpreted by looking for M and I characters (case insensitive) after unescaping.

• If an M character comes first, the mapping is Musician Credits.
• If an I character comes first, the mapping is Involved People.
• If neither an M or I character is found, the mapping is Musician Credits.

You can optionally specify the credits being added are an alias to a different credit. If an alias is specified, it must exist or the new credits will not be created. The alias's alphabetic case as in the database is always used. The alias's mapping overrides the specified mapping.

Remember that the mapping and optional alias are applied to all created credits.

The action test state is set to true if any credits were created.

Remove Credits

One or more user defined credits may be removed. The Credits field (after unescaping) is considered a list of items delimited by the default list delimiter (\~). Credits other than user defined credits are not deleted.

The action test state is set to true if any credits were deleted.

Set Alias

One or more credits can have their alias set or modified. The Credits field (after unescaping) is considered a list of items delimited by the default list delimiter (\~). There is no requirement that the specified credits are user defined credits.

The specified alias must exist or no changes will occur. The alias's alphabetic case as in the database is always used.

Every existing credit will have its alias set. If a credit does not exist, it will be created as an alias.

The action test state is set to true if any aliases were modified.