Hey CodeMeta'ers :0 Anyone want to review my PR for the SCWG document about the codemeta crosswalk; see force11/force11-scwg#125
Kyle Niemeyer
@kyleniemeyer
@cboettig@danielskatz@ashleysa (the latter two may not be in Gitter): we should try to resolve the authorship question
Carl Boettiger
@cboettig
@kyleniemeyer@danielkatz@ashleysa indeed. open to ideas but here's one proposal for you: If no one wants to take on a leadership role in wrangling and seeing it out the door; I'm happy to cover that and play first-author. If someone (cough Kyle) wants to do that I'd love to make them first author, maybe Ashley as second, and propose I go at the end ("senior author"). We order the others by some arbitrary metric, and we say authorship order was determined by "the consensus of the workshop" if we comment on it at all. Does this sound fair?
Daniel S. Katz
@danielskatz
As I said at the meeting, I think we either should list authors based on contribution (perhaps determined via the general consensus of the participants), or we should alphabetize (other than the lead author), as people who see a citation to the document will assume that we are doing one of these: If the order is alphabetic, it will be assumed that we used alphabetic order, and if the order is anything else, it will be assumed that we ordered according to contribution. (I can't believe I'm writing this badly while listening to a talk on bad writing)
Kyle Niemeyer
@kyleniemeyer
Since @cboettig suggested it (and @danielskatz has done the lion’s share of the work on the software citation principles doc), I can take the helm on this one
(was trying to fit as many cliches in there as I could)
Matt Jones
@mbjones
I agree with Dan's assessment of ordering -- first author, then alphabetical. Otherwise, it should go by order of contribution, and that is much harder to determine, especially as several people have bene working off and on on this for several years.
_
Daniel S. Katz
@danielskatz
That's another good point - this shouldn't just be based on contributions to the paper but really to the whole ball of wax (trying to follow Kyle's example of the use of cliches)
Ashley E. Sands
@ashleysa
The final potential authorship is a hybrid - the first set of authors are entered by order of contribution (or order of 'needing' authorship order?) and then the second set is alphabetical. This is actually common in astronomy. Perhaps too complicated in this context. The first set could be folks who 'need' earlier authorship and who actually step-up to ensure the writing itself is completed. Again, that's an option but may be too complicated - though it does provide incentive to not let the paper itself linger now that the enthusiasm of the weekend is over ;)
Kyle Niemeyer
@kyleniemeyer
@ashleysa that is certainly an interesting idea, but that hierarchy might not be recognizable by most (or supported by the journal!). Looks like PeerJ just has a standard flat list of authors, so not sure if that approach would be compatible.
I also agree that beyond whoever takes the lead being first author (either @cboettig or me, I guess), trying to order based on contribution (or need) becomes tricky and perhaps not fair/equitable. For my own case, other than the coveted lead author position, I don’t think position will matter too much—it’s a paper, and potentially one with good impact.
Ashley E. Sands
@ashleysa
It's still just a flat list -- the two sets are smushed together like one normal author list -- you determine the order like any other article. It would depend on your community if you knew how to "read" the ordering -- but sounds like most communities here it doesn't matter. But again, don't want to force a crazy idea on anyone.
Daniel S. Katz
@danielskatz
we’re going across communities, so we need to fall back to the least common elements, which is either alphabetical or significant
Matt Jones
@mbjones
on another topic -- was the unit test framework using the json-ld library in ruby loading the context without error before?
it currently is failing, seemingly because of a CORS header error on the context file
Matt Jones
@mbjones
NM, I figured it out -- some syntax typos had been introduced in the schema during a PR -- all passing again
Ashley E. Sands
@ashleysa
@cboettig So I think we've laid out all the authorship potentials. @danielskatz has a good point on alphabetical for simplicity (and because it seems to make sense to all research communities). Does that feel okay for @mbjones and @kyleniemeyer? If so, I'm okay with it.
Kyle Niemeyer
@kyleniemeyer
Yes, I agree that authorship should be alphabetical, other than the first author (whoever that is)
Carl Boettiger
@cboettig
Lots of people have made lots of different kind of contributions to the paper and broader ideas here. None of us believe these contributions are either exactly equal nor do we believe that they can be meaningfully rank-ordered in a single dimension. Thus I would prefer any decision that does not imply that we believe either of these fictions. I am perfectly fine with a hybrid order that is not alphabetical but also not a strictly ordered list from 1-17.
Kyle Niemeyer
@kyleniemeyer
Well said, @cboettig—at this point, does anybody prefer a model other than lead + alphabetical?
Sorry, I sent that message before finishing it
... Ok, this is an iOS gitter app problem... What
Kyle Niemeyer
@kyleniemeyer
alright, I give up for now.
Kyle Niemeyer
@kyleniemeyer
sorry for the jumble of messages, the iOS app was giving me problems last night… randomly sending messages before I finished typing with apparently no ability to edit
I don’t think I have anything more to contribute on the authorship discussion :smile:
Abigail Cabunoc Mayes
@acabunoc
oh yeah, i on iOS if you close the app it sends your current message
@danielskatz That’s the model previously called “Jisc” in the CodeMeta crosswalk (but actually the RRR project from STFC/St Andrews).
Daniel S. Katz
@danielskatz
Great. After missing the first day, I never did catch up on the actual table.
Daniel S. Katz
@danielskatz
I remember starting the codemeta paper in a google doc, but I thought the intro section at least was brought into latex by Matt or Carl. But we now seem to be in .Rmd
Am I misremembering? Are we just going to do this in Rmd?