You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that the PUBL_CONTACT_AUTHOR is now a looped category, so the descriptions should probably be updated accordingly ("of a contact author" changed to "of the contact author", etc.). Alternatively, the category could be reverted back to a Set category (I think it became looped immediately after migration from DDL1 to DDLm). However, I am unsure why the change was made in the first place, maybe to accommodate journals that allow several contact authors?
Please note that the PUBL_CONTACT_AUTHOR is now a looped category, so the descriptions should probably be updated accordingly
Good catch. I suspect it was changed to Loop to align with AUDIT_CONTACT_AUTHOR, where presumably databases allow more than one contact author. I checked with IUCr journals before making the changes in this PR, and they are emphatic that there should be only one article contact author. However, it may be that other publishers are more accommodating (though I foresee administrative difficulties with a policy that allows more than one point of contact).
Anyway, I propose to address this in the next PR by generally changing the introductory sentence to 'The name of a contact author...' etc. and making similar changes to the AUDIT_CONTACT_AUTHOR items. However, I will leave the definite article in place in subsequent references within such a definition, e.g. 'This is the person contacted by the journal editorial staff.' This may be understood at least by sophisticated English language readers as assigning a (linguistic) categorization to any one of the authors designated as a contact author. The result is a constructive ambiguity that I think permits publishers to have both single- and multiple-agent policies, and preserves the Loop category structure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.