Difference between revisions of "Title types"

From ECRIN-MDR Wiki
Jump to navigation Jump to search
Line 58: Line 58:
  
 
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. <br/>
 
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. <br/>
''The Biopsychosocial Burden of Prostate Biopsy ::  CTG Registry entry'', or ''Reducing Hippocampal Hyperactivity and Improving Cognition in Schizophrenia :: Protocol''
+
&nbsp;&nbsp;&nbsp;&nbsp;''The Biopsychosocial Burden of Prostate Biopsy ::  CTG Registry entry'', or <br/>
 +
&nbsp;&nbsp;&nbsp;&nbsp;''Reducing Hippocampal Hyperactivity and Improving Cognition in Schizophrenia :: Protocol''
 
<br/>
 
<br/>
 
Where this is not possible 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. <br/>
 
Where this is not possible 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. <br/>
 
In all three cases 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.
 
In all three cases 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.

Revision as of 14:58, 1 November 2019

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 source
16 Trial registry title Study Full scientific title, as quoted in a trial registry. ECRIN
17 Protocol title Study Full scientific title, from a punlished protocol. ECRIN
18 Other scientific title Study Full scientific title, not from the protocol or registry entry. ECRIN
14 Acronym or Abbreviation Study As provided by study sponsors. ECRIN
15 Public Title Study In contrast to the full scientific title, usually from a trial registry. ECRIN
12 Subtitle All A subtitle provided by object creators or study sponsors. DataCite
13 Translated Title All Used in conjunction with language code to indicate language translated into. DataCite
19 Journal article title Data Object Full journal title, as listed in citation. ECRIN
20 Unique data object title Data Object Use if the given name for the data object can be guaranteed to be unique. 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. 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. 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. 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. 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. 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. ECRIN
90 Other Alternative Title All Any alternative title not described elsewhere. DataCite
0 Not yet known All Dummy value supplied by default on entity creation. 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
Where this is not possible 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.
In all three cases 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.