DocMaps is a framework for representing the editorial processes used to create journal articles, preprints, peer reviews, and other documents in a machine-readable, extensible, interoperable format. This roadmap is intended to be a general overview of DocMaps’ project goals. It will provide a high-level list of social/technical projects regarding what we're thinking about, what we've prioritized, what we're currently working on, and what we've done.
We use GitHub to track sprints of work and document up-to-date lists of features. If you have a specific bug to report or a feature request, you can add a new issue to a repository in the DocMaps project.
Last updated: 27 February 2023
DONE | IN PROGRESS | ON DECK | FUTURE |
Pilot with eLife, EMBO, and CSHL | Build SDK | Discovery Services Dashboard | Services and Support |
Improve Process and Documentation | Expanding DocMaps Implementation Group | ||
Platform Community Assessment | Endorsements & Integration with Community Standards | ||
Preprint Review Groups User Research | DocMaps Governance |
The initial pilot of DocMaps sent information about community preprint evaluations from eLife’s Sciety and EMBO’s Early Evidence Base to CSHL Press’s biorxiv and medrxiv. This pilot created 5,000+ DocMaps for preprints related to biology research. In addition to giving various presentations during the pilot process, we wrote retrospective documentation about DocMaps implementation between Sciety, Early Evidence Base, and bioRxiv.
Based on conversations with the DocMaps Technical Committee and Pilot Working Group, as well as various community groups, preprint server and review infrastructure developers, and aggregators, we are developing a software development kit (SDK) for producing and consuming DocMaps. The SDK will facilitate DocMaps implementation for developers interested in integrating this framework.
With the pilot completed, we will revise docmaps.knowledgefutures.org to increase transparency regarding the efforts of DocMaps. In addition to the developer documentation from the SDK, this documentation will include definitions, vocabulary, implementation issues, governance structure, and ongoing updates with the project to better support communities and stakeholders.
In our interest to expand DocMaps to previously identified aggregators and preprint servers, we will invest in conversations with potential collaborators in the preprint publishing ecosystem to identify integration needs, complexities and challenges, as well as what KF can support in these collaborations. As a result of these conversations, we plan to identify additional and implementation agreements for integrating DocMaps into other platforms.
Working with the DocMaps Implementation Group and key advisors, we will coordinate user interviews with review groups. These conversations will help the DocMaps team to better understand review processes, priorities, and potential user visualization tools.
Our pilot has increased the number and kinds of evaluations displayed alongside preprints, providing greater visibility and credibility. Interest in preprint evaluation among authors and reviewers has risen as a consequence, demonstrated by the growth of both the number of curators on Sciety and EEB and the number of preprint reviews. This dashboard will serve as a way to identify existing DocMaps, learn how to access DocMaps from partner platforms, and assess the capture of preprint reviews.
Pilot DocMaps with new collaborators, we will work to expand our implementation group to understand new challenges and opportunities in the creation/consumption of DocMaps and the display of peer review status on preprint pages. We plan to build DocMaps integrations with/for preprint review platforms, aggregators, or preprint servers with open-source codebases or accessible APIs.
In order to support efforts from a wider range of publishers, we are working to secure endorsements and mapping with other community standards. We will work with community standards groups to facilitate the creation of DocMaps integrations with emerging standards like JATS4R, PrEF, NISO Peer Review Terminology, Project Notify, etc. This is a key step in sustainability within the publishing ecosystem and in conversation with existing community data standards.
As DocMaps implementation develops across platforms, we want to convene developers and other stakeholders. The DocMaps Stakeholders Forum will be an ongoing series of calls for developers/organizations interested in/working with DocMaps. These calls will be entirely driven by the user community. The goal is to create a space for discussion that will enable practitioners to connect with one another and identify common denominators, issues, and roadblocks that affect users across different organizations.
Our pilot has increased the number and kinds of evaluations displayed alongside preprints, providing greater visibility and credibility. Interest in preprint evaluation among authors and reviewers has risen as a consequence, demonstrated by the growth of both the number of curators on Sciety and EEB and the number of preprint reviews. As the DocMaps Implementation Group continues to grow, we plan to create adoption guides, best practices, and other sources of documentation to sustain DocMaps within the publishing ecosystem.