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
@michaelnmmeyer — in the past, Axelle's system and easrly version of yours do not seem to have picked up contents of Contributor fields. I learned to live with this by entering Zotero data in such a way that persons not needing to figure in a citation are recorded in Contributor fields, while those needing to appear are Author (or editor, etc.).
Now the setup seems to have changed, because the contributor of entry Zoetmulder1982_01 is displayed at though he is a regular co-author:
I think you need us to list what behaviors are wanted. I hope @danbalogh can help.
The text was updated successfully, but these errors were encountered:
I certainly agree with 1.
My personal preference would be to forget completely about any fields other than author and editor, because doing otherwise will lead to complications. I would thus prefer, instead of 2, to suppress the contents of any other field, and not show them at all, anywhere, even if they have been filled out for the sake of completeness in some of our Zotero entries. But quite possibly Arlo would prefer something along the lines of your 2, which is also fine by me. Perhaps, to keep things simpler: "(With S. O. Robson.)" instead of "In collaboration with S. O. Robson."
@michaelnmmeyer — in the past, Axelle's system and easrly version of yours do not seem to have picked up contents of Contributor fields. I learned to live with this by entering Zotero data in such a way that persons not needing to figure in a citation are recorded in Contributor fields, while those needing to appear are Author (or editor, etc.).
Now the setup seems to have changed, because the contributor of entry Zoetmulder1982_01 is displayed at though he is a regular co-author:
I think you need us to list what behaviors are wanted. I hope @danbalogh can help.
The text was updated successfully, but these errors were encountered: