Tag: Self-Archiving

  • Registry of Open Access Repository Mandates and Policies: A ROARMAP Guide for Research Administrators

    When a research office needs to check whether a funder requires immediate deposit or permits a twelve-month embargo, guesswork is not good enough. The registry of open access repository mandates and policies — known by its acronym ROARMAP — exists precisely to remove that guesswork. Maintained by the School of Electronics and Computer Science at the University of Southampton, it is a searchable, international catalogue of the open access mandates that universities, research institutions and funders have adopted, and it remains one of the few places where those policies can be compared side by side rather than tracked down one funder website at a time.

    This matters more in 2026 than it did a decade ago. Funder mandates have multiplied, cOAlition S members continue to refine Plan S implementation, and — as a June 2026 German constitutional ruling shows — even settled mandates can be challenged in court. Research administrators, library staff and compliance officers need a single reference point that tracks all of it. ROARMAP is that reference point.

    What ROARMAP catalogues, and why it matters

    ROARMAP began life in 2003 as the Institutional Archives Registry, built by the EPrints team at the University of Southampton. It was renamed the Registry of Open Access Repositories Mandatory Archiving Policies in 2006, then adjusted again, settling on its current name — Registry of Open Access Repository Mandates and Policies — around 2014. Throughout those renamings, its purpose stayed constant: track every publicly documented policy that requires or encourages researchers to make peer-reviewed outputs openly accessible, usually by depositing a copy in a repository.

    ROARMAP has a companion registry, ROAR (the Registry of Open Access Repositories), which indexes the repositories themselves rather than the policies that govern them. The distinction trips people up regularly, so it is worth setting out clearly alongside a third commonly confused resource, OpenDOAR.

    Registry What it indexes Typical use case
    ROARMAP Open access mandates and policies from institutions and funders Checking what a funder or institution requires
    ROAR Open access repositories themselves — location, size, growth Finding where a repository is hosted
    OpenDOAR Curated, vetted directory of repositories and their technical metadata Selecting a compliant repository to deposit into

    Entries in ROARMAP are not uniform in strength. Some record a simple recommendation to self-archive; others are mandatory policies where compliance is tied to continued grant funding — the sanction that gives a mandate real teeth. As of the last widely cited published count, ROARMAP had catalogued policies from more than 520 universities and over 75 research funders worldwide, a figure that has continued to grow as more institutions formalise their open access requirements.

    How cOAlition S members’ policies are catalogued

    cOAlition S is the group of research funders — including national funders, charitable foundations and the European Commission — that came together in 2018 to implement Plan S, the requirement that publicly funded research be made immediately open access without embargo. Because cOAlition S members are funders rather than repository operators, their individual mandates are exactly the kind of entry ROARMAP was built to hold.

    Each cOAlition S member’s policy is entered as a discrete record, so an administrator can look up, for example, what a specific national research council requires on licensing (typically CC BY), acceptable routes to compliance (Gold, Green with a zero-embargo repository deposit, or a transformative agreement), and how the policy interacts with the funder’s own compliance-monitoring tools, such as the Journal Checker Tool. Because ROARMAP predates Plan S by more than a decade, it also preserves the pre-2018 policy text for many of these funders, which is useful when institutions need to establish exactly when a requirement changed.

    This is a genuine information gain over simply reading each funder’s website individually: ROARMAP lets an administrator filter by funder type, country and adoption date, surfacing patterns — such as clusters of European funders tightening embargo terms in the same policy cycle — that are invisible from any single funder’s own page.

    Using the registry to compare institutional and funder mandates

    For day-to-day compliance work, ROARMAP is used less as a browsing tool and more as a lookup and benchmarking tool. A typical workflow for a research administrator looks like this:

    • Search by country or institution name to confirm whether a specific university has a formal mandate, and since when.
    • Filter by policymaker type — funder versus institution — to separate overlapping obligations on a single researcher.
    • Check the deposit timing and permitted embargo period recorded against each policy.
    • Note the required manuscript version — preprint, accepted manuscript or version of record.
    • Compare licensing requirements (commonly CC BY) where the policy specifies one.
    • Benchmark a draft institutional policy against comparable peer institutions before it goes to committee.

    This benchmarking use case is one of ROARMAP’s most practical applications. Rather than drafting an institutional open access policy from a blank page, a policy officer can pull several comparable universities’ mandates from the registry, line up their deposit windows and enforcement mechanisms, and use that comparison to justify the strength of a proposed new policy to institutional leadership.

    What is an open access repository?

    An open access repository is a freely accessible digital archive where researchers self-archive peer-reviewed articles, preprints or accepted manuscripts so readers can access them without a paywall. Universities run institutional repositories; funders and disciplines run subject-based ones. ROARMAP catalogues the policies requiring deposit — not the repositories themselves.

    How does OpenDOAR differ from ROARMAP?

    OpenDOAR is a curated directory listing vetted open access repositories and their technical characteristics, while ROARMAP lists the mandates and policies that require deposit into those repositories. Administrators typically use OpenDOAR to identify a compliant repository, then check ROARMAP to confirm whether deposit is compulsory and on what terms.

    What is self-archiving, and how do ROARMAP-listed policies define it?

    Self-archiving — the “Green” route to open access — means an author deposits a manuscript into a repository alongside, or instead of, publishing openly with a journal. Policies catalogued in ROARMAP typically specify the deposit timing, permitted embargo length, and which manuscript version satisfies the mandate.

    What are the drawbacks of relying on open access mandates?

    Mandates catalogued in registries such as ROARMAP vary widely in enforcement: some merely encourage deposit while others tie compliance to grant payment. Weak or unmonitored policies show low actual deposit rates, embargo terms conflict across funders, and legal challenges — as seen in Germany in 2026 — can unsettle even long-established mandates.

    What the changing legal landscape means for research administrators

    ROARMAP’s value is not static, and 2026 has already supplied a reminder of why. In June, Germany’s Federal Constitutional Court struck down a state-level bylaw at the University of Konstanz that would have compelled researchers to exercise their statutory secondary-publication right — ruling that regulating copyright through employment or institutional statute conflicted with the federal government’s exclusive legislative competence over copyright law. The University of Konstanz noted afterwards that the ruling changed little in practice, because the great majority of its researchers already deposit voluntarily. But the case is a useful illustration for administrators elsewhere: a mandate’s formal status, its legal basis and its actual compliance rate can diverge, and a registry entry captures only the first of those three.

    That gap between formal mandate and practical uptake is exactly why registries such as ROARMAP function as compliance infrastructure rather than mere reference material. Institutions revising their own open access policy — whether to align with cOAlition S requirements, respond to a national research assessment exercise, or pre-empt a legal challenge — need a documented, dated record of what comparable institutions and funders actually require, not an assumption based on the last policy a colleague happened to read. For a wider view of how these obligations sit alongside contributorship and compliance frameworks more broadly, CASRAI’s research administration resources and dictionary of research terms provide further grounding.

    As funder policies continue to tighten and jurisdictions test the legal limits of mandated deposit, expect ROARMAP’s role to shift from a static archive towards a living reference that research offices consult routinely, alongside compliance checkers and repository directories, whenever a grant agreement, tenure case or institutional policy review depends on knowing exactly what an open access mandate actually requires.

  • Archiving the Author Accepted Manuscript (AAM): Pathways to Green Open Access

    1. Introduction to the Role of Author Accepted Manuscript in Scholarly Infrastructure

    In the contemporary landscape of global science, open research practices, and institutional data governance, establishing robust standards is crucial. The integration of Author Accepted Manuscript represents a landmark advancement in addressing long-standing hurdles in scholarly communication, administrative reporting, and metadata curation. This extensive guide provides an expert-level breakdown of the operational frameworks, specifications, and systemic requirements surrounding Author Accepted Manuscript in 2026.

    As academic funders and research ministries worldwide enforce increasingly rigid compliance pathways, universities must transition from ad-hoc administrative workflows to unified, persistent-identifier-driven schemas. Implementing Author Accepted Manuscript is not merely a technical adjustment; it is a strategic necessity that secures institutional research visibility, ensures frictionless metadata reporting, and compounds the impact of scientific investments.

    2. Technical Architecture and Core Specifications

    Underpinning the deployment of Author Accepted Manuscript is a set of rigorous, machine-actionable specifications designed to operate seamlessly across diverse platforms. This environment relies heavily on defining the Author Accepted Manuscript (AAM) and its distinction from the Preprint and Version of Record (VOR). By establishing clear, standardized data exchange layers, organizations can bypass the siloed architectures that have traditionally plagued research information networks.

    A key focus of these specifications is the preservation of structural metadata integrity. This is achieved by mapping data payloads to recognized open vocabularies, such as Dublin Core, Schema.org, and custom JSON-LD graphs. This ensures that every scientific output—be it a journal article, a software version, or an administrative record—carries citable provenance tags, enabling automated indexing and cross-referencing by global citation engines such as OpenAlex and Crossref.

    3. Institutional Challenges, Workflows, and Solutions

    While the administrative and scientific benefits of Author Accepted Manuscript are indisputable, the practical deployment across universities and libraries reveals significant hurdles. Major friction points include navigating publisher-enforced embargo periods using Sherpa Romeo and deposit workflows in institutional repositories. Faculty reluctance, legacy software limitations (such as outdated CRIS databases), and the high administrative cost of manual curation represent substantial barriers to widespread compliance.

    Overcoming these implementation bottlenecks requires a systemic, top-down commitment to administrative automation. Institutions must deploy modern API middleware to coordinate data transfers between local enclaves and global public registries, eliminating manual data-entry redundancy. Furthermore, university promotion and tenure committees must update their evaluative rubrics to formally credit researchers for complying with these modern curation workflows, establishing a cultural positive-feedback loop.

    4. Technical Evaluation and Integration Matrix

    Integration Domain Primary Objective Core Interoperability Standard Friction Mitigation Strategy
    Persistent Identification Ensure permanent, citable links across registries. Unique URI / DOI Resolve Systems Implement automated metadata harvesting on ingest.
    Metadata Exchange Frictionless transfer between CRIS and repositories. JSON-LD / XML Schema Mapping Deploy standardized REST APIs with OAuth 2.0.
    Compliance Auditing Track, verify, and report on policy adherence. Standardized SQL / GraphQL Querying Generate real-time compliance scorecards for PIs.

    5. Five-Step Institutional Implementation Roadmap

    • Step 1: Institutional Alignment & Sign-off — Establish an official cross-departmental committee representing the library, IT services, and the research office to draft the institutional deployment charter for Author Accepted Manuscript.
    • Step 2: API & Schema Mapping — Audit existing repository databases and map local metadata schemas to match the international JSON-LD specifications required for Author Accepted Manuscript.
    • Step 3: Middleware Integration & SSO — Configure enterprise middleware layers to handle automated data harvesting and synchronize access using Single Sign-On (SAML/Shibboleth).
    • Step 4: Training & Support Networks — Deploy interactive workshops, dedicated helpdesks, and online documentation to educate researchers, metadata curators, and administrative staff.
    • Step 5: Automated Verification & Auditing — Launch real-time validation checks and annual data-quality audits to measure compliance rates and automatically identify and correct orphaned records.
  • Sherpa Romeo: Decoding Journal Open Access and Archiving Policies

    Introduction

    The strategic advancement of Sherpa Romeo: Decoding Journal Open Access and Archiving Policies is transforming how modern academic institutions catalog, preserve, and evaluate scientific outputs. In an era dominated by rapid open-science transitions and complex funding mandates, establishing unified metadata frameworks, secure persistent identifiers, and collaborative repositories is essential for ensuring institutional transparency and global research discoverability.

    Analyzing the Strategic Role of Sherpa Romeo in Research Ecosystems

    The implementation of Sherpa Romeo has emerged as a cornerstone in modern scholarly metadata and institutional reporting. By providing structured, standardized, and machine-actionable frameworks, Sherpa Romeo resolves long-standing issues relating to identity disambiguation, resource tracking, and global accessibility. Research administrators and funding bodies increasingly mandate the adoption of Sherpa Romeo-compliant workflows to automate report consolidation, minimize administrative burdens, and ensure complete transparency of project outcomes on a global scale.

    Technical Implementation Frameworks and Cross-System Interoperability

    From an engineering perspective, integrating Sherpa Romeo relies on standardized APIs, structured XML or JSON-LD metadata schemas, and secure communication protocols. When integrated into university repositories, library catalog systems, and national research databases, Sherpa Romeo acts as an unbreakable link that maps scholarly effort across disparate platforms. This cross-system interoperability is crucial for constructing the ‘Scholarly Graph’, which connects researchers, publications, funding records, and clinical datasets in a machine-readable format.

    Overcoming Policy Friction and Fostering Cultural Adoption

    Despite the technical advantages of Sherpa Romeo, institutional adoption is frequently hindered by policy friction, lack of specialized administrative training, and cultural inertia among academic staff. To overcome these hurdles, research offices must implement comprehensive outreach programs, establish centralized library support services, and formally write Sherpa Romeo compliance into promotion, tenure, and recruitment rubrics, ensuring that researchers are directly rewarded for contributing to a connected, transparent scholarly record.

    Key Evaluation and Interoperability Matrix

    Technical Dimension Core Standard / Protocol Implementation Action Primary Operational Benefit
    API Integration RESTful Web APIs / OAuth 2.0 Configure automated client credentials and secure token exchanges. Enables real-time data sync and eliminates manual data entry errors.
    Metadata Mapping JSON-LD / XML Schemas Map localized fields to recognized Dublin Core or Schema.org namespaces. Ensures global discoverability and machine-readability across indexes.
    Preservation Policy OAIS / CoreTrustSeal Establish long-term digital escrow and storage replication models. Guarantees continuous asset access and data longevity under compliance rules.

    Actionable Checklist for Implementing Sherpa Romeo

    • Review and audit existing institutional workflows for Sherpa Romeo compatibility.
    • Configure administrative APIs and establish secure client credentials.
    • Provide targeted training sessions for academic authors and research managers.
    • Verify metadata completeness and standardize mappings to global namespaces.
    • Formally recognize compliance in departmental promotion and evaluation rubrics.