Ten simple rules for making a vocabulary FAIR

We present ten simple rules that support converting a legacy vocabulary—a list of terms available in a print-based glossary or in a table not accessible using web standards—into a FAIR vocabulary. Various pathways may be followed to publish the FAIR vocabulary, but we emphasise particularly the goal of providing a globally unique resolvable identifier for each term or concept. A standard representation of the concept should be returned when the individual web identifier is resolved, using SKOS or OWL serialised in an RDF-based representation for machine-interchange and in a web-page for human consumption. Guidelines for vocabulary and term metadata are provided, as well as development and maintenance considerations. The rules are arranged as a stepwise recipe for creating a FAIR vocabulary based on the legacy vocabulary. By following these rules you can achieve the outcome of converting a legacy vocabulary into a standalone FAIR vocabulary, which can be used for unambiguous data annotation. In turn, this increases data interoperability and enables data integration.     

Ten simple rules for doing a postdoc in pharma

Postdoctoral programs in the pharmaceutical and life science industry offer opportunities for personal and professional development, if you know why to join, what to expect, and how to prepare.     

Ten simple rules for establishing a mentorship programme

In recent years, a wide variety of mentorship programmes targeting issues that cannot be addressed through traditional teaching and learning methods alone have been developed. Mentoring plays significant roles in the growth and development of both mentors and mentees, and the positive impacts of mentoring have been well documented. Mentorship programmes are therefore increasingly being implemented in a wide variety of fields by organisations, academic institutes, businesses, and governments. While there is a growing body of literature on mentoring and mentorship programmes, gaining a clear overview of the field is often challenging. In this article, we therefore provide a concise summary of recommendations to consider when designing and establishing mentorship programmes. These recommendations are based on the collective knowledge and experiences of 4 different emerging and established mentorship programmes and can be adapted across various mentorship settings or contexts.     

Ten simple rules on writing clean and reliable open-source scientific software

Functional, usable, and maintainable open-source software is increasingly essential to scientific research, but there is a large variation in formal training for software development and maintainability. Here, we propose 10 “rules” centered on 2 best practice components: clean code and testing. These 2 areas are relatively straightforward and provide substantial utility relative to the learning investment. Adopting clean code practices helps to standardize and organize software code in order to enhance readability and reduce cognitive load for both the initial developer and subsequent contributors; this allows developers to concentrate on core functionality and reduce errors. Clean coding styles make software code more amenable to testing, including unit tests that work best with modular and consistent software code. Unit tests interrogate specific and isolated coding behavior to reduce coding errors and ensure intended functionality, especially as code increases in complexity; unit tests also implicitly provide example usages of code. Other forms of testing are geared to discover erroneous behavior arising from unexpected inputs or emerging from the interaction of complex codebases. Although conforming to coding styles and designing tests can add time to the software development project in the short term, these foundational tools can help to improve the correctness, quality, usability, and maintainability of open-source scientific software code. They also advance the principal point of scientific research: producing accurate results in a reproducible way. In addition to suggesting several tips for getting started with clean code and testing practices, we recommend numerous tools for the popular open-source scientific software languages Python, R, and Julia.