Who Should Be an Author on a Paper? IV: Practical Ethics of Authorship

Part I is here.  You’ll need to read it and prior entries for context.

Let me start this final(?) part with a formal statement of my suggestion:

In general, researchers writing a paper that uses unpublished or otherwise unciteable data they did not produce should invite the proposers/observers/producers of that data to be co-authors.

Now, there are many situations where following my co-authorship suggestion isn’t practical. Maybe there are not well defined “proposers”. Maybe the data are 30 years old and widely used. Maybe there is a timeliness or competitive issue that precludes letting the proposer know what you’re working on. Maybe the proposing team didn’t actually do a lot of work to make the observations happen. Maybe the proposer is a social pariah or one of your more important co-authors refuses to be on a paper with them. Maybe you’re on a deadline and simply don’t have time. Maybe you’re in a collaboration whose authorship rules preclude adding these people to the paper. Depending on the specifics of a situation, those might be part of completely legitimate reasons to go ahead and publish without them.

Ethics is often a case-by-case subject; broadly written rules can become outdated, or fail to anticipate pathological cases, or obviously fail in corner cases, or just be too vague to apply to edge cases.  Personal ethics also come into play: we do not all share the same values, and do not all take the same approach to collaboration. Ethics also depend on expectations of the community, and those can change.

But I think our community’s expectation and standard that we never need to include the people who took otherwise unciteable data as co-authors is wrong and should change. 

I encourage my colleagues to consider adopting a presumption that the observers/proposers of public but unpublished data should be invited as co-authors, and even taken on as collaborators early in the project. If there are good reasons not to do so, that’s fine, but those reasons should be articulated and considered and weighed against the good reasons to the contrary before a decision is made.

So before rejecting this presumption, astronomers should ask themselves:

  • Why not include them?
  • What does it really cost me to include them?
  • Why not gain a collaborator?  Why not have a longer author list?
  • What would I want them to do if the roles were reversed?

In many cases, the answers to these questions might lead authors to conclude that the producers of the data should not be co-authors, and that’s fine.

But let’s ask these questions more often.

Finally, because Josh Peek got me off on this tangent on Twitter, inspired my particular example, and is working on the MAST data policy which will guide this sort of thing, let me suggest a concrete policy for MAST, consistent with my proposal and the AAS Ethics Policy:

  1. Propriety only concerns who can see and use data. It is silent on the issues of authorship. Public data are in the public domain and anyone may download them and use them as they see fit.
  2. STScI will provide guidance to users of its data products on how to properly credit STScI and its employees for their work. This is probably something like: include the boilerplate acknowledgement, and cite such and such papers describing the instrument and analysis methods.
  3. STScI should have an internal policy for how its many scientists accrue credit (citations and authorship) for their work on projects that produce data, especially for papers produced with public data they enabled. This policy should be consistent with community norms and (hopefully) the AAS Ethics Policy (which may need to change).

That’s it!  If authors want to scoop others and not give them co-authorship, that’s not MAST’s problem (indeed, it is part of MAST’s charter to enable such scooping!).  The AAS Committee on Ethics may be interested in that author list, of course, but I see no reason (or mechanism!) for MAST to be telling its users what they can do with public domain data except publish publish publish.

OK, that’s it.  Flame on!  I will probably update this thread with more entries as good ideas roll in.

[Edit: One more post!  I linked to the old Code of Ethics.  The new one actually further supports my position, I think.]

5 thoughts on “Who Should Be an Author on a Paper? IV: Practical Ethics of Authorship

  1. Alex Santerne

    Just discovered this – Nice discussion ! Agreed with most of what you wrote.
    This issue has been solved years ago in the case of creative works (such as pictures, videos, etc…). That’s exactly what the Creative Commons Licences are made for. Astronomical data are very similar to creative work, except that the former only have a binary status (public or non-public). We definitely need more flavours with data policy !

  2. anon

    As far as I know, in some other fields of science (mainly medicine/life sciences) it’s been common that the head of a group (who holds the funding grants) is last author on every paper no matter how small his/her contribution to writing that particular paper has been, and this practice is something that is now strongly discouraged. So my comment was maybe not that relevant to astrophysics, where the culture is quite different.

    Personally, if I was in Amber’s or Brie’s position, I would definitely refuse to be included as a co-author if I hadn’t contributed to anything else than the proposal. Even if the paper was written by Candice instead of Joe.

  3. jtw13 Post author

    Not sure I understand the question.

    If by being the PI of the grant they “contributed significantly to the inception, design, execution, or interpretation of the research to be reported” then yes.

    Otherwise (for instance if they are only an administrative PI and not really involved in the project) then no.

  4. anon

    How about funding proposals? Does the PI get to be on every paper that comes from the group that is funded by the grant?

  5. Josh Pepper

    These policies should also be recommended to IPAC and NExScI, and any other archives.

Leave a Reply

Your email address will not be published. Required fields are marked *