list_attributeDefinitions | R Documentation |
Add / List / Rename / Remove database operation functions for attribute
definition to / of / from an existing level definition of an emuDB.
Attribute definitions can be viewed as definitions of
parallel labels for the annotational units (ITEMs) of the emuDB.
Each level definition is required to have at least one
default attribute definition that has the same name as the level definition
(automatically created by add_levelDefinition
). For more
information on the structural elements of an emuDB see vignette(emuDB)
.
Note that as with level definitions, an attribute definition to a level cannot be removed,
if it contains labels in the emuDB.
As the only one of these operations, rename_attributeDefinition
can
also be used to manipulate (i.e. rename) a level definition. It is therefore
not necessary to specify the name of the level that the attribute definition
belongs to. While renaming a level or attribute definition, emuR will
(1) rewrite the levelDefinitions in DBconfig, (2) rewrite the
linkDefinitions in DBconfig, (3) rewrite the perspectives in DBconfig,
(4) rewrite the anagestConfig in DBconfig, and (5) rewrite all _annot.json
files. (5) May take quite a while, depending on the number of bundles in the
database.
list_attributeDefinitions(emuDBhandle, levelName)
emuDBhandle |
emuDB handle as returned by |
levelName |
name of level |
emuR::list_attributeDefinitions
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.