-
Notifications
You must be signed in to change notification settings - Fork 0
/
intro.qmd
24 lines (12 loc) · 5.11 KB
/
intro.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
# Introduction
The STAPLE mission: *Project Management* software that allows you to *document* your research project to improve *transparency*.
As researchers, we need to focus on the big picture - the overarching goals of a project, timelines, theory, hypotheses, and more. We then need to understand the smaller goals and tasks necessary to achieve the big picture. Researchers are often taught how to run projects, collect data, analyze that data, and write a paper summary. Training in project management is learned by example through the research lab, depending on the supervisor, and often not directly taught. Each project often involves special needs and circumstances, and the addition of even one more local collaborator can create complexity with multiple moving parts.
Research shows that the number of co-authors and collaborators on research projects is increasing over time. The globalization of research, the Internet, and software tools for collaboration (Zoom, GitHub, Google, etc.) has improved our ability to work together on new ideas. Large-scale collaboration has been encouraged to improve the diversity of participants, researchers, and cultures represented in data. Once we add other people (with different lab cultures and expectations!), institutions, geopolitical regions, and languages - the complexity of a research project also increases.
*So why do we need software*?
Project management software exists: Asana, Monday, Clickup, and Trello for example. These products were designs based on project management templates that are often business focuses. Research projects have their own unique and special needs that do not fit neatly into business models. Large-scale teams have found success treating a research project with many smaller teams as a classroom - but software designed for educational purposes is also not completely compatible with research project goals and management. STAPLE is designed for scientists by scientists with input from important stakeholders including funders, librarians, journals, and more.
*So what's the deal with documentation*?
In tandem with the encouragement for interdisciplinary, diverse teams, researchers have begun to focus on the improvement of science through transparency and sharing. The Transparency and Openness guidelines (https://www.cos.io/initiatives/top-guidelines) establish ideals for projects to be reproducible, open, and transparency through data sharing, code/analysis sharing, materials sharing, pre-registration, and replication. Journals require different levels of sharing for publication, which has pushed researchers to begin to implement these practices. However, the simple sharing of data, code, and materials does not make them FAIR: Findable, Accessible, Interoperable, and Reusable. Simple sharing of data does not necessarily allow someone to find that data in relation to the research project, or allow a researcher to know what `V1` means in the data, or even reuse part of the data.
Creating adequate documentation for the reuse of any output from a project can be difficult. There are often no clear standards, the work can be time consuming, and is often left to the end of a project when important details may have been forgotten. STAPLE is designed to encourage you to document information along the way and to provide guidance with what you should include with each document. As you complete specific task, such as create your materials for a study, you will be able to link your project to those materials and include information to interpret and understand those documents. We provide a set of minimum documentation standards for multiple types of documents - and the ability for you to include extra information if your field has set standards.
*Ok, so that's transparent*?
STAPLE allows you to track and run your project - and then include research outputs from that project. Each step of the way, STAPLE collects data about who did what and when. If you are the only person working on a project, it's simple: you will export a final project timeline that includes information about each step of the project, each output, and the documentation needed to make those outputs useful. If you work with other people, STAPLE will allow you to assign tasks to those individuals (or teams of individuals!) to complete as part of the project management functionality. At the same time, STAPLE tracks their work and creates a project timeline that shows that they completed a task for the project.
This component of the software was designed to align with contributorship models of research - instead of "authorship", each person receives credit for the components they contributed to the project. Each field has different standards for authorship, and many individual's work may be unacknowledge due to those cultures. Using STAPLE, their work would be credited, even if they did not earn final "authorship" on a publication. This output is also useful for defining contributions into systems such as CRediT (https://credit.niso.org/) - where each person's role is binned into categories. By linking each role to specific tasks, we can transparently show what each role means to a specific project.