Author roles draft definitions

James Hester jamesrhester at gmail.com
Wed Aug 26 02:01:50 BST 2020


Dear Core DMG,

Antanas has suggested (as a comment on the corresponding Github issue, see
https://github.com/COMCIFS/cif_core/issues/158#issuecomment-679311199 )
that we add 'other' as a possibility for an author role, as well as
additionally _audit_author_role.special_details to explain what 'other'
might mean and to allow further explanation to the other roles if desired,
e.g. which steps in a complex synthesis where conducted by whom.

This seems uncontroversial to me and addresses one of Herbert's points
below.

James.

On Mon, 24 Aug 2020 at 14:30, James Hester <jamesrhester at gmail.com> wrote:

> Dear Core DMG,
>
> There having been no unresolved objections to the author role definitions,
> I will now move them to the technical editing stage.  Thanks for your
> contributions.
>
> all the best,
> James.
>
> On Fri, 7 Aug 2020 at 12:10, James Hester <jamesrhester at gmail.com> wrote:
>
>> Dear Core DMG,
>>
>> Please see the draft definitions for author roles provided below,
>> developed in consultation with the CCDC and Chester. Please advise if you
>> feel any roles are missing. The roles are listed at the very end of the
>> definitions, the rest is boilerplate for setting up a new category.
>>
>> Note that we have explicitly decided not to adopt the CREDIT taxonomy, as
>> that did not capture the way crystallographic experiments are conducted
>> with sufficient granularity. The option remains open for us to include a
>> separate category where "CREDIT" roles are assigned to authors.
>>
>> An important decision that is encoded in the definitions below is that
>> the "primary" author identifier is found in the audit_author loop rather
>> than e.g. publ_author. This expands the role of audit_author authors to
>> cover anything related to the production of the data, whereas you could
>> argue that this category was originally intended to cover "just" the author
>> of the data block. If you expect this subtle in interpretation to cause
>> problems, please speak up.
>>
>> thanks,
>> James (Acting chair)
>> ================================
>> #
>> # Draft definitions for author roles, for discussion
>> #
>> save_AUDIT_AUTHOR_ROLE
>>
>> _definition.id                          AUDIT_AUTHOR_ROLE
>> _definition.scope                       Category
>> _definition.class                       Loop
>> _definition.update                      2020-08-06
>> _description.text
>> ;
>>      The CATEGORY of data items used to describe the role that
>>      authors took in the production of the dataset.
>> ;
>> _name.category_id                       AUDIT
>> _name.object_id                         AUDIT_AUTHOR_ROLE
>> _category.key_id                        '_audit_author_role.id'
>> loop_
>>   _category_key.name
>>          '_audit_author_role.id'
>>          '_audit_author_role.role'
>>
>> save_
>>
>> save_audit_author_role.id
>>
>> _definition.id                          '_audit_author_role.id'
>> _description.text
>> ;
>>      Unique identifier for the author for whom a role is identified.
>>      This may be repeated where an author took on multiple roles.
>> ;
>> _name.category_id                       audit_author_role
>> _name.object_id                         id
>> _name.linked_item_id                    '_audit_author.id'
>> _type.purpose                           Encode
>> _type.source                            Recorded
>> _type.container                         Single
>> _type.contents                          Code
>> save_
>>
>> save_audit_author_role.role
>> _definition.id                          '_audit_author_role.role'
>> _description.text
>> ;
>>      The role taken by the author identified by _audit_author_role.id,
>>      drawn from a predefined list.
>> ;
>> _name.category_id                       audit_author_role
>> _name.object_id                         role
>> _type.purpose                           State
>> _type.source                            Assigned
>> _type.container                         Single
>> _type.contents                          Text
>> loop_
>>   _enumeration_set.state
>>   _enumeration_set.detail
>>         design     'conceived and/or designed the experiment'
>>         synthesis  'synthesised the samples'
>>         preparation 'prepared the samples for measurement, e.g.
>> crystallised or recrystallised the sample'
>>         characterisation 'performed non-crystallographic measurements on
>> the samples'
>>         measurement 'collected and/or reduced diffraction data'
>>         analysis  'worked on the structural model'
>>         software  'developed bespoke software for specialised data
>> processing and/or analysis'
>>         submission 'prepared the final CIF file'
>> save_
>> --
>> T +61 (02) 9717 9907
>> F +61 (02) 9717 3145
>> M +61 (04) 0249 4148
>>
>
>
> --
> T +61 (02) 9717 9907
> F +61 (02) 9717 3145
> M +61 (04) 0249 4148
>


-- 
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.iucr.org/pipermail/coredmg/attachments/20200826/8cce630d/attachment.html>


More information about the coreDMG mailing list