---
title: "Personal stories - Authorship on Interdisciplinary Projects"
source: The Turing Way
source_url: https://github.com/the-turing-way/the-turing-way
licence: CC-BY-4.0
domain: data-and-analysis
subdomain: turing-way
date_added: 2026-04-25
---

(cm-aa-stories-interdisciplinary)=
# Personal stories - Authorship on Interdisciplinary Projects

## Federico Nanni and Mariona Coll Ardanuy - Living with Machines

[Living with Machines](https://livingwithmachines.ac.uk/) is a research project that rethinks the impact of technology on the lives of ordinary people during the Industrial Revolution.

It brings together an interdisciplinary group of researchers from a range of disciplines to create research methods, tools and data. They are working to change perceptions of how collaborations can be done and in doing this are discovering and working through some interesting challenges, including the issue of academic authorship. 

### Find out more about their work below:

**Federico Nanni:**
* ORCID: [0000-0003-2484-4331](https://orcid.org/0000-0003-2484-4331)
* X (formerly Twitter): [f_nanni](https://twitter.com/f_nanni)
* GitHub: [fedenanni](https://github.com/fedenanni)

**Mariona Coll Ardanuy**
* ORCID: [0000-0001-8455-7196](http://orcid.org/0000-0001-8455-7196)
* GitHub: [mcollardanuy](https://github.com/mcollardanuy)

**1. What is the *normal* practice of authorship for academic papers in your discipline? or used to be the normal practice?**

We are an interdisciplinary project and therefore bring with us the usual practices of authorship from two distinct disciplines: Computational linguistics and the Humanities (History). This makes it trickier when trying to decide how to tackle authorship on our publications. 

Some of our team are Computational linguists, which is a scientific field concerned with modelling language computationally. In the project, we use natural language processing that is the engineering side of Computational linguistics. We are used to working on papers that have a team of authors and papers are produced and published at pace. 

Other team members are from Humanities disciplines where sole author papers are common and are even required for career progression. The pace of publication in humanities is much slower. 

These two different approaches to authorship make it very hard to establish who should be an author or who should just be acknowledged. It is also difficult to work out who contributed the most, therefore establishing a ranking order of authors for papers, as we all have different roles in the project that are equally important to the overall goals. 

The publications we have published so far are more focused on the computational linguistics side of the project and therefore we have been generous with authorship for the whole team. This is due to the acceptance in computational linguistics that a team would have worked together to achieve this work. 

However, when writing more historically based papers we may need to consider that some of our team members need sole author publications and that adding authors onto these papers devalues the perceived prestige of the paper for them. In this case, we will be careful to fully cite our previous technical papers and acknowledge all of the team in an acknowledgement section.  


**2. When did you discuss authorship in your project?**

We started this process early but did not make much progress really until the first major paper of the project was about to be submitted. We then had to decide how to properly credit everyone in our team and it was driven by the need to get it done.

**3. Who had the discussion of authorship in your project?**

Everyone was involved in the discussions about authorship in meetings led by the Principal Investigator - Professor Ruth Ahnert. All our voices were listened to in these discussions and the approach to authorship in the project had good intentions from the start.

The discussions were very interdisciplinary as the project has a lot of postdoctoral researchers that all bring with them expert knowledge. 

**4. What approach have you decided to take in your project?**

We adopted the [CRediT taxonomy](https://casrai.org/credit/) to better present each author's contributions to the work. However, we felt it does not cover all the roles in our project so we adapted it. We felt that some of the categories were a bit vague and we wanted to be specific about the roles played by our team members. 

The categories that we added were implementation, reproducibility, interpretation, historical analysis and annotation. 

We encountered an issue with the roles that were not being perceived equally, such as conceptualisation and supervision being seen as having more prestige than other roles. Therefore, even when trying to acknowledge team members contributions more inclusively there are still problems that arise. 

We decided to produce a cover page for the pre-print of our first methods paper. We wanted to reflect our thinking about moving away from an author list and raise the curtain on roles that are often hidden in research projects. 

The cover page makes the jobs on the project more explicit, you therefore do not presume what the authors do as you would with a list. 

You can find out more about this in our blog - [Highlighting authors' contributions and interdisciplinary collaborations in Living with Machines](https://livingwithmachines.ac.uk/highlighting-authors-contributions-and-interdisciplinary-collaborations-in-living-with-machines/).

As we are trying to challenge how things are usually done, we were expecting this approach to bring conflicts and difficult discussions. Everyone came to this project with a similar mindset and this helped us to resolve any issues. 

**5. How have you gone about this practically?**

We used a Google doc to send around the CRediT taxonomy and everyone could fill in their own name under the different categories. 

We did find that everyone had different opinions - some people did put themselves in many categories and others would only put their name in one when they should have got credit for more. 

This meant that there had to be a degree of moderation when finalising the list of contributions.

**6. What have been the problems with doing this?**

The cover page was a statement that was put in our pre-print to try to solve the issue of assigning contributions fairly and the need for a list of authors but it was a footnote in the final published article. Therefore, there still had to be a list of authors, and a first author for publication. 

The main author, Mariona, was easy to decide as she had been the main writer and lead in everything to do with that paper but after that the order of authors was difficult. 

Some team members don't have the same need for publications as postdoctoral researchers because they hold permanent positions or work in areas where other types of outputs, such as code, are more important. This adds another layer of consideration that needs to be addressed when discussing the author list. 

There are also issues with assigning corresponding authors as in some fields this carries a perception of supervision or seniority in the team. In our case, it was just who was best to contact to find out more about the project. 

**7. How are you approaching the writing of the papers?** 
    
We had one person leading on a publication. They defined the structure, had an understanding of what was expected by the journal in terms of structure and formatting, they split up the paper into sections for different people to write and then everyone could write their parts. Then one person edited this work. It does need one person to edit the whole paper so they can have an idea of the overall flow and structure. 

This approach worked well for the technical papers we have written.

**8. What collaborative tools are you using for the writing and projects?**

We are using Overleaf, which is a LaTex based writing software, but I think some people are using Google docs for collaborative writing. 

*This interview was conducted by Emma Karoune. We would like to thank Federico and Mariona for the useful discussions about academic authorship, and for commenting on this personal story and the wider academic authorship chapter.*
