analyzing form of contribution?

[mbnebel]

Hello! I used the citation diversity codebook to evaluate a reference list before submitting a paper last year, and I just updated the analysis after a round of revisions. I'm working on a tutorial for the rest of the lab to use the tool, and I'm curious if there are any plans to look more closely at the forms of contribution cited stratified by predicted gender or race.

[dalejn]

Hi! That's great to hear! Could you expand a little more on what you mean by "forms of contribution?" Do you have in mind something like this? https://www.elsevier.com/authors/policies-and-guidelines/credit-author-statement

[mbnebel]

My initial interpretation of "forms of contribution" was a call to expand the types of materials I consider worth citing, like blog posts, tutorials, and software packages. And I wondered how citations to these different types of work might differ by predicted gender or race.

But you bring up an interesting question about how the types of contributions we consider worthy of authorship might differ by predicted gender or race - yes/no?

[dalejn]

Sorry about the late reply--I was out of town. I agree it'd be interesting to evalaute the types of contribution!

There's a few ways I can think of to get at this and I'm curious if you had one in mind, too.

One way is by the parser we currently use to read through the .bib files. Since BibTeX can accomodate many mediums such as blogs, tutorials, and software packages (e.g. see BibTeX Database Entry Types), we can use the parsing library to sort through the entries and grab the types of entry (the ENTRYTYPE field). We can then calculate the predicted breakdowns filtered by entry type. This method is limited in that it depends on the original .bib file to have accurate, well-curated entry types and that some entry types like "misc" don't easily translate to any intuitive category.

Is this something you'd like to give a go at contributing? Happy to include it and am flexible how you'd like to do it if you're interested (e.g. editing within an instance of the notebook and sending over any new code for us to test out or a pull request as described in the FAQ).