Title types
Last updated: 19/04/2022
Studies have a scientific (full or protocol) title, and some data objects, such as journal articles, also have explicit titles. In many cases either studies or data objects can also have alternative or additional titles. The system keeps these in the database so that they can be used in searches, and they are categorised using the title types listed in this table.
| id | name | applies_to | description | use_in_data_entry | source |
|---|---|---|---|---|---|
| 16 | Trial registry title | Study | Full scientific title, as quoted in a trial registry. | true | ECRIN |
| 17 | Protocol title | Study | Full scientific title, from a punlished protocol. | true | ECRIN |
| 18 | Other scientific title | Study | Full scientific title, not from the protocol or registry entry. | true | ECRIN |
| 14 | Acronym or abbreviation | Study | As provided by study sponsors. | true | ECRIN |
| 15 | Public title | Study | In contrast to the full scientific title, usually from a trial registry. | true | ECRIN |
| 12 | Subtitle | All | A subtitle provided by object creators or study sponsors. | true | DataCite |
| 13 | Translated title | All | Used in conjunction with language code to indicate language translated into. | true | DataCite |
| 19 | Journal article title | Data Object | Full journal title, as listed in citation. | true | ECRIN |
| 20 | Unique data object title | Data Object | Use if the given name for the data object can be guaranteed to be unique. | true | ECRIN |
| 21 | Study short name :: object name | Data Object | Constructed using study short name to prefix a non unique name. If obvious from context study name can be omitted. | true | ECRIN |
| 22 | Study short name :: object type | Data Object | Constructed using study short name to prefix object's type. If obvious from context study name can be omitted. | true | ECRIN |
| 23 | Study scientific name :: object name | Data Object | Constructed using study full name to prefix a non unique name. If obvious from context study name can be omitted. | false | ECRIN |
| 24 | Study scientific name :: object type | Data Object | Constructed using study full name to prefix object's type. If obvious from context study name can be omitted. | false | ECRIN |
| 25 | Study registry ID :: object name | Data Object | Constructed using registry id to prefix a non unique name. If obvious from context study ID can be omitted. | false | ECRIN |
| 26 | Study registry ID :: object type | Data Object | Constructed using registry id to prefix object's type. If obvious from context study ID can be omitted. | false | ECRIN |
| 90 | Other alternative title | All | Any alternative title not described elsewhere. | true | DataCite |
| 0 | Not yet known | All | Dummy value supplied by default on entity creation. | false | ECRIN |
In most cases (non journal) data object titles will have to be constructed as they will not possess a unique name. The preference should be to use the short study title as the prefix for the object's name or type, with the two separated by a double colon, e.g.
The Biopsychosocial Burden of Prostate Biopsy :: CTG Registry entry, or
Reducing Hippocampal Hyperactivity and Improving Cognition in Schizophrenia :: Protocol
Note that for registry entries the registry should be indicated, as some studies will have multiple registry entries.
If there is no brief (or 'public') title the scientific title can be used. If the scientific title is too long (e.g. longer than 200 characters) it may be more useful to use the study's primary registry id as a prefix instead.
The context will often make it unnecessary to include the prefix. For example the display of linked data objects under a study heading would allow the study name prefix to be dropped.
