SEIPID Metadata Schema

Version 2.0

Xpertno Research Center

SEIPID Metadata Schema

Definitions, structures and requirements for describing scholarly platforms and their outputs consistently, supporting identification, citation, discovery, validation and metadata exchange.

Version 2.0

SEIPID: 004:xrc-ir:2026n2

Issued 13 November 2026

Lead editor: Nasir Razzaq

Xpertno Research Center

SEIPID Metadata Schema

Definitions, structures and requirements for describing scholarly platforms and their outputs consistently, supporting identification, citation, discovery, validation and metadata exchange.

Publication Detail

  • Version: 2.0
  • SEIPID: 004:xrc-ir:2026n2
  • Status: Active
  • Issue date:
  • Effective date:
  • Previous version: 1.0
  • Author: SEIPID
  • Publisher: Xpertno Research Center
  • Licence: CC BY 4.0

Contributors

How to cite

Online version: https://seipid.com/seipid-schema/v2.0

Contents

    1. Introduction

    1.1 About the SEIPID Metadata Schema

    SEIPID is a persistent identifier infrastructure for scholarly platforms and their outputs. The SEIPID Registry gives each registered journal, institutional repository, archive, scholarly press or event organizer a persistent Namespace Identifier (NiD), and each article, thesis, dataset, book, chapter or other output registered under it a persistent SEIPID.

    The SEIPID Metadata Schema is the common language behind every SEIPID record. It defines each field that describes a platform or an output: what the field means, how its value is written, which values are permitted and when it is required. A platform is described once, and each output carries the platform’s persistent NiD. The same definitions apply however a record is submitted.

    Metadata is supplied by the registering platform, which is responsible for its accuracy and completeness. Platforms are encouraged to provide all applicable metadata, including Recommended fields and relevant Optional fields. More complete metadata helps readers and services discover, interpret and connect scholarly platforms and their outputs.

    Each registered scholarly platform and output has its own public page in the SEIPID Registry. Public metadata is also provided in machine-readable form for search engines, scholarly indexes, reference managers and AI tools. Contributor and organization identifiers connect outputs with their contributors and institutions, while references identify the works they cite. Output citations are tracked in SEIPID Rasad, and output metrics are measured in SEIPID Idraak.

    The schema serves every subject and every kind of scholarly platform. It describes platforms and outputs for identification, citation and discovery; it does not replace an output’s full text or the specialist metadata a discipline may require. Account requests, platform verification and submission procedures are set out in the SEIPID Guidelines.

    Metadata should be recorded in the original language of the platform or output. Where that language is not English, English versions of the title, subtitle and abstract are recommended; English keywords may be added.

    This document describes version 2.0 of the SEIPID Metadata Schema. Version 1.0 remains available at https://seipid.com/seipid-schema/v1.0.

    1.2 How to cite this document

    SEIPID. (2026). SEIPID Metadata Schema (Version 2.0). Xpertno Research Center (SMC Pvt.) Ltd. https://seipid.com/004:xrc-ir:2026n2

    1.3 How to cite registered outputs

    Registered outputs may be cited in any citation style. The citation should include the output’s SEIPID as a link, written as https://seipid.com/ followed by the SEIPID.

    Example (APA):

    Akmal, S. (2025). Impact of graphic illustrations on English vocabulary acquisition in Pakistani dyslexic students. Xpertno International Journal of Interdisciplinary Research, 2(2), 1–19. https://seipid.com/001:xijir:2025n4

    1.4 What’s New in 2.0

    Version 2.0 was issued on 13 November 2026 and takes effect on 13 December 2026. New records may follow it from its issue date. From 13 December 2026, new records and updates to existing records follow version 2.0. Records registered under version 1.0 keep schemaVersion “1.0” until they are updated on or after 13 December 2026, when they follow version 2.0. The changes by field number are listed in Section 10.5.

    • Platform types: Scholarly Press and Event Organizer (NiD ending -eo); an Event Organizer registers each event as an output (P5).
    • Subjects: Broad Subject Areas (list 5.18) and Disciplines (list 5.19). Platform Subjects (P20) and Output Subjects (O17) are retired.
    • Retired fields: P44, P48–P52, O20.6, O20.8, O20.11, O20.14, O26, O35 and O49.
    • New fields: Platform Editorial Team (P53), Output Award Title (O29.4), AI Use (O55), Withdrawal Reason (O56), Event Type (O57), Event Mode (O58), Event Sub-themes (O59), External Publisher (O60) and Copy Version (O61).
    • Contributors: up to three affiliations for each contributor (O18.6).
    • Dates: the order of dates (Section 8.2); the Embargo End Date with the access models Embargoed and Delayed open access (O20.10); the Retracted Date and the Withdrawn Date assigned by the Registry (O20.12, O20.13).
    • Content types: Expression of Concern and further content types (list 5.12); parts and parent works (Section 7.2).
    • References: the reference list (Section 7.4).
    • Events: Event End Date (O51) and Event Type (O57) are Mandatory.

    2. Metadata Field Conventions

    2.1 Overview

    This section sets out the conventions used to present the fields of the SEIPID Metadata Schema: requirement levels, naming and numbering, and number of values. Section 3 sets out the platform fields, which describe a registered scholarly platform, and Section 4 sets out the output fields, which describe a scholarly output registered under that platform. Each section contains tables giving the full description and requirements for each field.

    2.2 Requirement levels

    Each field has one of four requirement levels:

    • Mandatory: the field must be present in the applicable submission or registered record. Any stated conditions determine when it applies.
    • Required if it exists: the field must be provided when the information exists for that platform or output. It may be omitted only when the information does not exist.
    • Recommended: the field may be omitted, but should be provided whenever possible.
    • Optional: the field may be provided to give a fuller description.

    Requirements apply to the specified platform or output type and the relevant stage of registration. Fields marked as assigned by the Registry are filled by the Registry at the stated stage.

    Each field’s requirement level is shown in its field entry.

    2.3 Naming and numbering

    Each field has a readable name, a permanent field reference number and a public JSON key.

    • The name describes the information the field holds, for example Output Original Title.
    • The field reference number identifies the field independently of its name or position in this document. Platform fields are numbered P1, P2, P3 and so on. Output fields are numbered O1, O2, O3 and so on.
    • Where a field consists of several parts, each part is numbered under the field. For example, Output Contributors is O18, Output Contributor Name is O18.2 and Output Contributor Role is O18.3. A part that has its own parts continues the same pattern: Output Contributor Given Names is O18.2.1.
    • The public JSON key is the case-sensitive name used to represent the field in JSON, for example outputOriginalTitle. It is shown with the field’s description.
    • Identifier fields use the identifier’s own name as their JSON key, for example nid, seipid, xpenid, orcid and ror.

    Field reference numbers are separate from document section numbers and public JSON keys. Rules for changes in later versions are set out in Section 10.

    2.4 Number of values

    Each field states how many values it may hold:

    • One value: at most one value may be supplied.
    • Multiple values allowed: more than one value may be supplied, subject to the field's stated limits.

    Whether a field may be omitted is determined by its requirement level and any applicable conditions. A field with multiple values may also set a minimum or maximum number, for example up to three disciplines, or three to seven keywords.

    Output Original Title is Mandatory with one value, so every applicable output record has exactly one original title. Output Contributors is Mandatory with multiple values allowed, so every applicable output record has at least one contributor, and more may be added.

    3. Platform Metadata

    3.1 Overview

    This section defines the metadata describing a registered scholarly platform. Table 1 contains the fields for every platform. Table 2 contains the fields that apply to particular platform types.

    3.2 Field descriptions: every platform (P1 to P27.7)

    Table 1: Fields for every platform
    No.FieldDefinitionValue specification
    P1Platform NiD Key: nid
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The persistent identifier of the registered scholarly platform.

    Format: Registration number of three or more digits, a colon, and the platform abbreviation in lower case with its type ending

    The Registry assigns the NiD when the platform is approved. The submitter does not supply it. The type ending is: none for a journal, -ir for an institutional repository, -arch for an archive, -p for a scholarly press and -eo for an event organizer. A NiD is never reassigned to another platform, including when management of the platform changes.

    Example: 001:xijir; 014:example-ir

    P2Platform Status Key: platformStatus
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The current standing of the platform in the Registry.

    Format: Controlled value

    The Registry sets and updates the status. A platform reports when it ceases publication or merges with another platform. A NiD is never deleted, and its public page remains available whatever its status. When the status is Merged, P26 identifies the platform it merged into; when it is Renamed, P26 identifies the new NiD.

    Allowed values: see list 5.1.

    Example: Active

    P3Platform Registration Date Key: platformRegistrationDate
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The date the Registry issued the platform’s NiD.

    Format: Date, YYYY-MM-DD

    Set when the NiD is issued and never changed. For a NiD issued after a change of title or abbreviation, this is the date of the change.

    Example: 2026-05-14

    P4Platform Status Date Key: platformStatusDate
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The date the current status took effect.

    Format: Date, YYYY-MM-DD

    The Registry updates it whenever P2 changes.

    Example: 2026-05-14

    P5Platform Type Key: platformType
    Level:
    Mandatory
    Values:
    One value

    The main category of the scholarly platform.

    Format: Controlled value

    Select the category that describes the platform’s main function. The type decides the subtypes available in P6, the fields in Table 2 that apply, and the content types its outputs may use. An Event Organizer gives only P1 to P16, P25 to P27 and P6; each event is registered as an output record (Section 6).

    Allowed values: see list 5.2.

    Example: Journal

    P6Platform Subtype Key: platformSubtype
    Level:
    Mandatory
    Values:
    One value

    The more specific category of the platform within its type.

    Format: Controlled value

    Select one subtype listed under the chosen type. Choose by the platform’s main function, not by its subject coverage. For a journal, the subtype states the journal’s focus.

    Allowed values: see list 5.3.

    Example: Interdisciplinary Journal

    P7Platform Original Title Key: platformOriginalTitle
    Level:
    Mandatory
    Values:
    One value

    The full title of the platform in its original language.

    Format: Text

    Record the title exactly as the platform publicly uses it, keeping its language and script. Record an English translation in P9 and any other or former title in P10.

    Example: Xpertno International Journal of Interdisciplinary Research

    P8Platform Abbreviation Key: platformAbbreviation
    Level:
    Mandatory
    Values:
    One value

    The short form of the platform’s title, usually the initial letters of its main words.

    Format: Letters and digits, 2–15 characters

    Supply the platform’s own abbreviation.

    Example: XIJIR

    P9Platform English Translated Title Key: platformEnglishTranslatedTitle
    Level:
    Recommended (when the title is not in English)
    Values:
    One value

    An English translation of the platform’s original title.

    Format: Text, English

    Translate the original title faithfully; do not create a new name. Omit when the original title is already in English.

    Example: Journal of Linguistic Research (original title in Urdu)

    P10Platform Other or Former Title Key: platformOtherOrFormerTitle
    Level:
    Optional
    Values:
    One value

    An alternative title, or a previous title, used by the same platform.

    Format: Text

    Supply one alternative or former title. When a registered platform changes its title or abbreviation, it receives a new NiD; the Registry records the previous title here on the new record and links the two NiDs through P26.

    Example: Journal of Language Studies

    P11Platform Website Key: platformWebsite
    Level:
    Mandatory
    Values:
    One value

    The official public website of the platform.

    Format: HTTPS URL

    Supply the platform’s own canonical home page, verified for this platform during registration. Do not use a social media page, or the organization’s general home page when the platform has its own site.

    Example: https://journal.example.org

    P12Platform Contact Email Key: platformContactEmail
    Level:
    Mandatory
    Values:
    One value

    The public address for official correspondence with the platform.

    Format: Email address

    Use a monitored address authorized for platform correspondence. It is public, and separate from contributor email (O18.9), which is restricted.

    Example: [email protected]

    P13Platform Country Key: platformCountry
    Level:
    Mandatory
    Values:
    One value

    The country where the platform’s responsible office is based.

    Format: Country (ISO 3166-1 code)

    Record the office that runs the platform, not the location of its hosting server.

    Example: Pakistan (PK)

    P14Platform City Key: platformCity
    Level:
    Mandatory
    Values:
    One value

    The city where the platform’s responsible office is based.

    Format: Text

    Record the city of the same office as P13.

    Example: Islamabad

    P15Platform Establishment Year Key: platformEstablishmentYear
    Level:
    Mandatory
    Values:
    One value

    The year in which the platform was established.

    Format: Four-digit year

    Use the documented founding year. Do not use the year of SEIPID registration.

    Example: 2023

    P16Platform Short Description Key: platformShortDescription
    Level:
    Mandatory
    Values:
    One value

    A brief factual account of the platform’s purpose, content and audience.

    Format: Text, 50–800 characters

    Write a plain factual description without promotional claims, rankings or unverified indexing statements.

    Example: A diamond open access journal publishing research on language, education and society.

    P17Platform Content Languages Key: platformContentLanguages
    Level:
    Mandatory (not for Event Organizers)
    Values:
    Multiple values allowed

    The languages of the scholarly content the platform publishes, deposits or preserves.

    Format: Language codes (BCP 47)

    Supply at least one language. Describe the content, not the language of the website.

    Example: en; ur

    P18Platform Subject Group Key: platformSubjectGroup
    Level:
    Mandatory for journals and scholarly presses; Optional for repositories and archives; not for Event Organizers
    Values:
    One value

    The broad knowledge area the platform covers.

    Format: Controlled value

    Select one broad subject area: the area of the platform’s main discipline. A platform covering several areas selects the area of its main discipline and names the others through P19.

    Allowed values: see list 5.18.

    Example: Social Sciences and Humanities

    P19Platform Disciplines Key: platformDisciplines
    Level:
    As P18
    Values:
    Multiple values allowed (1–3)

    The defined fields of study the platform covers.

    Format: Controlled values

    Select 1 to 3 disciplines from the discipline list. They may come from any area; at least one belongs to the area selected in P18, and the main discipline comes first.

    Allowed values: see list 5.19.

    Example: Linguistics; Education

    P20Platform Subjects Key: platformSubjects
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed (up to 3)

    Specific topics the platform covers, each within one of its disciplines.

    Retired in 2.0. Not supplied in records following version 2.0. Specific topics are described by each output’s keywords (O13). The definition below is that of version 1.0.

    Format: Subject term + discipline

    Supply up to 3 topics, each linked to one of the disciplines selected in P19.

    Example: Applied linguistics (Languages, Linguistics and Literature)

    P21Platform Content Licence Key: platformContentLicence
    Level:
    Mandatory for journals and scholarly presses; Optional for repositories and archives (only when the same for all content); not for Event Organizers
    Values:
    One value

    The licence under which the platform usually provides its content.

    Format: Controlled value

    Select the licence that normally applies. A work under a different licence records its own licence in O24.

    Allowed values: see list 5.20.

    Example: CC BY 4.0

    P22Platform Content Copyright Holder Key: platformContentCopyrightHolder
    Level:
    As P21
    Values:
    One value

    Who normally holds copyright in the platform’s content.

    Format: Holder category + name

    Select the usual holder category and give the holder’s name where known. A work with a different holder records it in O25.

    Allowed values: see list 5.21.

    Example: Author / Creator

    P23Platform Content Access Model Key: platformContentAccessModel
    Level:
    Mandatory (not for Event Organizers)
    Values:
    One value

    The access conditions that normally apply to the platform’s content.

    Format: Controlled value

    Select the usual model. It describes access for readers, not charges to authors, which are recorded in P34. A work with different access records it in O23. When the model is Open access and P34 is No fee, the Registry shows the platform as Diamond open access.

    Allowed values: see list 5.22.

    Example: Open access

    P24Platform Reference Style Key: platformReferenceStyle
    Level:
    Mandatory for journals and scholarly presses; not for repositories, archives or Event Organizers
    Values:
    One value

    The citation style the platform uses for references in its content.

    Format: Style name + edition

    Name one style and its edition where known. Each work’s references are recorded as published, in O34. Repositories, archives and Event Organizers give no platform style: each work keeps its own.

    Example: APA, 7th edition

    P25Platform External Links Key: platformExternalLinks
    Level:
    Optional
    Values:
    Multiple values allowed

    Links to the platform’s own records or official profiles on other services.

    Format: Service + HTTPS URL

    Each entry gives one service and one link to the platform’s own record or profile on that service, not to a search page.

    Allowed services: see list 5.10.

    Example: OpenAlex + link to the platform’s OpenAlex record

    P26Platform Related Platforms Key: platformRelatedPlatforms
    Level:
    Optional
    Values:
    Multiple values allowed

    Other platforms connected to this platform by continuation or merger.

    Format: Relation + NiD

    Each entry gives one relation and the related platform’s NiD. Give the title and website only when the related platform has no NiD. When P2 is Merged, a “Merged into” entry is required; when P2 is Renamed, a “Continued by” entry is required.

    Allowed relations: see list 5.5.

    Example: Merged into 001:example

    P27Platform Organization Key: platformOrganization
    Level:
    Mandatory
    Values:
    One value

    The organization responsible for publishing or managing the platform.

    Format: Group of parts

    Identify the publisher or managing organization, not the person or account submitting the record. Its details are given in P27.1–P27.7.

    Example: see P27.1–P27.7

    P27.1Platform Organization Name Key: platformOrganizationName
    Level:
    Mandatory
    Values:
    One value

    The full official name of the organization.

    Format: Text

    Use the name as legally or publicly used, without abbreviations.

    Example: Xpertno Research Center (SMC-Private) Limited

    P27.2Platform Organization Type Key: platformOrganizationType
    Level:
    Recommended
    Values:
    One value

    The kind of organization.

    Format: Controlled value

    Select the category that best describes the organization.

    Allowed values: see list 5.4.

    Example: University or college

    P27.3Platform Organization Website Key: platformOrganizationWebsite
    Level:
    Mandatory
    Values:
    One value

    The official website of the organization.

    Format: HTTPS URL

    Supply the organization’s own home page. It may differ from P11.

    Example: https://www.example.org

    P27.4Platform Organization Country Key: platformOrganizationCountry
    Level:
    Mandatory
    Values:
    One value

    The country where the organization is based.

    Format: Country (ISO 3166-1 code)

    Record it even when it is the same as P13.

    Example: Pakistan (PK)

    P27.5Platform Organization City Key: platformOrganizationCity
    Level:
    Mandatory
    Values:
    One value

    The city where the organization is based.

    Format: Text

    Record it even when it is the same as P14.

    Example: Islamabad

    P27.6Platform Organization Office Address Key: platformOrganizationOfficeAddress
    Level:
    Mandatory
    Values:
    One value

    The official office or postal address of the organization.

    Format: Text

    Give the full address, including the street or building and the postal code where used.

    Example: Building 12, Example Road, Lahore 54000

    P27.7Platform Organization ROR Key: ror
    Level:
    Recommended
    Values:
    One value

    The ROR identifier of the organization.

    Format: https://ror.org/ + identifier

    Supply the canonical ROR link when the organization has one. It must identify the organization named in P27.1.

    Example: https://ror.org/0abcde123

    3.3 Field descriptions: platform-specific fields (P28 to P53)

    Table 2: Fields for particular platform types
    No.FieldDefinitionValue specification
    P28Platform ISSN and eISSN Key: issn
    Level:
    Required if it exists
    Values:
    Multiple values allowed (up to 2)
    Applies to:
    Journal

    The ISSNs assigned to the journal’s print and electronic editions.

    Format: ISSN + edition

    Supply each ISSN that has been assigned, marked as print or electronic. Never invent or borrow an ISSN.

    Example: 3005-8457 (electronic)

    P29Platform Publication Model Key: platformPublicationModel
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    How the journal releases its published content.

    Format: Controlled value

    Select how content is released. This is separate from the access model.

    Allowed values: see list 5.6.

    Example: Continuous

    P30Platform Publication Frequency Key: platformPublicationFrequency
    Level:
    Mandatory (when the model includes issues)
    Values:
    One value
    Applies to:
    Journal

    How often the journal publishes issues.

    Format: Controlled value

    State the real schedule. Not used for a continuous-only journal.

    Allowed values: see list 5.7.

    Example: Quarterly

    P31Platform First Publication Date Key: platformFirstPublicationDate
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal

    The date the journal first published scholarly content.

    Format: Date: YYYY-MM-DD, YYYY-MM or YYYY

    Use the most exact date known. It may differ from P15.

    Example: 2023

    P32Platform Editor in Chief Key: platformEditorInChief
    Level:
    Mandatory
    Values:
    Multiple values allowed
    Applies to:
    Journal

    The person or persons with chief editorial responsibility for the journal.

    Format: Name + affiliation

    Give each editor in chief’s name and affiliation as publicly stated. List joint editors separately. The other members of the editorial team are given in P53.

    Example: A. Rahman, University of Example

    P53Platform Editorial Team Key: platformEditorialTeam
    Level:
    Optional
    Values:
    Multiple values allowed (up to 100)
    Applies to:
    Journal

    The members of the journal’s editorial team other than the editor in chief.

    Format: Group of parts

    Give each member as publicly stated on the editorial board page (P35.4), with the parts in P53.1–P53.6. The editor in chief is given in P32.

    Example: see P53.1–P53.6

    P53.1Platform Team Member Role Key: platformTeamRole
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    The member’s editorial role.

    Format: Controlled value

    Allowed values: see list 5.31.

    Example: Associate Editor

    P53.2Platform Team Member Name Key: platformTeamMemberName
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    The member’s name.

    Format: Given names + family name

    Give the given names and the family name separately, as the member writes them.

    Example: Ayesha Khan

    P53.3Platform Team Member Affiliation Key: platformTeamAffiliation
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    The member’s current institution.

    Format: Text

    Give the institution as publicly stated.

    Example: University of Example

    P53.4Platform Team Member Country Key: platformTeamCountry
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    The country of the member’s institution.

    Format: Country code (ISO 3166-1 alpha-2)

    Example: PK

    P53.5Platform Team Member XPENID Key: xpenid
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Journal

    The member’s XPENID.

    Format: XPENID

    Example: AB-XPEN2026-0123

    P53.6Platform Team Member ORCID iD Key: orcid
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Journal

    The member’s ORCID iD.

    Format: https://orcid.org/ + identifier

    Example: https://orcid.org/0000-0002-1825-0097

    P33Platform Peer Review Type Key: platformPeerReviewType
    Level:
    Mandatory for journals; Recommended for scholarly presses
    Values:
    One value
    Applies to:
    Journal, Scholarly Press

    The review model the platform applies to its scholarly content.

    Format: Controlled value

    Select the model actually used. For a journal, the public peer review policy (P35.6) explains the process and any exceptions.

    Allowed values: see list 5.8.

    Example: Double blind

    P34Platform Author Fees Key: platformAuthorFees
    Level:
    Mandatory for journals; Recommended for scholarly presses
    Values:
    Multiple values allowed
    Applies to:
    Journal, Scholarly Press

    The charges the platform makes to authors to submit or publish.

    Format: Fee type + amount + currency

    Select No fee, or give each charge with its type, amount and currency. Charges to readers are not recorded here. Waivers are explained in the author fees policy (P35.2).

    Allowed values: see list 5.9.

    Example: No fee

    P35Platform Policy Links Key: platformPolicyLinks
    Level:
    Mandatory
    Values:
    Multiple values allowed
    Applies to:
    Journal

    Public links to the journal’s own published policies.

    Format: Group of parts

    Supply a link for each Mandatory policy in P35.1–P35.11, and for P35.12–P35.15 where the journal has them. One page may serve several policies if each policy can be clearly found on it. Each link must lead to the journal’s own published page.

    Example: https://journal.example.org/policies/peer-review

    P35.1Platform Copyright and Licence Policy Key: platformCopyrightAndLicencePolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    Who keeps copyright, which reuse licences apply, and how permissions are handled.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.2Platform Author Fees Policy Key: platformAuthorFeesPolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    All charges to authors, their amounts, currency and when they are paid, or a statement that there are none, with any waivers.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.3Platform Ethics Policy Key: platformEthicsPolicy
    Level:
    Mandatory for journals; Recommended for scholarly presses
    Values:
    One value
    Applies to:
    Journal, Scholarly Press

    The journal’s research and publication ethics expectations, and how suspected misconduct is handled.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.4Platform Editorial Board Key: platformEditorialBoard
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    The names, roles and affiliations of the editorial board, including the editor in chief.

    Format: HTTPS URL

    Link to the journal’s own current editorial board page.

    P35.5Platform Author Instructions Key: platformAuthorInstructions
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    Who may submit, how to prepare a manuscript, the declarations required and the submission process.

    Format: HTTPS URL

    Link to the journal’s own published instructions.

    P35.6Platform Peer Review Policy Key: platformPeerReviewPolicy
    Level:
    Mandatory for journals; Recommended for scholarly presses
    Values:
    One value
    Applies to:
    Journal, Scholarly Press

    The review model, how reviewers are chosen, who decides, expected timescales and any exceptions by content type.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.7Platform Plagiarism Policy Key: platformPlagiarismPolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    How plagiarism concerns are checked and what follows a confirmed finding.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.8Platform AI Use Policy Key: platformAiUsePolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    Permitted uses of AI tools, and the disclosure duties of authors, reviewers and editors.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.9Platform Conflicts of Interest Policy Key: platformConflictsOfInterestPolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    How interests are disclosed, and how editorial and reviewer conflicts are managed.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.10Platform Corrections and Retractions Policy Key: platformCorrectionsAndRetractionsPolicy
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Journal

    How errors, corrections, withdrawals and retractions are handled, and how notices stay linked to the works they concern.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.11Platform Archiving Policy Key: platformArchivingPolicy
    Level:
    Mandatory (“Not arranged yet” allowed)
    Values:
    One value
    Applies to:
    Journal

    The arrangements for continued access to the journal’s content if it stops publishing.

    Format: HTTPS URL or “Not arranged yet”

    Link to the policy, or declare “Not arranged yet”. The declaration is not an archiving arrangement.

    P35.12Platform Complaints and Appeals Policy Key: platformComplaintsAndAppealsPolicy
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal

    How to make a complaint or appeal against an editorial decision.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.13Platform Data Sharing Policy Key: platformDataSharingPolicy
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal

    Expectations for supporting data, repositories, access limits and data availability statements.

    Format: HTTPS URL

    Link to the journal’s own published policy.

    P35.14Platform Aims and Scope Key: platformAimsAndScope
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal

    The subjects covered, the intended readers and the types of contribution considered.

    Format: HTTPS URL

    Link to the journal’s own published page.

    P35.15Platform Editorial Office Address Key: platformEditorialOfficeAddress
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal

    The journal’s public contact page giving its editorial office address.

    Format: HTTPS URL

    Link to the journal’s official contact page.

    P36Platform Indexing Links Key: platformIndexingLinks
    Level:
    Optional
    Values:
    Multiple values allowed
    Applies to:
    Journal, Scholarly Press

    Links to the journal’s own records in indexes and directories.

    Format: Index name + HTTPS URL

    Each entry gives one index and one link to the platform’s own record in it. A scholarly press may give Scopus, Web of Science and DOAB. A listing must not suggest any status beyond what the index record shows.

    Allowed services: see list 5.10.

    Example: AlifIndex + link to the journal’s record

    P37Platform Repository Content Types Key: platformRepositoryContentTypes
    Level:
    Mandatory
    Values:
    Multiple values allowed
    Applies to:
    Repository

    The kinds of material the repository holds.

    Format: Content type values

    Select each content type the repository registers, from the content types allowed for repositories. Outputs of the repository may use only the selected types.

    Allowed values: see list 5.12.

    Example: Thesis; Dissertation; Dataset

    P38Platform Repository Software Key: platformRepositorySoftware
    Level:
    Optional
    Values:
    One value
    Applies to:
    Repository

    The software that runs the repository.

    Format: Text

    Name the software and its version. Recommended names: DSpace, EPrints, Islandora, Fedora, Samvera Hyrax, Invenio, InvenioRDM, Dataverse, Figshare, Omeka S, Omeka Classic, CONTENTdm, Greenstone, Digital Commons, Pure, Esploro, Custom (in-house); another name may be given.

    Example: DSpace 7.6

    P39Platform OAI-PMH Address Key: platformOaiPmhAddress
    Level:
    Recommended for repositories; Optional for archives
    Values:
    One value
    Applies to:
    Repository, Archive

    The base address of the platform’s OAI-PMH service, which other systems use to collect its records automatically.

    Format: HTTPS URL

    Supply the base URL that answers OAI-PMH requests.

    Example: https://repository.example.edu/oai/request

    P40Platform Repository Policy Links Key: platformRepositoryPolicyLinks
    Level:
    Recommended
    Values:
    Multiple values allowed
    Applies to:
    Repository

    Public links to the repository’s own policies.

    Format: Group of parts

    Supply one link for each policy in P40.1–P40.3.

    P40.1Platform Deposit Policy Key: platformDepositPolicy
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Repository

    Who may deposit material, what may be deposited, and how.

    Format: HTTPS URL

    Link to the repository’s own published policy.

    P40.2Platform Preservation Policy Key: platformPreservationPolicy
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Repository

    How long, and by what means, the repository keeps its content available.

    Format: HTTPS URL

    Link to the repository’s own published policy.

    P40.3Platform Metadata Reuse Policy Key: platformMetadataReusePolicy
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Repository

    The terms on which others may reuse the repository’s metadata.

    Format: HTTPS URL

    Link to the repository’s own published policy.

    P41Platform Coverage Period Key: platformCoveragePeriod
    Level:
    Optional
    Values:
    One value
    Applies to:
    Archive

    The time span covered by the archive’s holdings.

    Format: Date range

    Give the period of the material held, not the archive’s founding date.

    Example: 1947–1990

    P42Platform Holdings Format Key: platformHoldingsFormat
    Level:
    Mandatory
    Values:
    Multiple values allowed
    Applies to:
    Archive

    The kinds of material the archive holds.

    Format: Content type values

    Select each content type the archive registers, from the content types allowed for archives. Outputs of the archive may use only the selected types.

    Allowed values: see list 5.12.

    Example: Digitized Manuscript / Historical Document; Photograph / Image; Audio Recording

    P43Platform Approximate Holdings Key: platformApproximateHoldings
    Level:
    Optional
    Values:
    One value
    Applies to:
    Archive

    An estimate of the amount of material the archive holds.

    Format: Quantity + unit + date

    Give the quantity, the unit and the date of the estimate. Recommended units: items, volumes, documents, files, folders, boxes, pages, photographs, recordings, maps, objects, reels, linear metres.

    Example: About 12,000 items (2026)

    P44Platform Access Conditions Key: platformAccessConditions
    Level:
    Retired in 2.0
    Values:
    One value
    Applies to:
    Archive

    How the public can use the archive’s holdings.

    Retired in 2.0. Not supplied in records following version 2.0. Access to archive holdings is given by the access model (P23), and each output records its own (O23). The definition below is that of version 1.0.

    Format: Text

    State whether material is available online, on site or by appointment, and any conditions that apply.

    Example: Catalogue online; originals on site by appointment

    P45Platform Finding Aids Link Key: platformFindingAidsLink
    Level:
    Optional
    Values:
    One value
    Applies to:
    Archive

    A link to the archive’s catalogue, inventory or finding aid.

    Format: HTTPS URL

    Link to the archive’s own public catalogue.

    Example: https://archive.example.org/catalogue

    P46Platform ISBN Prefix Key: platformIsbnPrefix
    Level:
    Required if it exists
    Values:
    Multiple values allowed
    Applies to:
    Scholarly Press

    The ISBN prefix assigned to the scholarly press.

    Format: ISBN prefix

    Supply each prefix the scholarly press has been assigned. It does not replace the ISBN of each book, which is recorded in O28.

    Example: 978-1-23456

    P47Platform Editorial Board Link Key: platformEditorialBoardLink
    Level:
    Optional
    Values:
    One value
    Applies to:
    Scholarly Press

    The public page listing the scholarly press’s editorial board.

    Format: HTTPS URL

    Link to the scholarly press’s own current page.

    P48Platform Committee Links Key: platformCommitteeLinks
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed
    Applies to:
    Event Organizer

    Public pages listing the organizing or scientific committees.

    Retired in 2.0. Not supplied in records following version 2.0. Each event is an output record with its own details (Section 6). The definition below is that of version 1.0.

    Format: HTTPS URL

    Link to the organization’s official committee pages.

    P49Platform Series Name Key: platformSeriesName
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed
    Applies to:
    Event Organizer

    The name of each recurring conference series the organization runs.

    Retired in 2.0. Not supplied in records following version 2.0. Each event is an output record with its own details (Section 6). The definition below is that of version 1.0.

    Format: Text

    Keep the organization, the series and each event distinct. Individual events are recorded as outputs.

    Example: International Conference on Language and Education

    P50Platform Conference Frequency Key: platformConferenceFrequency
    Level:
    Retired in 2.0
    Values:
    One value
    Applies to:
    Event Organizer

    How often the conference series usually takes place.

    Retired in 2.0. Not supplied in records following version 2.0. Each event is an output record with its own details (Section 6). The definition below is that of version 1.0.

    Format: Text

    State the usual interval. It is not a promise of future events.

    Example: Annual

    P51Platform First Event Year Key: platformFirstEventYear
    Level:
    Retired in 2.0
    Values:
    One value
    Applies to:
    Event Organizer

    The year of the first event in the conference series.

    Retired in 2.0. Not supplied in records following version 2.0. Each event is an output record with its own details (Section 6). The definition below is that of version 1.0.

    Format: Four-digit year

    Use the year the first event took place. It may differ from P15.

    Example: 2019

    P52Platform Proceedings ISSN or ISBN Key: platformProceedingsIdentifiers
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed
    Applies to:
    Event Organizer

    The ISSN of the conference’s proceedings series, or the ISBNs of its proceedings volumes.

    Retired in 2.0. Not supplied in records following version 2.0. The ISBN of a proceedings volume and the ISSN of a proceedings series are recorded on the volume’s output record (O28). The definition below is that of version 1.0.

    Format: ISSN or ISBN + type

    Supply each identifier that has been assigned. Never invent one.

    Example: ISSN 1234-5679

    4. Output Metadata

    4.1 Overview

    This section defines the metadata describing a scholarly output registered under a platform. Table 3 contains the fields for every output. Table 4 contains the fields that apply to particular content types. Requirements specific to a content type are set out in Section 6. Some output fields are filled from the platform record and may be changed for an individual output.

    4.2 Field descriptions: every output (O1 to O35, O55, O56, O60)

    Table 3: Fields for every output
    No.FieldDefinitionValue specification
    O1Output NiD Key: nid
    Level:
    Mandatory
    Values:
    One value

    The persistent NiD of the platform under which the output is registered.

    Format: Assigned NiD

    The NiD of the platform registering the output. The output’s content type must be permitted for that platform’s type.

    Example: 001:xijir

    O2Output SEIPID Key: seipid
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The persistent identifier of the registered scholarly output.

    Format: The NiD, a colon and a suffix assigned by the Registry. The suffix is the publication year, a letter and a running number: n for most outputs (2025n4), b for books (2026b1) and e for events (2026e1). A chapter adds c and its chapter number to its book’s suffix (2026b1c4); a contribution adds c and a running number to its event’s suffix (2026e1c3). An archive uses the year of registration and pid (2026pid15).

    The Registry assigns the SEIPID when the output is registered. The submitter does not supply it. A SEIPID is never reassigned to another output and is never deleted.

    Example: 001:xijir:2025n4

    O3Output Status Key: outputStatus
    Level:
    Mandatory (assigned by the Registry)
    Values:
    One value

    The current standing of the output in the Registry.

    Format: Controlled value

    The Registry sets and updates the status. Retracted or Withdrawn is set only when the notice is linked in O33 or confirmed by the platform. Replaced is set when a newer record identifies this one with Replaces in O33. Removed is set only by SEIPID. When more than one applies, the first in this order is used: Removed, Retracted, Withdrawn, Replaced. The record and its public page remain available, marked with the status.

    Allowed values: see list 5.11.

    Example: Active

    O4Output Content Type Key: outputContentType
    Level:
    Mandatory
    Values:
    One value

    The category that describes the nature of the output.

    Format: Controlled value

    Select one content type permitted for the platform’s type (P5); a repository or archive may use only the types it selected in P37 or P42. The content type decides which fields in Table 4 apply and which content-type requirements must be met.

    Allowed values: see list 5.12.

    Example: Research Article

    O5Output Language Key: outputLanguage
    Level:
    Mandatory (when the content type requires it)
    Values:
    Multiple values allowed

    The principal language or languages of the output.

    Format: Language codes (BCP 47)

    Give the language of the output itself, not of its translated metadata. A dataset or software output may omit it when no natural language applies.

    Example: en

    O6Output Original Title Key: outputOriginalTitle
    Level:
    Mandatory
    Values:
    One value

    The complete title of the output in its original language, as published.

    Format: Text

    Keep the spelling, script and meaning as published. Record a separately published subtitle in O7.

    Example: Impact of Graphic Illustrations on English Vocabulary Acquisition in Pakistani Dyslexic Students

    O7Output Subtitle Key: outputSubtitle
    Level:
    Optional
    Values:
    One value

    The additional title statement published with the main title.

    Format: Text

    Keep it separate from the main title. Do not create a subtitle by splitting an ordinary title. For an event record, the subtitle holds the event’s theme.

    O8Output Short Title Key: outputShortTitle
    Level:
    Mandatory (when the original title is over 59 characters; made by the Registry when not supplied)
    Values:
    One value

    A concise English title used for search results and shared-link previews.

    Format: Text, 1–59 characters

    Supply it when the original title is over 59 characters, counting spaces and punctuation. Keep the meaning of the full title, which is still recorded in O6. When it is not supplied, the Registry makes it from the title.

    Example: Graphic Illustrations for Dyslexic Learners

    O9Output English Translated Title Key: outputEnglishTranslatedTitle
    Level:
    Recommended (when the title is not in English)
    Values:
    One value

    An English translation of a title published in another language.

    Format: Text, English

    Keep the meaning of the original title. The translation does not replace the original title.

    O10Output English Translated Subtitle Key: outputEnglishTranslatedSubtitle
    Level:
    Recommended (when the subtitle is not in English)
    Values:
    One value

    An English translation of a subtitle published in another language.

    Format: Text, English

    Supply only when the output has a subtitle in O7.

    O11Output Abstract or Description Key: outputAbstractOrDescription
    Level:
    Mandatory (when the content type requires it)
    Values:
    Multiple values allowed

    A substantive summary of the output’s content or purpose.

    Format: Text with language code

    Use the published abstract where one exists; otherwise give an accurate description. A title alone is not a description. When the output publishes abstracts in more than one language, give each with its language.

    O12Output English Translated Abstract or Description Key: outputEnglishTranslatedAbstractOrDescription
    Level:
    Recommended (when not in English)
    Values:
    One value

    An English translation of the original abstract or description.

    Format: Text, English

    Keep the original text in O11. Do not add findings that are not in the original.

    O13Output Keywords Key: outputKeywords
    Level:
    Mandatory (when the content type requires them)
    Values:
    Multiple values allowed (3–7)

    Terms in the output’s original language describing its main topics.

    Format: Text terms

    Supply 3 to 7 distinct keywords. Keep each term separate.

    Example: dyslexia; vocabulary acquisition; graphic illustrations

    O14Output English Translated Keywords Key: outputEnglishTranslatedKeywords
    Level:
    Optional
    Values:
    Multiple values allowed (up to 7)

    English equivalents of the original keywords.

    Format: Text terms, English

    Keep the original terms in O13 alongside their translations.

    O15Output Subject Group Key: outputSubjectGroup
    Level:
    Mandatory (when the content type requires it)
    Values:
    One value

    The broad subject area of the output.

    Format: Controlled value

    Select one broad subject area: the area of the output’s main discipline.

    Allowed values: see list 5.18.

    Example: Social Sciences and Humanities

    O16Output Disciplines Key: outputDisciplines
    Level:
    As O15
    Values:
    Multiple values allowed (1–3)

    The defined fields of study of the output.

    Format: Controlled values

    Select 1 to 3 disciplines from the discipline list. They may come from any area; at least one belongs to the area selected in O15, and the main discipline comes first.

    Allowed values: see list 5.19.

    Example: Applied Linguistics and Language Teaching

    O17Output Subjects Key: outputSubjects
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed (up to 3)

    Specific topics of the output, each within one of its disciplines.

    Retired in 2.0. Not supplied in records following version 2.0. Specific topics are described by the keywords (O13). The definition below is that of version 1.0.

    Format: Subject term + discipline

    Supply up to 3 topics, each linked to one of the disciplines in O16.

    Example: Applied linguistics (Languages, Linguistics and Literature)

    O18Output Contributors Key: outputContributors
    Level:
    Mandatory
    Values:
    Multiple values allowed

    The people or organizations credited with responsibility for the output, in published order.

    Format: Ordered group of parts

    Include every author in publication order, and other credited contributors with their actual roles. At least one contributor is required. Each contributor’s details are given in O18.1–O18.9.

    O18.1Output Contributor Type Key: outputContributorType
    Level:
    Mandatory (person or organization)
    Values:
    One value

    Whether the contributor is a person or an organization.

    Format: Controlled value

    Applies to every contributor. A group author is an organization.

    Allowed values: see list 5.13.

    Example: Person

    O18.2Output Contributor Name Key: outputContributorName
    Level:
    Mandatory (built by the Registry for a person; entered for an organization)
    Values:
    One value

    The contributor’s name as credited on the output.

    Format: Text

    For a person, the Registry builds the name from O18.2.1 and O18.2.2. For an organization, enter its full credited name.

    Example: Saba Akmal

    O18.2.1Output Contributor Given Names Key: outputContributorGivenNames
    Level:
    Required if it exists (persons)
    Values:
    One value

    The person’s given name or names.

    Format: Text

    Leave it empty when the person uses a single name. Do not invent a given name.

    Example: Saba

    O18.2.2Output Contributor Family Name Key: outputContributorFamilyName
    Level:
    Mandatory (persons)
    Values:
    One value

    The person’s family name, or their only name.

    Format: Text

    A person with a single name records it here.

    Example: Akmal

    O18.3Output Contributor Role Key: outputContributorRole
    Level:
    Mandatory
    Values:
    One value

    The capacity in which the contributor took part.

    Format: Controlled value

    Select the contributor’s actual role. A contributor’s position in the list is separate from the role and from CRediT roles.

    Allowed values: see list 5.14.

    Example: Author

    O18.4Output Contributor CRediT Roles Key: outputContributorCreditRoles
    Level:
    Optional
    Values:
    Multiple values allowed

    The specific research contributions credited to the contributor, using the CRediT taxonomy.

    Format: Controlled values

    Select one or more of the 14 CRediT roles. Several contributors may share a role. These roles do not decide author order or authorship.

    Allowed values: see list 5.15.

    Example: Conceptualization; Methodology

    O18.5Output Corresponding Author Key: outputCorrespondingAuthor
    Level:
    Mandatory (one author, when the output has authors)
    Values:
    One value

    The author designated to handle correspondence about the output.

    Format: Yes on one listed author

    Mark exactly one author. A sole author is the corresponding author automatically. When a new record marks no one, the Registry marks the first person with the role Author. Do not make a non-author the corresponding author.

    O18.6Output Contributor Affiliation Key: outputContributorAffiliation
    Level:
    Mandatory (persons; “Independent researcher” when there is no affiliation)
    Values:
    Multiple values allowed (up to 3)

    The organization with which the person was associated for this output.

    Format: Group of parts

    Give each affiliation stated in the output, in the order the output prints them, up to three; not the person’s later employment. A person with no affiliation is recorded as “Independent researcher”. Do not invent an institution. Details are given in O18.6.1–O18.6.4.

    O18.6.1Output Affiliation Name Key: outputAffiliationName
    Level:
    Mandatory
    Values:
    One value

    The name of the affiliated organization.

    Format: Text

    Use the organization’s full name, or “Independent researcher”.

    Example: University of Example

    O18.6.2Output Affiliation Department Key: outputAffiliationDepartment
    Level:
    Optional
    Values:
    One value

    The department or unit within the affiliated organization.

    Format: Text

    Give the department stated in the output.

    Example: Department of English

    O18.6.3Output Affiliation Country Key: outputAffiliationCountry
    Level:
    Mandatory
    Values:
    One value

    The country of the affiliated organization.

    Format: Country (ISO 3166-1 code)

    For an independent researcher, give the country where the research was carried out. This field does not record nationality.

    Example: Pakistan (PK)

    O18.6.4Output Affiliation ROR Key: ror
    Level:
    Recommended
    Values:
    One value

    The ROR identifier of the affiliated organization.

    Format: https://ror.org/ + identifier

    Supply the canonical ROR link for the organization in O18.6.1. Never assign an organization’s ROR to a person.

    O18.7Output Contributor XPENID Key: xpenid
    Level:
    Recommended
    Values:
    One value

    The contributor’s persistent XPENID.

    Format: XPENID, such as SA-XPEN2025-0057

    Supply the contributor’s own XPENID where one exists. It is not a condition of authorship.

    Example: SA-XPEN2025-0057

    O18.8Output Contributor ORCID iD Key: orcid
    Level:
    Recommended
    Values:
    One value

    The persistent ORCID identifier of a person.

    Format: https://orcid.org/ + identifier

    Supply the person’s own ORCID link. Never use an ORCID iD for an organization.

    Example: https://orcid.org/0000-0002-1825-0097

    O18.9Output Contributor Email Key: outputContributorEmail
    Level:
    Recommended (restricted, never public)
    Values:
    One value

    An email address for correspondence with the contributor and for identity matching.

    Format: Email address

    Restricted. It is never shown on public pages or included in public metadata, feeds or exports. It is separate from the platform’s public contact address (P12).

    Example: [email protected]

    O19Output Publication Date Key: outputPublicationDate
    Level:
    Mandatory
    Values:
    One value

    The date on which the output was published or made available by its source.

    Format: Date: YYYY-MM-DD, YYYY-MM or YYYY

    Use the date of the output, not the date of SEIPID registration. Use only the precision known; explain uncertain dates in O20.14.

    Example: 2025-05-15

    O20Output Other Dates Key: outputOtherDates
    Level:
    Optional
    Values:
    Multiple values allowed

    Further dates in the life of the output.

    Format: Group of parts

    Each date is given in its own part, O20.1–O20.13. Use only the precision known. Dates follow the order set out in Section 8.2.

    O20.1Output Submitted Date Key: outputSubmittedDate
    Level:
    Recommended (journal items)
    Values:
    One value

    The date the output was submitted for publication or review.

    Format: Date

    Record the date of first submission to this platform.

    Example: 2025-01-10

    O20.2Output Revised Dates Key: outputRevisedDates
    Level:
    Optional
    Values:
    Multiple values allowed

    The dates on which revised versions were submitted.

    Format: Dates

    List the dates in time order.

    O20.3Output Accepted Date Key: outputAcceptedDate
    Level:
    Recommended (journal items)
    Values:
    One value

    The date the output was accepted for publication.

    Format: Date

    Record the actual acceptance date. Do not infer it from the publication date.

    Example: 2025-04-02

    O20.4Output Online First Date Key: outputOnlineFirstDate
    Level:
    Optional
    Values:
    One value

    The date of online publication before a volume or issue was assigned.

    Format: Date

    For a journal item without a volume, this date allows O36 to stay empty until the volume is assigned.

    O20.5Output Posted Date Key: outputPostedDate
    Level:
    Optional
    Values:
    One value

    The date the output was posted, such as a preprint.

    Format: Date

    Record the date the source first posted it.

    O20.6Output Available Date Key: outputAvailableDate
    Level:
    Retired in 2.0
    Values:
    One value

    The date the output became available to readers, where this differs from publication.

    Retired in 2.0. Not supplied in records following version 2.0. The publication date (O19) and the access model (O23) describe availability. The definition below is that of version 1.0.

    Format: Date

    Use only when availability differs from O19.

    O20.7Output Created Date Key: outputCreatedDate
    Level:
    Optional
    Values:
    One value

    The date the resource itself was created.

    Format: Date

    Use for datasets, software, media and archival material.

    O20.8Output Updated Date Key: outputUpdatedDate
    Level:
    Retired in 2.0
    Values:
    One value

    The date the resource itself was last updated.

    Retired in 2.0. Not supplied in records following version 2.0. Each output is registered as published; a changed resource is registered as a new version (O33). The definition below is that of version 1.0.

    Format: Date

    Describes a change to the resource, not to its SEIPID record.

    O20.9Output Collected Date Key: outputCollectedDate
    Level:
    Optional
    Values:
    One value

    The date or period in which material or data was collected.

    Format: Date or date range

    Give a start and end when collection took place over a period.

    O20.10Output Embargo End Date Key: outputEmbargoEndDate
    Level:
    Mandatory with the access model Embargoed or Delayed open access; otherwise not given
    Values:
    One value

    The date on which an access embargo ends.

    Format: Date

    Give it only when O23 is Embargoed or Delayed open access. It is on or after the publication date (O19). The date alone does not change O23. Update the access model when access actually changes.

    O20.11Output Copyright Year Key: outputCopyrightYear
    Level:
    Retired in 2.0
    Values:
    One value

    The year stated in the output’s copyright notice.

    Retired in 2.0. Not supplied in records following version 2.0. The copyright holder is given in O25. The definition below is that of version 1.0.

    Format: Four-digit year

    Use the year as published.

    O20.12Output Retracted Date Key: outputRetractedDate
    Level:
    Assigned by the Registry
    Values:
    One value

    The date the retraction of the output was published.

    Format: Date

    The Registry sets it when the platform registers a Retraction Notice that “Retracts” the output: it is the notice’s publication date (Section 7.3). It is not supplied directly.

    O20.13Output Withdrawn Date Key: outputWithdrawnDate
    Level:
    Assigned by the Registry
    Values:
    One value

    The date the output was withdrawn.

    Format: Date

    The Registry sets it when it confirms the platform’s withdrawal request, with the reason in O56 (Section 7.3). It is not supplied directly.

    O56Output Withdrawal Reason Key: outputWithdrawalReason
    Level:
    Assigned by the Registry (withdrawn outputs)
    Values:
    One value

    Why the output was withdrawn.

    Format: Controlled value

    The Registry records the reason given in the confirmed withdrawal request.

    Allowed values: see list 5.27.

    Example: Duplicate publication

    O20.14Output Date Note Key: outputDateNote
    Level:
    Retired in 2.0
    Values:
    One value

    An explanation of a date’s precision, uncertainty or meaning.

    Retired in 2.0. Not supplied in records following version 2.0. Use only the precision known for each date; give no day or month that is not known. The definition below is that of version 1.0.

    Format: Text

    Use for approximate or historical dates. Never invent a day or month to make a date look complete.

    Example: Publication year known; month and day not recorded.

    O21Output Target Page Link Key: outputTargetPageLink
    Level:
    Mandatory
    Values:
    One value

    The source page for this specific output.

    Format: HTTPS URL

    Give the page of this output, not the platform’s home page or a private session link. Keep it current.

    Example: https://journal.example.org/article/view/123

    O22Output PDF Link Key: outputPdfLink
    Level:
    Recommended
    Values:
    One value

    A direct link to a PDF of the output.

    Format: HTTPS URL

    Supply only when a PDF exists. The link must respect the output’s access conditions.

    Example: https://journal.example.org/article/download/123.pdf

    O23Output Access Model Key: outputAccessModel
    Level:
    Mandatory (filled from the platform, can be changed)
    Values:
    One value

    The conditions under which the output itself can be accessed.

    Format: Controlled value

    Filled from P23. Change it when this output differs. A public SEIPID record does not mean the full text is open.

    Allowed values: see list 5.22.

    Example: Open access

    O24Output Licence Key: outputLicence
    Level:
    Mandatory (filled from the platform, can be changed)
    Values:
    One value

    The terms under which the output may be reused.

    Format: Controlled value

    Filled from P21. Change it when this output differs. Give the exact licence version. For a custom licence, supply its text or link. Use Unknown when there is no evidence; never invent permission.

    Allowed values: see list 5.20.

    Example: CC BY 4.0

    O25Output Copyright Holder Key: outputCopyrightHolder
    Level:
    Mandatory (filled from the platform, can be changed)
    Values:
    One value

    Who holds copyright in the output, or its stated copyright status.

    Format: Holder category + name

    Filled from P22. Change it when this output differs. Give the holder’s name where known.

    Allowed values: see list 5.21.

    Example: Author / Creator; Saba Akmal

    O60Output External Publisher Key: outputExternalPublisher
    Level:
    Optional
    Values:
    One value

    The publisher of the output when it is not the platform’s organization (P27.1).

    Format: Text

    Give it only when another organization published the output.

    Example: Example University Press

    O26Output Reader Price Key: outputReaderPrice
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed

    The price a reader pays to access or buy this output.

    Retired in 2.0. Not supplied in records following version 2.0. A reader’s access is described by the access model (O23). The definition below is that of version 1.0.

    Format: Description + amount + currency

    State what the price covers, its amount and currency. Charges to authors are recorded in P34, not here.

    Example: Full-text access; 10.00; USD

    O27Output Peer Reviewed Key: outputPeerReviewed
    Level:
    Optional (filled from the platform, can be changed)
    Values:
    One value

    Whether this output underwent peer review.

    Format: Yes or No

    Filled from P33. The value must describe this output; not every item in a peer-reviewed journal is reviewed, such as editorials. Omission means not stated.

    Example: Yes

    O28Output Other Identifiers Key: outputOtherIdentifiers
    Level:
    Required if it exists
    Values:
    Multiple values allowed

    Identifiers given to the same output by other systems.

    Format: Group of parts

    Record every identifier the output has, such as a DOI or ISBN, with its type in O28.1 and value in O28.2. An ISBN of a parent book belongs to the book, not to its chapter.

    O28.1Output Identifier Type Key: outputIdentifierType
    Level:
    Mandatory
    Values:
    One value

    The scheme of the identifier.

    Format: Controlled value

    Select the scheme.

    Allowed values: see list 5.16.

    Example: DOI

    O28.2Output Identifier Value Key: outputIdentifierValue
    Level:
    Mandatory
    Values:
    One value

    The identifier itself.

    Format: Text

    Give the exact value as issued by its scheme.

    Example: 10.1234/example.2025.4

    O29Output Funding Key: outputFunding
    Level:
    Required if it exists
    Values:
    Multiple values allowed

    The financial support acknowledged for producing the output.

    Format: Group of parts

    Give one entry for each funder or award. Do not infer funding from an affiliation. Details are given in O29.1–O29.4.

    O29.1Output Funder Name Key: outputFunderName
    Level:
    Mandatory
    Values:
    One value

    The name of the funding organization.

    Format: Text

    Use the funder’s full official name.

    Example: Example Research Foundation

    O29.2Output Funder ROR Key: ror
    Level:
    Recommended
    Values:
    One value

    The ROR identifier of the funder.

    Format: https://ror.org/ + identifier

    Supply the canonical ROR link for the funder in O29.1.

    O29.3Output Award Number Key: outputAwardNumber
    Level:
    Required if it exists
    Values:
    One value

    The grant or award number given by the funder.

    Format: Text

    Give the number exactly as issued.

    Example: ERF-2025-117

    O29.4Output Award Title Key: outputAwardTitle
    Level:
    Optional
    Values:
    One value

    The title of the grant or award.

    Format: Text

    Give the title as the funder states it.

    Example: Inclusive Reading for Dyslexic Learners

    O30Output Data Availability Key: outputDataAvailability
    Level:
    Optional
    Values:
    One value

    Whether and how the data supporting the output can be accessed.

    Format: Controlled value

    Select the option that matches the output’s published statement. Omission means not stated; it does not mean no data exist.

    Allowed values: see list 5.23.

    Example: Openly available in a public repository

    O31Output Ethics Status Key: outputEthicsStatus
    Level:
    Optional
    Values:
    One value

    The ethical approval status of the research reported in the output.

    Format: Controlled value

    Select the status stated in the output.

    Allowed values: see list 5.24.

    Example: Approved by an ethics committee / IRB

    O32Output Competing Interests Key: outputCompetingInterests
    Level:
    Optional
    Values:
    One value

    Whether the output declares competing interests.

    Format: Controlled value

    Select the option stated in the output. Do not select “No competing interests” when the output makes no statement.

    Allowed values: see list 5.25.

    Example: No competing interests

    O55Output AI Use Key: outputAiUse
    Level:
    Optional
    Values:
    One value

    Whether and how artificial intelligence tools were used to prepare the output.

    Format: Controlled value

    Give the statement the output makes.

    Allowed values: see list 5.26.

    Example: AI used for language editing

    O33Output Related Works Key: outputRelatedWorks
    Level:
    As stated in Section 6; otherwise Optional
    Values:
    Multiple values allowed

    Links between this output and other identified works.

    Format: Group of parts

    Each entry gives a relation type (O33.1) and the related work’s identifier (O33.2). A correction must link the work it corrects; a retraction notice must link the work it retracts; an expression of concern must link the work it is about.

    O33.1Output Relation Type Key: outputRelationType
    Level:
    Mandatory
    Values:
    One value

    How this output relates to the other work.

    Format: Controlled value

    Select the relation.

    Allowed values: see list 5.17.

    Example: Corrects

    O33.2Output Related Identifier Key: outputRelatedIdentifier
    Level:
    Mandatory
    Values:
    One value

    The identifier of the related work.

    Format: SEIPID, other identifier or HTTPS URL

    Use its SEIPID where it has one; otherwise its DOI or link.

    Example: 001:example:2025n7

    O34Output References Key: outputReferences
    Level:
    Mandatory (when the content type requires them)
    Values:
    Multiple values allowed

    The works cited by the output, in their published order.

    Format: Ordered reference entries

    List each cited work once, in full, in one style. Footnotes and short forms such as “Ibid.”, “op. cit.” or “supra” are not references. Keep each reference’s text as published. Add its SEIPID, DOI or other identifier when known, with its type from list 5.16. Never invent a reference.

    O35Output Extra Metadata Key: outputExtraMetadata
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed

    Additional structured information not covered by a defined field.

    Retired in 2.0. Not supplied in records following version 2.0. Each value is recorded in its own defined field. The definition below is that of version 1.0.

    Format: Named values

    Each entry has a documented name, meaning and source. It must not replace a defined field, change its meaning or expose restricted information.

    4.3 Field descriptions: some content types (O36 to O54, O57 to O59, O61)

    Table 4: Fields for particular content types
    No.FieldDefinitionValue specification
    O36Output Volume Key: outputVolume
    Level:
    Mandatory (unless Online First without a volume)
    Values:
    One value
    Applies to:
    Journal items

    The volume of the journal in which the item appears.

    Format: Text

    Supply it once assigned. An Online First item may leave it empty while O20.4 is supplied; add the volume when assigned.

    Example: 2

    O37Output Issue Key: outputIssue
    Level:
    Required if it exists
    Values:
    One value
    Applies to:
    Journal items

    The issue within the volume.

    Format: Text

    Keep the published value, including supplements or combined issues.

    Example: 2

    O38Output Issue Title Key: outputIssueTitle
    Level:
    Optional
    Values:
    One value
    Applies to:
    Journal items

    The title of a special, themed or named issue.

    Format: Text

    Do not use it for the journal title or the article title.

    Example: Language and Inclusive Education

    O39Output Pages Key: outputPages
    Level:
    Required if it exists
    Values:
    One value
    Applies to:
    Journal items, chapters and other parts, conference papers

    The page range of the output.

    Format: Page range

    Keep the published range. Do not create pages for an unpaginated item.

    Example: 15–28

    O40Output Article Number Key: outputArticleNumber
    Level:
    Required if it exists
    Values:
    One value
    Applies to:
    Journal items

    The number the journal gives the article instead of, or as well as, pages.

    Format: Text

    Keep the journal’s own number. It is not the SEIPID.

    Example: e1042

    O41Output Chapter or Paper Number Key: outputChapterOrPaperNumber
    Level:
    Optional
    Values:
    One value
    Applies to:
    Parts of books, reference works, literary works and events

    The number printed for the chapter, entry, piece or paper within its parent publication.

    Format: Number

    Use digits only, without a label such as “Chapter” or “Paper”. Keep it separate from the pages and from the parent’s identifier. The Registry numbers each part in its SEIPID (Section 7.2); this field holds the number printed in the publication, where there is one.

    Example: 4

    O42Output Edition Key: outputEdition
    Level:
    Required if it exists
    Values:
    One value
    Applies to:
    Books, event records

    The edition of the book.

    Format: Text

    Describe the edition this record represents. Recommended values: 1st to 10th, Revised, Expanded, Special; another value may be given. A new edition is linked to the earlier one in O33; it does not replace it.

    Example: 2nd

    O43Output Series Key: outputSeries
    Level:
    Optional
    Values:
    One value
    Applies to:
    Books, reports

    The publication series to which the output belongs.

    Format: Group of parts

    Give the series name in O43.1 and its number in O43.2.

    O43.1Output Series Name Key: outputSeriesName
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Books, reports

    The title of the series.

    Format: Text

    Use the series title as published.

    Example: Studies in Language Education

    O43.2Output Series Number Key: outputSeriesNumber
    Level:
    Required if it exists
    Values:
    One value
    Applies to:
    Books, reports

    The output’s number within the series.

    Format: Text

    Give the number as published.

    Example: 12

    O44Output Book Format Key: outputBookFormat
    Level:
    Optional
    Values:
    One value
    Applies to:
    Books

    The format of the book this record describes.

    Format: Text

    State the format, such as hardback, paperback or electronic. Each format’s ISBN goes in O28.

    Example: Electronic

    O45Output Degree Key: outputDegree
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Theses, dissertations

    The qualification for which the thesis or dissertation was submitted.

    Format: Text

    Use the qualification as stated by the awarding institution, written as in list 5.32 where it is listed; another degree may be given as text.

    Example: PhD

    O46Output Awarding Institution Key: outputAwardingInstitution
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Theses, dissertations, student projects

    The institution that awarded or supervised the degree or project.

    Format: Group of parts

    Name the actual institution, not the repository hosting the record. Details are given in O46.1–O46.2.

    O46.1Output Awarding Institution Name Key: outputAwardingInstitutionName
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Theses, dissertations, student projects

    The full name of the awarding institution.

    Format: Text

    Use the institution’s official name.

    Example: University of Example

    O46.2Output Awarding Institution ROR Key: ror
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Theses, dissertations, student projects

    The ROR identifier of the awarding institution.

    Format: https://ror.org/ + identifier

    Supply the canonical ROR link for the institution in O46.1.

    O47Output Department Key: outputDepartment
    Level:
    Optional
    Values:
    One value
    Applies to:
    Theses, dissertations, student projects

    The department in which the thesis or project was completed.

    Format: Text

    Contributors’ departments belong in O18.6.2, not here.

    Example: Department of English

    O48Output Version Key: outputVersion
    Level:
    As stated
    Values:
    One value
    Applies to:
    Software and standards (Mandatory); datasets (Recommended)

    The release or version of the resource.

    Format: Text

    Describe this resource’s version, not the version of this schema. Journal items and parts of books or events have no version; a copy of an already published work states its version in O61.

    Example: 1.2.0

    O49Output File Format and Size Key: outputFileFormatAndSize
    Level:
    Retired in 2.0
    Values:
    Multiple values allowed
    Applies to:
    Datasets, software, archival resources

    The format and size of each file of the output.

    Retired in 2.0. Not supplied in records following version 2.0. Each output links to its own page (O21) and full text (O22). The definition below is that of version 1.0.

    Format: Format + size

    Describe each file separately. Use a media type where known, and the size in bytes.

    Example: text/csv; 24576 bytes

    O50Output Event Start Date Key: outputEventStartDate
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Event records

    The date on which the event began.

    Format: Date: YYYY-MM-DD

    Do not use the event’s registration or announcement date.

    Example: 2026-10-08

    O51Output Event End Date Key: outputEventEndDate
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Event records

    The date on which the event ended.

    Format: Date: YYYY-MM-DD

    Must not be earlier than O50. For a one-day event, use the same date; when it is not supplied, the Registry uses O50.

    Example: 2026-10-10

    O57Output Event Type Key: outputEventType
    Level:
    Mandatory
    Values:
    One value
    Applies to:
    Event records

    The kind of scholarly event.

    Format: Controlled value

    Allowed values: see list 5.28.

    Example: Conference

    O58Output Event Mode Key: outputEventMode
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Event records

    Whether the event was held in person, online or both.

    Format: Controlled value

    Every event gives its country (O52).

    Allowed values: see list 5.29.

    Example: Hybrid

    O59Output Event Sub-themes Key: outputEventSubThemes
    Level:
    Optional
    Values:
    Multiple values allowed (up to 15)
    Applies to:
    Event records

    The tracks or sub-themes of the event.

    Format: Text values

    The event’s main theme is its subtitle (O7).

    Example: Language assessment; Inclusive education

    O52Output Place Country Key: outputPlaceCountry
    Level:
    As stated
    Values:
    One value
    Applies to:
    Event records and their parts (Mandatory); archival resources (Recommended)

    The country where the event took place, or where an archival resource was created.

    Format: Country (ISO 3166-1 code)

    Every event gives its country, also when it is held online: the organizing country. A part of an event (a paper, poster, talk or recording) takes the event’s country when it gives none.

    Example: Pakistan (PK)

    O53Output Place City Key: outputPlaceCity
    Level:
    As stated
    Values:
    One value
    Applies to:
    Event records and their parts (Recommended); archival resources (Recommended)

    The city where the event took place, or where an archival resource was created.

    Format: Text

    For an online event, give the organizing city; the mode is given in O58. A part of an event takes the event’s city when it gives none.

    Example: Lahore

    O54Output Archival Reference Code Key: outputArchivalReferenceCode
    Level:
    Recommended
    Values:
    One value
    Applies to:
    Archival resources

    The archive’s own reference code or shelfmark for the item.

    Format: Text

    Give the code exactly as used in the archive’s catalogue.

    Example: MS 1947/12

    O61Output Copy Version Key: outputCopyVersion
    Level:
    Optional
    Values:
    One value
    Applies to:
    Archived Publication Copy

    Which version of an already published work the copy holds.

    Format: Controlled value

    Give the version the copy holds.

    Allowed values: see list 5.30.

    Example: Accepted Manuscript

    5. Controlled Lists

    Some fields accept only values from a fixed list. This section sets out each list. Every value has a code and a label, and a definition where the label alone is not enough. The code is the value carried in JSON and must be used exactly as written. The label is the text shown to people. Languages and countries are not listed here: languages use BCP 47 language tags, and countries use ISO 3166-1 alpha-2 codes. Changes to the lists follow Section 10.

    5.1 Platform Status (P2)

    Platform Status (P2)
    CodeLabelDefinition
    activeActiveThe platform is operating and registering outputs.
    ceasedCeasedThe platform has stopped publishing. Its records and public pages remain.
    inactiveInactiveThe platform is not registering new outputs at present. Its records and public pages remain.
    mergedMergedThe platform has merged into another platform, identified in P26.
    renamedRenamedThe platform continues under a new title or abbreviation and a new NiD, identified in P26.
    suspendedSuspendedSuspended by SEIPID for violating its policies, integrity rules and terms. Its records and public pages remain.

    5.2 Platform Types (P5)

    Platform Types (P5)
    CodeLabelDefinition
    journal_platformJournalA scholarly publication that releases articles and related material under a continuing journal title.
    institutional_repositoryInstitutional RepositoryA platform that collects, manages and provides access to scholarly material of an institution or research community.
    archive_systemArchiveA platform that preserves and provides access to publications, records or other material kept for long-term reference.
    publisherScholarly PressA university press or publisher of scholarly books, textbooks, reference works, literary works, proceedings and reports.
    conference_event_organizerEvent OrganizerAn organization or unit that arranges scholarly events (conferences, seminars, webinars, workshops) and registers each event and its outputs.

    5.3 Platform Subtypes (P6)

    Platform Subtypes (P6)
    CodeLabelPlatform typeDefinition
    discipline_specific_journalDiscipline-Specific JournalJournalA journal focused mainly on one discipline or a specialist area within it.
    multidisciplinary_journalMultidisciplinary JournalJournalA journal covering several disciplines without requiring their methods to be combined.
    interdisciplinary_journalInterdisciplinary JournalJournalA journal publishing research that combines methods, concepts or perspectives from two or more disciplines.
    transdisciplinary_journalTransdisciplinary JournalJournalA journal publishing research that builds shared approaches beyond disciplinary boundaries, often with participants outside academia.
    general_institutional_repositoryGeneral Institutional RepositoryInstitutional RepositoryA repository covering a broad range of an institution’s scholarly material.
    theses_dissertations_repositoryTheses & Dissertations RepositoryInstitutional RepositoryA repository mainly collecting theses and dissertations.
    research_outputs_repositoryResearch Outputs RepositoryInstitutional RepositoryA repository mainly collecting outputs of an institution’s researchers.
    data_repositoryData RepositoryInstitutional RepositoryA repository mainly managing research datasets.
    reports_working_papers_repositoryReports & Working Papers RepositoryInstitutional RepositoryA repository mainly collecting technical reports, working papers and similar documents.
    department_or_center_repositoryDepartment / Research Center RepositoryInstitutional RepositoryA repository serving one department, research center or similar unit.
    preprint_server_repositoryPreprint ServerInstitutional RepositoryA repository mainly sharing manuscripts before formal publication, including versions not yet peer reviewed.
    digital_preservation_systemDigital Preservation SystemArchiveAn archive mainly keeping digital material authentic, usable and accessible over time.
    journal_backfile_archiveJournal Backfile ArchiveArchiveAn archive mainly preserving previously published journal issues and articles.
    heritage_special_collectionsHeritage & Special CollectionsArchiveAn archive mainly managing historical, cultural or other distinctive collections.
    audiovisual_archiveAudiovisual ArchiveArchiveAn archive mainly managing sound recordings, moving images and related material.
    web_archiveWeb ArchiveArchiveAn archive mainly capturing and preserving websites at particular points in time.
    general_mixed_archiveGeneral / Mixed ArchiveArchiveAn archive with substantial holdings across several material types.
    book_monograph_publisherBook / Monograph PublisherScholarly PressA publisher mainly producing scholarly books and monographs.
    university_pressUniversity PressScholarly PressA publishing operation affiliated with a university or similar institution.
    textbook_educational_publisherTextbook / Educational PublisherScholarly PressA publisher mainly producing textbooks and teaching materials.
    conference_proceedings_publisherConference Proceedings PublisherScholarly PressA publisher mainly producing collections of conference contributions.
    report_series_publisherReport Series PublisherScholarly PressA publisher mainly producing scholarly, technical or policy reports in continuing series.
    general_mixed_publisherGeneral / Mixed PublisherScholarly PressA publisher producing several kinds of scholarly publications.
    recurring_conference_seriesRecurring Conference SeriesEvent OrganizerAn organizer responsible for successive editions of a named conference.
    academic_society_organizerAcademic / Professional SocietyEvent OrganizerAn academic or professional society that organizes scholarly events.
    university_event_unitUniversity Conference / Event UnitEvent OrganizerA university unit responsible for organizing scholarly events.
    workshop_seminar_seriesWorkshop / Seminar / Webinar SeriesEvent OrganizerAn organizer mainly responsible for a continuing series of workshops or seminars.
    general_event_organizerGeneral / Mixed Event OrganizerEvent OrganizerAn organizer managing several kinds of scholarly events.

    5.4 Organization Types (P27.2)

    Organization Types (P27.2)
    CodeLabelDefinition
    university_collegeUniversity or collegeA degree-awarding higher education institution.
    research_instituteResearch instituteAn organization whose main activity is research.
    learned_societyLearned society or associationA membership body serving a discipline or profession.
    government_public_bodyGovernment or public bodyA government department, agency or other public body.
    commercial_publisherCommercial publisherA company that publishes for profit.
    non_profit_organizationNon-profit organizationA non-profit body that is not one of the types above.
    otherOtherAn organization of another kind.

    5.5 Related Platform Relations (P26)

    Related Platform Relations (P26)
    CodeLabelDefinition
    continuesContinuesThis platform continues the identified earlier platform.
    continued_byContinued byThis platform has been continued by the identified later platform.
    merged_intoMerged intoThis platform has merged into the identified platform.
    merged_fromMerged fromThis platform was formed by merging the identified platform into it.

    5.6 Publication Models (P29)

    Publication Models (P29)
    CodeLabelDefinition
    issue_basedIssue-basedContent is released in numbered issues.
    continuousContinuousEach article is published as soon as it is ready, without waiting for an issue.
    combinedCombinedArticles are published as they are ready and later grouped into issues.

    5.7 Publication Frequencies (P30)

    Publication Frequencies (P30)
    CodeLabelDefinition
    monthlyMonthlyTwelve issues a year.
    bimonthlyBimonthlySix issues a year.
    quarterlyQuarterlyFour issues a year.
    triannualTriannualThree issues a year.
    semiannualSemiannualTwo issues a year.
    annualAnnualOne issue a year.
    irregularIrregularIssues have no fixed schedule.

    5.8 Peer Review Types (P33)

    Peer Review Types (P33)
    CodeLabelDefinition
    double_blindDouble blindReviewers and authors do not know each other’s identities.
    single_blindSingle blindReviewers know the authors’ identities; authors do not know the reviewers’.
    open_reviewOpen reviewReviewers and authors know each other’s identities, and reviews may be published.
    editorial_reviewEditorial reviewEditors assess the work without external reviewers.
    not_peer_reviewedNot peer reviewedThe content is not peer reviewed.

    5.9 Author Fee Types (P34)

    Author Fee Types (P34)
    CodeLabelDefinition
    no_feeNo feeAuthors are not charged to submit or publish.
    article_processing_chargeArticle processing charge (APC)Authors are charged when an article is accepted or published.
    submission_feeSubmission feeAuthors are charged when a manuscript is submitted.
    other_author_feeOther author feeAny other charge to authors, such as a fast-track or page charge.

    5.10 Link and Indexing Services (P25, P36)

    Link and Indexing Services (P25, P36)
    CodeLabelUsed inDefinition
    wikidataWikidataP25The platform’s Wikidata item.
    rorRORP25Retired in 2.0. The organization’s ROR is given in P27.7.
    isniISNIP25The platform’s ISNI record.
    viafVIAFP25The platform’s VIAF authority record.
    wikipediaWikipediaP25The platform’s Wikipedia article.
    openalexOpenAlexP25The platform’s OpenAlex source record.
    google_scholarGoogle ScholarP25The platform’s Google Scholar profile.
    researchgateResearchGateP25The platform’s ResearchGate page.
    ssrnSSRNP25The platform’s SSRN page.
    sherpaSherpa Romeo / OpenDOARP25The platform’s Sherpa Romeo or OpenDOAR record.
    re3datare3dataP25The repository’s re3data record.
    dblpDBLPP25The platform’s DBLP record.
    linkedinLinkedInP25The platform’s official LinkedIn page.
    facebookFacebookP25The platform’s official Facebook page.
    xX (Twitter)P25The platform’s official X account.
    youtubeYouTubeP25The platform’s official YouTube channel.
    alifindexAlifIndexP36The journal’s AlifIndex record.
    doajDOAJP36The journal’s DOAJ record.
    scopusScopusP36The journal’s Scopus source record.
    wosWeb of ScienceP36The journal’s Web of Science record.
    abdcABDCP36The journal’s ABDC Journal Quality List entry.
    doabDOABP36The scholarly press’s record in the Directory of Open Access Books.

    5.11 Output Status (O3)

    Output Status (O3)
    CodeLabelDefinition
    activeActiveThe output is current. It stays Active when it is corrected or when a newer version or edition exists; these are linked through O33.
    removedRemovedThe record has been removed by SEIPID. Its SEIPID still opens a page that identifies the work and states the reason.
    replacedReplacedThe record has been replaced by a newer record, which identifies it in O33 with Replaces.
    retractedRetractedThe output has been retracted. The retraction notice is linked in O33.
    withdrawnWithdrawnThe output has been withdrawn by its platform.

    5.12 Content Types (O4, P37)

    Content Types (O4, P37)
    CodeLabelPlatform typesDefinition
    research_articleResearch ArticleJournalAn article reporting original research.
    review_articleReview ArticleJournalAn article reviewing existing research on a topic.
    short_communicationShort Communication / Brief ReportJournalA short article reporting brief or early findings.
    editorialEditorialJournalAn article written by or for the editors.
    case_reportCase Report / Case StudyJournalAn article describing a particular case.
    commentaryCommentary / PerspectiveJournalAn article giving a view on a topic or on other work.
    letter_to_editorLetter to the EditorJournalA letter responding to published work or raising a matter.
    book_reviewBook ReviewJournalA review of a published book.
    methodology_protocolMethodology / Protocol PaperJournalAn article describing a method or study protocol.
    data_paperData Paper / Data NoteJournalAn article describing a dataset.
    correctionCorrectionJournalA notice correcting an error in a published work.
    retractionRetraction NoticeJournalA notice retracting a published work.
    expression_of_concernExpression of ConcernJournalA notice the journal publishes while it checks concerns about a published work. It must relate to that work with “Expresses concern about” (Section 7.3).
    abstract_bookAbstract BookJournal · Repository · Scholarly Press · Event OrganizerA collection of abstracts, usually from an event.
    thesisThesisRepositoryA thesis submitted for a degree.
    dissertationDissertationRepositoryA dissertation submitted for a degree.
    student_projectStudent Project / Final-Year ProjectRepositoryA project completed as part of a course of study.
    technical_reportTechnical ReportRepository · Scholarly PressA report of technical or research work, including a report in a series.
    standardStandardRepository · Scholarly PressA standard, specification or set of guidelines issued by an organization.
    working_paperWorking PaperRepositoryA paper shared for discussion before formal publication.
    policy_briefPolicy BriefRepositoryA short document presenting research for policy decisions.
    preprintPreprintRepositoryA manuscript shared before peer review or formal publication.
    article_recordArticle Record / Accepted ManuscriptRepositoryA repository copy of an article, such as an accepted manuscript.
    conference_paperConference PaperRepository · Event OrganizerA paper presented at a conference.
    conference_posterConference PosterRepository · Event OrganizerA poster presented at a conference.
    presentationPresentation / SlidesRepository · Event OrganizerSlides from a lecture, talk or keynote.
    datasetDatasetRepositoryA collection of research data.
    software_codeSoftware / Code RecordRepositorySoftware or source code.
    educational_resourceEducational ResourceRepositoryMaterial made for teaching or learning.
    patentPatentRepositoryA patent or published patent application.
    archived_publicationArchived Publication CopyArchiveA preserved copy of a published work.
    historical_manuscriptDigitized Manuscript / Historical DocumentArchiveA digitized manuscript or historical document.
    photograph_imagePhotograph / ImageArchiveA photograph or other still image.
    artwork_objectArtwork / ObjectArchiveA record of an artwork or a physical object.
    audio_recordingAudio RecordingRepository · ArchiveA sound recording.
    video_recordingVideo RecordingRepository · ArchiveA moving-image recording.
    oral_historyOral History InterviewArchiveA recorded interview preserving personal memories or testimony.
    newspaper_issueDigitized Newspaper IssueArchiveA digitized issue of a newspaper.
    printed_ephemeraPamphlet / Poster / EphemeraArchiveA pamphlet, poster, leaflet or other short-lived printed item.
    mapMap / PlanArchiveA map or chart.
    web_snapshotWeb SnapshotArchiveA captured copy of a web page or website.
    archived_datasetArchived DatasetArchiveA preserved copy of a dataset.
    collection_recordCollection RecordArchiveA description of a collection as a whole.
    book_monographBook (Full Monograph)Repository · Scholarly PressA complete book by one or more authors.
    edited_bookEdited BookScholarly PressA book of chapters by different authors, assembled by editors.
    book_chapterBook ChapterRepository · Scholarly PressA chapter within a book.
    textbookTextbookScholarly PressA book made for teaching a subject.
    reference_workReference Work (Encyclopedia / Dictionary / Handbook)Scholarly PressAn encyclopedia, dictionary, handbook or similar work made of entries.
    reference_work_entryReference Work EntryScholarly PressAn entry in an encyclopedia, dictionary or handbook.
    literary_workLiterary Work (Poetry / Fiction / Drama)Scholarly PressA creative work of poetry, fiction or drama. A study about literature is a Book or Book Chapter.
    literary_pieceLiterary Piece (Poem / Story / Play)Scholarly PressOne poem, story or play within a literary work or an edited book.
    conference_proceedingsProceedings VolumeScholarly PressA published collection of conference papers.
    proceedings_paperProceedings PaperScholarly PressA paper within published conference proceedings.
    conference_abstractAbstractScholarly Press · Event OrganizerOne abstract within an abstract book.
    white_paperWhite PaperScholarly PressAn authoritative report on an issue or proposal.
    eventEvent RecordEvent OrganizerA record of a scholarly event itself.
    proceedings_volumeProceedings VolumeEvent OrganizerA volume of an event’s proceedings issued by the organizer.
    session_recordingSession / Keynote RecordingEvent OrganizerA recording of a session or keynote.

    5.13 Contributor Types (O18.1)

    Contributor Types (O18.1)
    CodeLabelDefinition
    individualPersonAn individual person.
    organizationOrganizationAn organization or group author.

    5.14 Contributor Roles (O18.3)

    Contributor Roles (O18.3)
    CodeLabelDefinition
    authorAuthorWrote or created the work.
    editorEditorPrepared or oversaw the work for publication.
    translatorTranslatorTranslated the work from another language.
    supervisorSupervisor / AdvisorSupervised or advised a thesis, dissertation or project.
    contributorContributorContributed in a way not covered by another role.
    compilerCompilerGathered and arranged material from other sources.
    illustratorIllustratorCreated illustrations or images.
    producerProducer / DirectorProduced or directed audio, video or event material.
    contact_personContact PersonThe contact for questions about the work.
    hosting_institutionHosting InstitutionHosts the work, or the facility where it was produced.
    distributorDistributorDistributes the work.
    rights_holderRights HolderHolds rights in the work.
    sponsorSponsorSponsored or supported the work.
    data_collectorData CollectorCollected the data the work reports or contains.
    data_curatorData CuratorOrganized, cleaned or maintained the data.
    researcherResearcherTook part in the research without being an author.
    project_leaderProject LeaderLed the project that produced the work.
    project_managerProject ManagerManaged the project that produced the work.
    organizerOrganizerOrganized the event (event records).
    conference_chairConference Chair / ConvenerChaired or convened the event (event records).
    organizing_committeeOrganizing Committee MemberServed on the organizing committee (event records).
    program_committeeScientific / Program Committee MemberServed on the scientific or programme committee (event records).
    keynote_speakerKeynote SpeakerGave a keynote address (event records).
    speakerSpeaker / PresenterSpoke or presented at the event (event records).
    session_chairSession Chair / ModeratorChaired or moderated a session (event records).
    panelistPanelistTook part in a panel discussion (event records).
    host_institutionHost InstitutionThe institution that hosted the event (event records).
    otherOtherAnother role.

    5.15 CRediT Roles (O18.4)

    CRediT Roles (O18.4)
    CodeLabelDefinition
    conceptualizationConceptualizationForming the ideas and research goals.
    data_curationData curationManaging and maintaining the research data.
    formal_analysisFormal analysisStatistical, mathematical or other formal analysis.
    funding_acquisitionFunding acquisitionObtaining the financial support.
    investigationInvestigationCarrying out the research and collecting evidence.
    methodologyMethodologyDesigning the methods or models.
    project_administrationProject administrationManaging and coordinating the research activity.
    resourcesResourcesProviding materials, instruments, samples or other resources.
    softwareSoftwareDeveloping the software used.
    supervisionSupervisionOverseeing and leading the research, including mentoring.
    validationValidationChecking that results can be reproduced.
    visualizationVisualizationPreparing figures and visual presentation of data.
    writing_original_draftWriting - original draftWriting the first draft.
    writing_review_editingWriting - review and editingReviewing, commenting on or revising the text.

    5.16 Identifier Types (O28.1, O34)

    Identifier Types (O28.1, O34)
    CodeLabelDefinition
    seipidSEIPIDThe persistent identifier of a work registered in the SEIPID Registry.
    previous_seipidPrevious SEIPIDAn earlier SEIPID of the same work.
    doiDOIDigital Object Identifier.
    isbnISBNInternational Standard Book Number, format not stated.
    isbn_hardbackISBN HardbackISBN of the hardback edition.
    isbn_paperbackISBN PaperbackISBN of the paperback edition.
    isbn_ebookISBN eBookISBN of the electronic edition.
    isbn_pdfISBN PDFISBN of the PDF edition.
    isbn_epubISBN EPUBISBN of the EPUB edition.
    isbn_audiobookISBN AudiobookISBN of the audiobook edition.
    issnISSNISSN of a print serial.
    eissneISSNISSN of an electronic serial.
    issn_lISSN-LLinking ISSN covering all editions of a serial.
    pmidPMIDPubMed identifier.
    pmcidPMCIDPubMed Central identifier.
    arxivarXivarXiv identifier.
    handleHandleHandle System identifier.
    arkARKArchival Resource Key.
    urnURNUniform Resource Name.
    oclcOCLCOCLC (WorldCat) number.
    lccnLCCNLibrary of Congress Control Number.
    wos_accessionWeb of Science Accession NumberWeb of Science record number.
    scopus_eidScopus EIDScopus record identifier.
    openalex_idOpenAlex IDOpenAlex work identifier.
    wikidata_qidWikidata QIDWikidata item identifier.
    semantic_scholar_idSemantic Scholar IDSemantic Scholar paper identifier.
    dblp_idDBLP IDDBLP record key.
    clinicaltrials_nctClinicalTrials.gov NCTClinical trial registration number.
    patent_numberPatent NumberPatent number, with its issuing office.
    isrcISRCInternational Standard Recording Code.
    ismnISMNInternational Standard Music Number.
    isanISANInternational Standard Audiovisual Number.
    iswcISWCInternational Standard Musical Work Code.
    local_idLocal IDAn identifier assigned by the platform itself.
    repository_idRepository IDAn identifier assigned by a repository.
    urlURLA web address that identifies the work.
    uriURIA persistent URI that identifies the work.
    otherOtherAnother identifier; give its kind with the value.

    5.17 Relation Types (O33.1)

    Each relation has a reverse. When this output “Corrects” another work, the other work is “Corrected by” this one.

    Relation Types (O33.1)
    CodeLabelReverse labelDefinition
    is_part_ofPart ofHas partThis output is part of the identified work, such as a chapter of a book or a paper of a proceedings volume.
    is_translation_ofTranslation ofHas translationThis output is a translation of the identified work.
    is_new_version_ofNew version ofHas new versionThis output is a later, substantively changed version of the identified work.
    is_new_edition_ofNew edition ofHas new editionThis publication is a later edition of the identified publication.
    is_version_ofVersion ofHas versionThis output is a version of the identified work, without being newer.
    is_preprint_ofPreprint ofHas preprintThis output is a preprint of the identified published or accepted work.
    is_supplement_toSupplement toHas supplementThis output provides supplementary material for the identified work.
    is_review_ofReview ofReviewed byThis output reviews the identified work.
    uses_data_fromUses data fromData used byThis output uses data from the identified dataset or work.
    correctsCorrectsCorrected byThis correction notice corrects an error in the identified work.
    retractsRetractsRetracted byThis retraction notice retracts the identified work.
    expresses_concernExpresses concern aboutConcern expressed byThis expression of concern is about the identified work.
    replacesReplacesReplaced byThis output is designated as a replacement for the identified work. Both records remain.

    5.18 Broad Subject Areas (P18, O15)

    Version 2.0 has 11 broad subject areas. The groups of version 1.0 are retired and keep their codes.

    Broad Subject Areas (P18, O15)
    CodeLabelDefinition
    mathematics_computingMathematics and ComputingMathematics, statistics, computing and information systems.
    physical_sciencesPhysical SciencesPhysics, astronomy and chemistry.
    earth_environmental_sciencesEarth and Environmental SciencesGeology, the atmosphere, oceans, water and the environment.
    life_sciencesLife SciencesBiology in all its branches, biotechnology and neuroscience.
    engineering_technologyEngineering and TechnologyEngineering in all its branches and applied technologies.
    medicineMedicineBasic medical sciences, clinical medicine and surgery.
    health_sciencesHealth SciencesDentistry, pharmacy, nursing, public health and allied health.
    agricultural_veterinary_sciencesAgriculture, Food and Veterinary SciencesAgriculture, food, forestry, fisheries and veterinary medicine.
    social_sciences_humanitiesSocial Sciences and HumanitiesSocial sciences, education, law and the humanities.
    business_economicsBusiness, Economics and ManagementEconomics, finance, accounting, management and marketing.
    arts_architecture_designArts, Architecture and DesignArchitecture, planning, design and the arts.
    natural_sciencesNatural SciencesRetired in 2.0. Now Physical Sciences.
    medical_health_sciencesMedical and Health SciencesRetired in 2.0. Now Medicine.
    social_sciencesSocial SciencesRetired in 2.0. Now Social Sciences and Humanities.
    humanities_artsHumanities and the ArtsRetired in 2.0. Now Social Sciences and Humanities.
    multidisciplinaryMultidisciplinaryRetired in 2.0. Select the area of the main discipline.
    interdisciplinaryInterdisciplinaryRetired in 2.0. Select the area of the main discipline.
    otherOtherRetired in 2.0. Select the area of the main discipline.

    5.19 Disciplines (P19, O16)

    Each discipline belongs to one broad subject area; the larger areas show their disciplines under headings. Each area also has a General choice for work that covers the area as a whole. Disciplines of version 1.0 that changed are retired and keep their codes; the last part of the table shows where each now belongs.

    Disciplines (P19, O16)
    CodeLabel
    Mathematics and Computing
    general_mathematics_computingGeneral Mathematics and Computing
    mathematicsMathematics
    applied_mathematicsApplied Mathematics
    statisticsStatistics and Probability
    computer_scienceComputer Science
    artificial_intelligenceArtificial Intelligence
    data_scienceData Science
    software_engineeringSoftware Engineering
    information_systemsInformation Systems
    cybersecurityCybersecurity
    computer_networksComputer Networks
    Physical Sciences
    general_physical_sciencesGeneral Physical Sciences
    physicsPhysics
    condensed_matter_physicsCondensed Matter Physics
    optics_photonicsOptics and Photonics
    nuclear_particle_physicsNuclear and Particle Physics
    astronomy_space_scienceAstronomy and Astrophysics
    chemical_sciencesChemistry
    organic_chemistryOrganic Chemistry
    inorganic_chemistryInorganic Chemistry
    physical_chemistryPhysical Chemistry
    analytical_chemistryAnalytical Chemistry
    polymer_sciencePolymer Science
    Earth and Environmental Sciences
    general_earth_environmental_sciencesGeneral Earth and Environmental Sciences
    geologyGeology
    geophysicsGeophysics
    atmospheric_climate_scienceAtmospheric and Climate Science
    oceanography_marine_scienceOceanography and Marine Science
    hydrology_water_resourcesHydrology and Water Resources
    environmental_sciencesEnvironmental Science
    remote_sensing_gisRemote Sensing and GIS
    natural_hazards_disaster_managementNatural Hazards and Disaster Management
    Life Sciences
    general_life_sciencesGeneral Life Sciences
    biochemistryBiochemistry
    molecular_cell_biologyMolecular and Cell Biology
    genetics_genomicsGenetics and Genomics
    microbiologyMicrobiology
    plant_sciencesPlant Sciences
    zoologyZoology
    ecology_evolutionEcology and Evolution
    biotechnologyBiotechnology
    bioinformaticsBioinformatics
    neuroscienceNeuroscience
    biophysicsBiophysics
    Engineering and Technology
    general_engineering_technologyGeneral Engineering and Technology
    Engineering and Technology › Civil and Environmental
    civil_engineeringCivil Engineering
    transportation_engineeringTransportation Engineering
    environmental_engineeringEnvironmental Engineering
    Engineering and Technology › Electrical, Electronic and Computer
    electrical_engineeringElectrical Engineering
    energy_engineeringPower and Energy Engineering
    electronics_engineeringElectronics Engineering
    telecommunications_engineeringTelecommunications Engineering
    computer_engineeringComputer Engineering
    Engineering and Technology › Mechanical, Chemical and Materials
    mechanical_engineeringMechanical Engineering
    robotics_automationMechatronics and Robotics
    aerospace_engineeringAerospace Engineering
    chemical_engineeringChemical Engineering
    petroleum_gas_engineeringPetroleum and Gas Engineering
    mining_engineeringMining Engineering
    materials_engineeringMaterials Science and Engineering
    textile_engineeringTextile Engineering
    nanotechnologyNanotechnology
    Engineering and Technology › Industrial, Biomedical and Management
    industrial_manufacturing_engineeringIndustrial and Manufacturing Engineering
    medical_engineeringBiomedical Engineering
    engineering_managementEngineering Management
    Medicine
    general_medicineGeneral Medicine
    Medicine › Basic Medical Sciences
    anatomy_physiologyAnatomy and Physiology
    pathology_laboratory_medicinePathology and Laboratory Medicine
    pharmacology_toxicologyPharmacology and Toxicology
    immunologyImmunology
    forensic_medicineForensic Medicine
    Medicine › Clinical Medicine
    internal_medicineInternal Medicine
    cardiologyCardiology
    gastroenterology_hepatologyGastroenterology and Hepatology
    nephrology_urologyNephrology and Urology
    endocrinology_diabetesEndocrinology and Diabetes
    pulmonologyPulmonology and Respiratory Medicine
    hematologyHematology
    rheumatologyRheumatology
    oncologyOncology
    neurologyNeurology
    psychiatryPsychiatry
    pediatricsPediatrics
    dermatologyDermatology
    infectious_diseasesInfectious Diseases
    family_community_medicineFamily and Community Medicine
    radiology_medical_imagingRadiology and Medical Imaging
    anesthesia_critical_care_emergencyAnesthesia, Critical Care and Emergency
    traditional_eastern_medicineTraditional and Complementary Medicine
    Medicine › Surgery
    surgerySurgery
    orthopedicsOrthopedics
    obstetrics_gynecologyObstetrics and Gynecology
    ophthalmologyOphthalmology
    otorhinolaryngologyEar, Nose and Throat
    Health Sciences
    general_health_sciencesGeneral Health Sciences
    dentistryDentistry
    pharmacyPharmacy
    nursingNursing and Midwifery
    public_healthPublic Health and Epidemiology
    nutritionNutrition and Dietetics
    rehabilitationPhysical Therapy and Rehabilitation
    sports_exercise_scienceSports and Exercise Science
    medical_educationMedical Education
    health_management_policyHealth Management and Policy
    optometry_vision_scienceOptometry and Vision Science
    speech_language_therapySpeech and Language Therapy
    Agriculture, Food and Veterinary Sciences
    general_agricultural_veterinary_sciencesGeneral Agriculture, Food and Veterinary Sciences
    agronomy_crop_scienceAgronomy and Crop Science
    horticultureHorticulture
    plant_protectionPlant Protection
    soil_scienceSoil Science
    agricultural_engineeringAgricultural Engineering
    agricultural_economics_extensionAgricultural Economics and Extension
    forestryForestry and Rangeland
    fisheriesFisheries and Aquaculture
    food_scienceFood Science and Technology
    animal_dairy_scienceAnimal Science and Dairy
    veterinary_scienceVeterinary Medicine
    plant_breeding_geneticsPlant Breeding and Genetics
    entomologyEntomology
    Social Sciences and Humanities
    general_social_sciences_humanitiesGeneral Social Sciences and Humanities
    Social Sciences and Humanities › Social Sciences
    psychologyPsychology
    sociologySociology
    anthropologyAnthropology
    social_workSocial Work and Social Policy
    gender_studiesGender Studies
    population_studiesPopulation Studies
    development_studiesDevelopment Studies
    social_economic_geographyHuman Geography
    political_sciencePolitical Science
    international_relationsInternational Relations
    peace_conflict_studiesPeace and Conflict Studies
    public_administrationPublic Administration and Governance
    area_regional_studiesArea and Regional Studies
    criminologyCriminology
    media_communicationsMedia and Communication
    library_information_scienceLibrary and Information Science
    Social Sciences and Humanities › Education
    educational_sciencesEducation
    teacher_educationTeacher Education
    educational_psychology_assessmentEducational Psychology and Assessment
    educational_leadership_policyEducational Leadership and Policy
    special_inclusive_educationSpecial and Inclusive Education
    educational_technologyEducational Technology
    Social Sciences and Humanities › Law
    lawLaw
    international_law_human_rightsInternational Law and Human Rights
    criminal_law_justiceCriminal Law and Justice
    constitutional_public_lawConstitutional and Public Law
    business_commercial_lawBusiness and Commercial Law
    religious_customary_lawReligious and Customary Law
    Social Sciences and Humanities › Humanities
    historyHistory
    archaeology_heritageArchaeology and Heritage
    philosophy_ethicsPhilosophy and Ethics
    religious_studiesReligious Studies and Theology
    islamic_studiesIslamic Studies
    linguisticsLinguistics
    applied_linguistics_language_teachingApplied Linguistics and Language Teaching
    literatureLiterature
    translation_studiesTranslation Studies
    cultural_studiesCultural Studies
    Business, Economics and Management
    general_business_economicsGeneral Business, Economics and Management
    economicsEconomics
    financeFinance
    accountingAccounting
    bankingBanking
    business_managementManagement
    marketingMarketing
    human_resource_managementHuman Resource Management
    operations_supply_chainOperations and Supply Chain
    entrepreneurship_innovationEntrepreneurship and Innovation
    tourism_hospitalityTourism and Hospitality
    islamic_banking_financeIslamic Banking and Finance
    project_managementProject Management
    Arts, Architecture and Design
    general_arts_architecture_designGeneral Arts, Architecture and Design
    architectureArchitecture
    urban_regional_planningUrban and Regional Planning
    visual_artsVisual Arts
    designDesign
    musicMusic
    performing_artsPerforming Arts
    film_media_artsFilm and Media Arts
    interior_designInterior Design
    fashion_textile_designFashion and Textile Design
    landscape_architectureLandscape Architecture
    Retired in 2.0 (codes of version 1.0)
    artificial_intelligence_data_scienceArtificial Intelligence and Data Science — now Artificial Intelligence
    information_systems_cybersecurityInformation Systems and Cybersecurity — now Information Systems
    earth_sciencesEarth Sciences — now General Earth and Environmental Sciences
    biological_sciencesBiological Sciences — now General Life Sciences
    other_natural_sciencesOther Natural Sciences — now General Physical Sciences
    architecture_planningArchitecture and Planning — now Architecture
    electrical_power_engineeringElectrical and Power Engineering — now Electrical Engineering
    electronics_telecommunicationsElectronics and Telecommunications — now Electronics Engineering
    other_engineering_technologiesOther Engineering and Technologies — now General Engineering and Technology
    basic_medicineBasic Medical Sciences — now General Medicine
    clinical_medicineClinical Medicine — now General Medicine
    health_biotechnologyHealth Biotechnology — now Biotechnology
    other_medical_sciencesOther Medical Sciences — now General Medicine
    agricultureAgriculture — now General Agriculture, Food and Veterinary Sciences
    agricultural_biotechnologyAgricultural Biotechnology — now Biotechnology
    other_agricultural_sciencesOther Agricultural Sciences — now General Agriculture, Food and Veterinary Sciences
    accounting_financeAccounting and Finance — now General Business, Economics and Management
    other_social_sciencesOther Social Sciences — now General Social Sciences and Humanities
    languages_literatureLanguages, Linguistics and Literature — now General Social Sciences and Humanities
    visual_arts_designVisual Arts and Design — now Visual Arts
    performing_arts_musicPerforming Arts and Music — now Performing Arts
    other_humanitiesOther Humanities — now General Social Sciences and Humanities

    5.20 Licences (P21, O24)

    Licences (P21, O24)
    CodeLabelDefinition
    cc_by_4_0CC BY 4.0Reuse for any purpose, with credit.
    cc_by_sa_4_0CC BY-SA 4.0Reuse with credit; adaptations under the same licence.
    cc_by_nd_4_0CC BY-ND 4.0Reuse with credit; no adaptations.
    cc_by_nc_4_0CC BY-NC 4.0Non-commercial reuse, with credit.
    cc_by_nc_sa_4_0CC BY-NC-SA 4.0Non-commercial reuse with credit; adaptations under the same licence.
    cc_by_nc_nd_4_0CC BY-NC-ND 4.0Non-commercial reuse with credit; no adaptations.
    cc0_1_0CC0 1.0Rights waived; free reuse without conditions.
    public_domain_markPublic Domain MarkThe work is already free of known copyright.
    odc_by_1_0ODC-BY 1.0Database reuse, with credit.
    odbl_1_0ODbL 1.0Database reuse with credit; adapted databases under the same licence.
    pddl_1_0PDDL 1.0Database dedicated to the public domain.
    mitMITSoftware: permissive reuse, keeping the licence notice.
    apache_2_0Apache 2.0Software: permissive reuse, with a patent grant.
    gpl_3_0_or_laterGPL 3.0 or laterSoftware: derived works under the same licence.
    lgpl_3_0_or_laterLGPL 3.0 or laterSoftware library: linking permitted; changes to the library under the same licence.
    agpl_3_0_or_laterAGPL 3.0 or laterSoftware: as GPL, also covering use over a network.
    bsd_2_clauseBSD 2-ClauseSoftware: permissive reuse, keeping the notice.
    bsd_3_clauseBSD 3-ClauseSoftware: as BSD 2-Clause, without using the holder’s name for endorsement.
    all_rights_reservedAll rights reservedNo reuse beyond what law allows without the holder’s permission.
    custom_licenseCustom licenceA licence not in this list. Its text or link is supplied with the record.
    unknownUnknownNo evidence of the licence is available.

    5.21 Copyright Holder Categories (P22, O25)

    Copyright Holder Categories (P22, O25)
    CodeLabelDefinition
    author_creatorAuthor / CreatorThe authors or creators of the work.
    publisher_platformPublisher / PlatformThe publisher or the platform.
    institution_organizationInstitution / OrganizationAn institution or organization, such as a university.
    conference_societyConference / SocietyA conference organizer or learned society.
    government_public_bodyGovernment / Public BodyA government or public body.
    employer_work_for_hireEmployer / Work for HireThe creator’s employer, under a work-for-hire arrangement.
    multiple_rightsholdersMultiple RightsholdersSeveral holders share the copyright.
    otherOtherAnother holder, named with the record.
    unknownUnknownThe holder is not known.

    5.22 Access Models (P23, O23)

    Access Models (P23, O23)
    CodeLabelDefinition
    open_accessOpen accessFree to read and reuse under an open licence.
    free_to_readFree to readFree to read, without an open reuse licence.
    public_accessPublic accessAvailable to the public without charge under public-access terms.
    subscriptionSubscriptionAccess requires a subscription.
    hybridHybridA subscription platform where some items are open access.
    delayed_openDelayed open accessBecomes free to read after a set period.
    embargoedEmbargoedClosed until a stated date.
    restrictedRestrictedAccess is limited to authorized users.
    institution_onlyInstitution-only accessAccess is limited to members of an institution.
    member_loginMember / login accessAccess requires a member account.
    request_onlyRequest-only accessAvailable on request.
    reading_room_onlyReading-room / on-site accessAvailable on site only.
    preservation_onlyPreservation-onlyKept for preservation and not offered for access.
    paid_accessPaid accessEach item is bought individually.
    mixed_accessMixed accessDifferent items have different access conditions.
    metadata_onlyMetadata onlyOnly the description is available; the content is not online.
    not_publicNot publicly accessibleNot accessible to the public.
    unknownUnknownThe access conditions are not known.

    5.23 Data Availability (O30)

    Data Availability (O30)
    CodeLabelDefinition
    public_repositoryOpenly available in a public repositoryThe data can be accessed in a public repository.
    in_articleIncluded in the article / supplementary filesThe data are part of the output or its supplementary files.
    on_requestAvailable from the authors on reasonable requestThe data are provided by the authors on request.
    restrictedAvailable with restrictionsAccess is limited by third-party rights, a licence or the sensitivity of the data.
    not_availableNot availableThe data cannot be shared for ethical, legal or privacy reasons.
    embargoedAvailable laterThe data will become available after an embargo.
    not_applicableNot applicableNo new data were created or analysed.
    otherOtherAnother arrangement, described in the output.

    5.24 Ethics Status (O31)

    Ethics Status (O31)
    CodeLabelDefinition
    approvedApproved by an ethics committee / IRBThe research was approved by an ethics committee or institutional review board.
    exemptExempt / waived by an ethics committeeAn ethics committee exempted the research or waived approval.
    not_requiredNot requiredNo human or animal participants were involved.
    not_applicableNot applicableEthical approval does not apply to this output.

    5.25 Competing Interests (O32)

    Competing Interests (O32)
    CodeLabelDefinition
    noneNo competing interestsThe output states that there are no competing interests.
    declaredCompeting interests declaredThe output declares one or more competing interests.

    5.26 AI Use (O55)

    AI Use (O55)
    CodeLabelDefinition
    noneNo AI usedThe output states that no AI tool was used to prepare it.
    languageAI used for language editingAI tools were used only to edit the language.
    contentAI used for content or analysisAI tools were used to produce content or analysis; the output describes how.

    5.27 Withdrawal Reasons (O56)

    The Registry records the reason when it confirms a withdrawal request.

    Withdrawal Reasons (O56)
    CodeLabelDefinition
    duplicateDuplicate publicationThe work was published more than once.
    mistakePublished by mistakeThe work was published in error.
    author_requestAuthor's requestThe authors asked for the work to be withdrawn.
    otherOther reasonAnother reason, stated in the request.

    5.28 Event Types (O57)

    Event Types (O57)
    CodeLabelDefinition
    conferenceConference
    congressCongress
    symposiumSymposium
    seminarSeminar
    webinarWebinar
    workshopWorkshop
    colloquiumColloquium
    summitSummit
    lectureLecture / Talk
    panel_discussionPanel Discussion
    trainingTraining / Course
    schoolSummer / Winter School
    otherOther

    5.29 Event Modes (O58)

    Every event gives its country (O52), also when it is held online.

    Event Modes (O58)
    CodeLabelDefinition
    in_personIn personHeld at a physical place.
    onlineOnlineHeld online only.
    hybridHybridHeld at a physical place and online.

    5.30 Copy Versions (O61)

    Which version of an already published work an archived copy holds.

    Copy Versions (O61)
    CodeLabelDefinition
    submitted_versionSubmitted VersionThe version first submitted for publication.
    accepted_manuscriptAccepted ManuscriptThe author’s final version accepted after review, before the publisher’s layout.
    proofProofA typeset version before final publication.
    published_versionPublished VersionThe version as published.
    corrected_published_versionCorrected Published VersionThe published version with later corrections.
    not_knownNot KnownThe version is not known.

    5.31 Editorial Team Roles (P53.1)

    Editorial Team Roles (P53.1)
    CodeLabelDefinition
    deputy_editorDeputy Editor
    managing_editorManaging Editor
    editorEditor
    section_editorSection Editor
    associate_editorAssociate Editor
    guest_editorGuest Editor
    board_memberEditorial Board Member
    advisory_memberAdvisory Board Member

    5.32 Degrees (O45)

    Recommended values: the degree is written as listed here. Another degree may be given as text.

    Degrees (O45)
    GroupValues
    DoctoralPhD · DPhil · EdD · DBA · DSc · DLitt · LLD · DEng · DMus · Habilitation
    PostdoctoralPostdoctoral Research
    Medical and Dental PostgraduateFCPS · MCPS · MD · MS (Surgery) · MDS · FRCS · MRCP
    Master'sMPhil · MS · MSc · MSc (Hons) · MA · MBA · MEd · LLM · MEng · MPA · MPH · MFA · MArch · MSN · MSW · MCom · MLIS · MCS · MIT · MRes · MPharm
    Professional First DegreeMBBS · BDS · Pharm-D · DPT · DVM · LLB · BArch
    Bachelor'sBS · BSc · BSc (Hons) · BA · BA (Hons) · BBA · BEd · BE · BEng · BFA · BCom · BCS · BSN · BPharm
    Associate and DiplomaAssociate Degree · Postgraduate Diploma · Diploma · Certificate

    6. Content-Type Requirements

    Every output must meet the requirements in Section 4 that apply to all outputs. In addition, its content type (O4) places it in one of the families below, which sets the further fields that the content type requires. Where Section 4 marks a field “Mandatory (when the content type requires it)”, this table states which content types require it. A field not listed for a family keeps the level shown in Section 4. Fields that do not apply to a content type are left empty. Broad Subject Area and Disciplines (O15, O16) are Mandatory for every family except archival and heritage resources and events, where they are Optional.

    Requirements by content-type family
    Family and content typesMandatoryRecommendedFurther rules
    Journal research articles Research Article · Review Article · Short Communication / Brief Report · Case Report / Case Study · Methodology / Protocol Paper · Data Paper / Data Note

    Language (O5)

    Abstract (O11)

    Keywords, 3–7 (O13)

    References (O34)

    Volume (O36)

    Submitted Date (O20.1)

    Accepted Date (O20.3)

    An item published Online First may leave Volume empty while its Online First Date (O20.4) is supplied.

    Journal commentary Commentary / Perspective

    Language (O5)

    References (O34)

    Volume (O36)

    —

    Abstract and keywords are optional. The Online First rule applies.

    Other journal items Editorial · Letter to the Editor · Book Review · Correction · Retraction Notice · Expression of Concern

    Language (O5)

    Volume (O36)

    Abstract (O11)

    A correction must link the work it corrects with “Corrects” (O33). A retraction notice must link the work it retracts with “Retracts” (O33). An expression of concern must link the work it is about with “Expresses concern about” (O33). A correction, retraction notice or expression of concern may relate only to a work of the same platform. A book review should link the reviewed book with “Review of” (O33) where it has an identifier. The Online First rule applies.

    Theses and student projects Thesis · Dissertation · Student Project / Final-Year Project

    Language (O5)

    Abstract (O11)

    Keywords, 3–7 (O13)

    Awarding Institution (O46)

    Degree (O45), for theses and dissertations, written as in list 5.32

    Awarding Institution ROR (O46.2)

    Supervisor listed in Contributors (O18) with the role Supervisor / Advisor

    The awarding institution is the institution that awarded the degree, not the repository hosting the record.

    Reports, standards, preprints and manuscript records Technical Report · Standard · Working Paper · Policy Brief · White Paper · Preprint · Article Record / Accepted Manuscript

    Language (O5)

    Abstract or description (O11)

    Keywords, 3–7 (O13)

    Version (O48), for a standard

    References (O34)

    Series (O43), for reports in a series

    A preprint should link its published version with “Preprint of” (O33) once one exists. An accepted manuscript should link the published article with “Version of” (O33).

    Conference and proceedings papers Conference Paper · Proceedings Paper

    Language (O5)

    Abstract (O11)

    Keywords, 3–7 (O13)

    References (O34)

    “Part of” (O33): a proceedings paper links its Proceedings Volume; a conference paper of an Event Organizer links the event or one of its Proceedings Volumes

    Pages (O39) and Chapter or Paper Number (O41), where printed

    “Part of” (O33) linking the event, for repository copies of conference papers

    A paper of an Event Organizer takes the event’s dates and place when it gives none (Section 7.2).

    Posters, presentations and session recordings Conference Poster · Presentation / Slides · Session / Keynote Recording · Abstract, for Event Organizers

    Language (O5)

    “Part of” (O33) linking the registered event’s SEIPID, for outputs of Event Organizers

    Abstract or description (O11)

    “Part of” (O33) linking the event, for repository copies

    An abstract of an Event Organizer links its Abstract Book. An item of an Event Organizer takes the event’s dates and place when it gives none (Section 7.2).

    Books and complete volumes Book (Full Monograph) · Edited Book · Textbook · Reference Work · Literary Work · Proceedings Volume · Abstract Book

    Language (O5)

    Abstract or description (O11)

    Series (O43)

    Book Format (O44)

    Each ISBN is recorded in Other Identifiers (O28) as Required if it exists. Edition (O42) is Required if it exists. A Proceedings Volume or Abstract Book of an Event Organizer links its event with “Part of” (O33). A literary work is a creative work; a study about literature is a Book.

    Chapters and reference-work entries Book Chapter · Reference Work Entry · Literary Piece · Abstract

    Language (O5)

    “Part of” (O33) linking its parent: a Book Chapter a Book, Edited Book or Textbook; a Reference Work Entry a Reference Work; a Literary Piece a Literary Work or Edited Book; an Abstract an Abstract Book

    Abstract (O11)

    Pages (O39) and Chapter or Paper Number (O41), where printed

    Pages (O39) are Required if they exist. The ISBN of the book belongs to the book’s record, not to the chapter. The Registry numbers each part in its SEIPID (Section 7.2).

    Datasets Dataset · Archived Dataset

    Description (O11)

    Version (O48)

    Created Date (O20.7)

    Collected Date (O20.9)

    Language (O5) may be omitted when no natural language applies. A dataset used by another output is linked from that output with “Uses data from” (O33).

    Software and code Software / Code Record

    Description (O11)

    Version (O48)

    —

    The licence (O24) must name the exact software licence. Language (O5) may be omitted when no natural language applies.

    Educational resources and patents Educational Resource · Patent

    Language (O5)

    Description (O11)

    Keywords (O13)

    —

    Archival and heritage resources Archived Publication Copy · Digitized Manuscript / Historical Document · Photograph / Image · Artwork / Object · Audio Recording · Video Recording · Oral History Interview · Digitized Newspaper Issue · Pamphlet / Poster / Ephemera · Map / Plan · Web Snapshot · Collection Record

    Description (O11)

    Archival Reference Code (O54)

    Place Country and City (O52, O53)

    Record known creators, or responsible custodians, in Contributors (O18) with their actual roles. A custodian is not described as the author. Language (O5) may be omitted when no natural language applies. An Archived Publication Copy states the version it holds in Copy Version (O61).

    Events Event Record

    Event Start Date (O50)

    Event End Date (O51)

    Event Type (O57)

    Place Country (O52)

    Event Mode (O58)

    Place City (O53)

    Description (O11)

    Organizers in Contributors (O18)

    The event is recorded separately from its organizing platform and from the contributions presented at it. Contributions link to the event with “Part of” (O33). An event is registered by an Event Organizer before its contributions. Every event gives its country, also when it is held online: the organizing country and city. The theme is the subtitle (O7); sub-themes are given in O59; Edition (O42) where the event is one of a series. The people of an event take the event roles of list 5.14 (Organizer, Conference Chair / Convener, committee members, speakers).

    7. Relationships and References

    Outputs are connected to other works in two ways. Related Works (O33) records a relationship between this output and another identified work, such as a correction, a translation or a chapter’s book. References (O34) record the works the output cites. This section sets out how both are recorded.

    7.1 Direction and reverse relations

    A relation is recorded once, on the output that makes the statement. The relation type (O33.1) states how this output relates to the work identified in O33.2. When the related work has a SEIPID, the Registry shows the reverse relation on that work’s record automatically, using the reverse label in list 5.17. The relation is not entered a second time on the other record. A related work without a SEIPID is identified by its DOI or another persistent identifier where one exists, and otherwise by its link.

    Direction and reverse relations
    Recorded onRelation (O33)Shown on the related work
    A correction noticeCorrects 001:example:2025n7Corrected by: the correction notice
    A book chapterPart of: the book’s SEIPIDHas part: the chapter
    A translationTranslation of: the original’s SEIPIDHas translation: the translation
    A research articleUses data from: the dataset’s SEIPIDData used by: the article

    7.2 Parts and parent works

    Use “Part of” (O33) to identify the parent book, reference work, proceedings volume or event. Section 6 sets the requirement level for each content type and platform type. For a book chapter or a contribution registered by an Event Organizer, the parent book or event must already have a persistent SEIPID, which is recorded in O33.2. The parent work lists its parts through the reverse relation; parts are not entered on the parent. Each part keeps its own persistent SEIPID, contributors and metadata. It does not take the parent’s authors or identifiers. The ISBN of a book, for example, stays with the book.

    A part may have only a parent of the right kind:

    • Scholarly Press: a Book Chapter is part of a Book, Edited Book or Textbook; a Reference Work Entry of a Reference Work; a Literary Piece of a Literary Work or Edited Book; a Proceedings Paper of a Proceedings Volume; an Abstract of an Abstract Book.
    • Event Organizer: each event is registered first as an Event Record. Its Proceedings Volumes and Abstract Books are part of the event; a Conference Paper is part of the event or of one of its Proceedings Volumes; an Abstract is part of an Abstract Book; a Conference Poster, Presentation or Session / Keynote Recording is part of the event.
    • Whole books, reports, standards, white papers and journal items are never parts, except the Proceedings Volumes and Abstract Books of an Event Organizer, which are parts of their event.

    The SEIPID of a part shows its place: an event is numbered with e, a book with b and a part with c, each counted under its parent by the Registry, for example 014:example-eo:2026e1 (an event), 014:example-eo:2026e1b1 (a proceedings volume of that event) and 014:example-eo:2026e1b1c3 (the third part registered under that volume). The count is not the number printed in the publication, which is given in O41. A number already used is never given again.

    A part registered under an event, or under a book of an event, takes the parent’s licence (O24), copyright holder (O25) and access model (O23) when it gives none; a contribution of an Event Organizer also takes the event’s dates (O50, O51) and place (O52, O53) when it gives none. A part may give its own values.

    7.3 Corrections, retractions, withdrawals and versions

    • Correction: a correction is registered as its own output with the content type Correction, and links the corrected work with “Corrects”. The corrected work shows “Corrected by”. This relation does not itself change the work’s status (O3).
    • Expression of concern: while a journal checks concerns about a published work, it may register an expression of concern as its own output with the content type Expression of Concern, linking the work with “Expresses concern about”. The work shows “Concern expressed by” and a notice on its public page. The work’s status (O3) does not change. The outcome is registered later as a correction or a retraction notice.
    • Retraction: a retraction notice is registered as its own output with the content type Retraction Notice, and links the retracted work with “Retracts”. When the notice is registered, the retracted work’s status (O3) becomes Retracted and the Registry records its Retracted Date (O20.12): the notice’s publication date. Its record and public page remain available, marked as retracted.
    • Withdrawal: a withdrawal is recorded at the request of the platform that registered the output and confirmed by the Registry. The request gives the date of withdrawal, between the publication date and the day of the request, and the reason (list 5.27). The status (O3) becomes Withdrawn and the Withdrawn Date (O20.13) and Withdrawal Reason (O56) are recorded. The record and public page remain available, marked as withdrawn.
    • Same platform: a correction, retraction notice or expression of concern relates only to a work registered under the same platform.
    • New version or edition: a substantially changed version, or a new edition, is registered as a new output with its own SEIPID and links the earlier one with “New version of” or “New edition of”. Both records remain. Metadata corrections follow 7.6.
    • Replacement: “Replaces” is used only where the source explicitly designates one work as replacing another. Both records remain.

    No SEIPID record is deleted, and no SEIPID is reassigned to another work.

    7.4 Reference entries

    References (O34) list the works cited by the output, in their published order: the first entry is reference 1, the second is reference 2, and so on. Each entry keeps its reference text exactly as published. Where the cited work has a SEIPID, DOI or other persistent identifier, the identifier is added to the entry. References are separate from relations: citing a work does not create a relation in O33.

    The reference list names each cited work once, in full, in one citation style. It does not contain footnotes or short forms such as “Ibid.”, “Id.”, “op. cit.”, “supra” or “See also”, and no entry is repeated.

    7.5 Integrity of relationships and references

    A registered record must continue to describe the same scholarly output. It must not be altered to represent an unrelated work, fabricate authorship, conceal a retraction or misstate access or rights.

    Relations and references must describe real connections between works. The following are not permitted:

    • references to works that the output does not cite
    • references or relations added to increase the citations of a work, an author or a platform, including arranged exchanges of citations between platforms
    • citations required by editors or reviewers without scholarly reason
    • relations between unrelated works

    Relations and references on an output are added and changed by the platform that registered it. The Registry may correct a relation that does not meet this section. SEIPID may exclude a reference that breaches this section from citation counts and apply the measures set out in its policies and terms.

    7.6 Metadata corrections

    Small corrections to metadata are made by editing the existing record and do not create a new persistent SEIPID. Formal corrections and retractions are registered as separate outputs under 7.3.

    8. Validation and Conformance

    This section sets out the common rules for field values and records, and what it means for a platform or output record to conform to version 2.0 of the SEIPID Metadata Schema.

    8.1 Text

    Text is written in Unicode (UTF-8). It must not contain HTML or other markup. Special characters, including mathematical symbols and letters of any script, are written as Unicode characters. Leading and trailing spaces and repeated spaces are removed. Abstracts and descriptions may contain paragraph breaks. Character limits stated in a field’s description, such as 50–800 characters for P16 or 59 characters for O8, include spaces and punctuation.

    8.2 Dates

    Dates are written as YYYY-MM-DD. When only the month or year is known, they are written as YYYY-MM or YYYY. A day or month is never added to make a date look complete. A period is written as a start date and an end date, and the end must not be earlier than the start. A publication date may not be later than the date the output is registered. Event dates and the Embargo End Date may be in the future; the Submitted, Revised, Accepted, Online First, Posted, Created and Collected dates may not.

    The dates of an output follow their natural order: Submitted (O20.1) is not later than any Revised date (O20.2); the last Revised date is not later than Accepted (O20.3); Accepted is not later than Online First (O20.4); and Submitted, Accepted and Online First are not later than the publication date (O19). The Embargo End Date (O20.10) is not earlier than the publication date. A record whose dates do not follow this order fails validation.

    8.3 Links

    Links are full addresses beginning with https://. An http:// link is permitted only when the site offers no secure version. Each link must identify the page or resource specified by its field and must not contain a temporary session code. A general home page must not replace a link to a specific output or policy. Public metadata pages must be accessible without a login. Links to restricted full text must respect the output’s stated access conditions.

    8.4 Identifiers

    Each identifier must follow the rules of its own scheme and identify the entity described by the field. A valid format alone does not establish that the identifier belongs to that entity.

    Identifier checks
    IdentifierCheck
    NiD, SEIPIDPersistent identifiers assigned by the Registry, not chosen or reassigned by a submitter. An output record carries its platform’s existing NiD (O1) and its assigned SEIPID (O2).
    XPENIDWritten as the XPENID itself: initials, “-XPEN”, the year of issue, a hyphen and a number of four or more digits, such as SA-XPEN2025-0057. It must belong to an existing XPENID record
    ORCID iDWritten as a link to an ORCID record, with a valid check digit
    RORWritten as a link to an existing ROR record
    ISSN, eISSNEight characters in the form 1234-5679, with a valid check digit
    ISBNThirteen digits, or ten for older books, with a valid check digit
    DOIBegins with “10.” followed by a prefix, a slash and a suffix

    8.5 Codes, languages, countries and amounts

    Controlled values are written using the codes in Section 5, exactly as listed. Languages use BCP 47 language tags, such as en or ur. Countries use ISO 3166-1 alpha-2 codes, such as PK. Amounts of money are written as a number with an ISO 4217 currency code, such as 50.00 USD.

    8.6 Empty and placeholder values

    A field with no information is omitted only when its requirement level permits. Placeholder text such as “N/A”, “-”, “none”, “nil” or “not available” must not stand in for missing information. Values explicitly permitted by a field or its controlled list remain valid in that field. These include none in list 5.25, “Independent researcher” (O18.6.1), “Not arranged yet” (P35.11), “Not Known” (list 5.30) and Unknown where a controlled list includes it.

    8.7 Duplicate records

    The same work must not be registered more than once. A DOI must not belong to more than one SEIPID record. A new version or edition is a distinct output, linked to the earlier one under Section 7.3; it is not a duplicate.

    8.8 Validation results

    A record fails validation when an applicable Mandatory or Required if it exists field is missing, a supplied value does not meet its field’s rules, or a rule linking fields is not met. Omitting a Recommended or Optional field does not cause validation to fail. Every supplied value must follow the field’s rules, regardless of its requirement level.

    8.9 Conformance

    • Output record: an output record conforms to version 2.0 of the SEIPID Metadata Schema when it meets every applicable Mandatory and Required if it exists field in Section 4, the requirements of its content type in Section 6, the controlled lists in Section 5, the relationship and integrity rules in Section 7, and this section.
    • Platform record: a platform record conforms to version 2.0 when it meets every applicable Mandatory and Required if it exists field in Section 3, including the requirements for its platform type, the controlled lists in Section 5 and this section.
    • Journal policy metadata: conformance concerns the metadata required by P35, including links to the journal’s own published policies. It does not certify the journal’s implementation of those policies.
    • Version: every record represented in JSON states the schema version it follows, using the key schemaVersion, for example "schemaVersion": "2.0". Rules for records and versions are set out in Section 10.3.
    • Claims: a platform or system may state that its records conform to the SEIPID Metadata Schema 2.0 only when they meet this section.

    9. Worked Examples

    This section shows complete output records written in JSON, covering every platform type. Example 1 is the public record 001:xijir:2025n4; the other examples use invented names and example.org addresses. Long texts are shortened with “…”, and long lists show only their first entries.

    9.1 Writing compound values

    Some fields hold a value made of several pieces, such as an ISSN with its edition or a fee with its amount and currency. Unless the field has numbered parts of its own, these pieces are written as a small group using the following sub-keys:

    Compound-value sub-keys
    Sub-keyHoldsExample
    valueThe identifier itself"3005-8457"
    editionPrint or electronic, for an ISSN"electronic"
    categoryA code from a controlled list"author_creator"
    typeA type code, such as a fee type or identifier type"no_fee"
    nameA name"Example University"
    affiliationThe affiliation of a named person"Example University"
    serviceA service code from list 5.10"wikidata"
    urlA link"https://…"
    relationA relation code from list 5.5"merged_into"
    nidThe NiD of a related platform"001:xijir"
    termA subject term (P20, O17; retired in 2.0)"Applied linguistics"
    disciplineA discipline code from list 5.19"linguistics"
    languageA language tag"en"
    textA text: an abstract or description in its language, or a reference as published"…"
    amountAn amount of money, such as an author fee"50.00"
    currencyAn ISO 4217 currency code"USD"
    formatA media type (O49; retired in 2.0)"text/csv"
    sizeA size in bytes (O49; retired in 2.0)24576
    startThe first date of a period"2000-01-01"
    endThe last date of a period"2024-12-31"

    9.2 Output records

    Example 1: Journal research article

    {
  "schemaVersion": "2.0",
  "nid": "001:xijir",
  "seipid": "001:xijir:2025n4",
  "outputStatus": "active",
  "outputContentType": "research_article",
  "outputLanguage": ["en"],
  "outputOriginalTitle": "Impact of Graphic Illustrations on English Vocabulary Acquisition in Pakistani Dyslexic Students",
  "outputShortTitle": "Visual English Vocabulary for Dyslexic Pakistani Students",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "This study investigates the impact of graphic illustrations on short- and long-term vocabulary acquisition among Pakistani students with and without dyslexia. …" }
  ],
  "outputKeywords": ["graphic illustration", "dyslexia", "vocabulary acquisition", "multimedia learning", "mixed factorial design", "inclusive education", "Pakistan"],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["psychology", "general_social_sciences_humanities"],
  "outputContributors": [
    {
      "outputContributorType": "individual",
      "outputContributorName": "Saba Akmal",
      "outputContributorGivenNames": "Saba",
      "outputContributorFamilyName": "Akmal",
      "outputContributorRole": "author",
      "outputContributorCreditRoles": ["conceptualization", "formal_analysis", "investigation", "methodology", "writing_original_draft", "writing_review_editing"],
      "outputCorrespondingAuthor": true,
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "COMSATS University",
            "outputAffiliationCountry": "PK"
        }
      ],
      "xpenid": "SA-XPEN2025-0057"
    }
  ],
  "outputPublicationDate": "2025-05-15",
  "outputTargetPageLink": "https://xijir.com/index.php/en/article/view/41",
  "outputAccessModel": "open_access",
  "outputLicence": "cc_by_4_0",
  "outputCopyrightHolder": { "category": "author_creator" },
  "outputOtherIdentifiers": [
    { "outputIdentifierType": "doi", "outputIdentifierValue": "10.5281/zenodo.15423059" }
  ],
  "outputDataAvailability": "on_request",
  "outputEthicsStatus": "approved",
  "outputCompetingInterests": "none",
  "outputReferences": [
    { "text": "Afflerback, P., Pearson, P. D., & Paris, S. G. (2008). Clarifying differences between reading skills and reading strategies. The Reading Teacher, 61(5), 364–373. https://doi.org/10.1598/RT.61.5.1", "type": "doi", "value": "10.1598/RT.61.5.1" },
    { "text": "Alderson, J. C. (2000). Assessing reading. Cambridge, UK: Cambridge University Press." }
  ],
  "outputVolume": "2",
  "outputIssue": "2",
  "outputPages": "1–19"
}

    Example 2: Thesis

    {
  "schemaVersion": "2.0",
  "nid": "014:exu-ir",
  "seipid": "014:exu-ir:2024n12",
  "outputStatus": "active",
  "outputContentType": "thesis",
  "outputLanguage": ["en"],
  "outputOriginalTitle": "Code-Switching in Urdu-English Classroom Talk",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "This thesis examines how teachers and students switch between Urdu and English during lessons. …" }
  ],
  "outputKeywords": ["code-switching", "classroom discourse", "Urdu", "English language teaching"],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["applied_linguistics_language_teaching"],
  "outputContributors": [
    {
      "outputContributorType": "individual",
      "outputContributorName": "Ayesha Khan",
      "outputContributorGivenNames": "Ayesha",
      "outputContributorFamilyName": "Khan",
      "outputContributorRole": "author",
      "outputCorrespondingAuthor": true,
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "Example University",
            "outputAffiliationDepartment": "Department of English",
            "outputAffiliationCountry": "PK"
        }
      ]
    },
    {
      "outputContributorType": "individual",
      "outputContributorName": "Imran Ali",
      "outputContributorGivenNames": "Imran",
      "outputContributorFamilyName": "Ali",
      "outputContributorRole": "supervisor",
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "Example University",
            "outputAffiliationCountry": "PK"
        }
      ]
    }
  ],
  "outputPublicationDate": "2024-09",
  "outputTargetPageLink": "https://repository.example.edu/handle/123/456",
  "outputPdfLink": "https://repository.example.edu/bitstream/123/456/thesis.pdf",
  "outputAccessModel": "open_access",
  "outputLicence": "cc_by_nc_4_0",
  "outputCopyrightHolder": { "category": "author_creator", "name": "Ayesha Khan" },
  "outputDegree": "MPhil",
  "outputAwardingInstitution": {
    "outputAwardingInstitutionName": "Example University",
    "ror": "https://ror.org/0abcde123"
  },
  "outputDepartment": "Department of English"
}

    Example 3: Dataset

    {
  "schemaVersion": "2.0",
  "nid": "014:exu-ir",
  "seipid": "014:exu-ir:2025n3",
  "outputStatus": "active",
  "outputContentType": "dataset",
  "outputOriginalTitle": "Rainfall Records for Punjab Districts, 2000–2024",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "Daily rainfall measurements for 36 districts of Punjab. …" }
  ],
  "outputSubjectGroup": "earth_environmental_sciences",
  "outputDisciplines": ["environmental_sciences"],
  "outputContributors": [
    {
      "outputContributorType": "individual",
      "outputContributorName": "Hina Shah",
      "outputContributorGivenNames": "Hina",
      "outputContributorFamilyName": "Shah",
      "outputContributorRole": "author",
      "outputContributorCreditRoles": ["data_curation", "investigation"],
      "outputCorrespondingAuthor": true,
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "Example University",
            "outputAffiliationCountry": "PK",
            "ror": "https://ror.org/0abcde123"
        }
      ]
    }
  ],
  "outputPublicationDate": "2025-02-01",
  "outputOtherDates": {
    "outputCreatedDate": "2025-01-20",
    "outputCollectedDate": { "start": "2000-01-01", "end": "2024-12-31" }
  },
  "outputTargetPageLink": "https://repository.example.edu/handle/123/789",
  "outputAccessModel": "open_access",
  "outputLicence": "cc_by_4_0",
  "outputCopyrightHolder": { "category": "institution_organization", "name": "Example University" },
  "outputFunding": [
    { "outputFunderName": "Example Research Foundation", "outputAwardNumber": "ERF-2024-031" }
  ],
  "outputVersion": "1.0"
}

    Example 4: Book chapter

    {
  "schemaVersion": "2.0",
  "nid": "031:exp-p",
  "seipid": "031:exp-p:2026b1c4",
  "outputStatus": "active",
  "outputContentType": "book_chapter",
  "outputLanguage": ["en"],
  "outputOriginalTitle": "Teaching Reading in Multilingual Classrooms",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "This chapter describes reading activities for classrooms where pupils speak several languages. …" }
  ],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["educational_sciences"],
  "outputContributors": [
    {
      "outputContributorType": "individual",
      "outputContributorName": "Fatima Noor",
      "outputContributorGivenNames": "Fatima",
      "outputContributorFamilyName": "Noor",
      "outputContributorRole": "author",
      "outputCorrespondingAuthor": true,
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "Independent researcher",
            "outputAffiliationCountry": "PK"
        }
      ]
    }
  ],
  "outputPublicationDate": "2026-03",
  "outputTargetPageLink": "https://press.example.org/books/language-education/chapter-4",
  "outputAccessModel": "paid_access",
  "outputLicence": "all_rights_reserved",
  "outputCopyrightHolder": { "category": "publisher_platform", "name": "Example Academic Press" },
  "outputRelatedWorks": [
    { "outputRelationType": "is_part_of", "outputRelatedIdentifier": "031:exp-p:2026b1" }
  ],
  "outputPages": "61–84",
  "outputChapterOrPaperNumber": 4
}

    Example 5: Event record

    {
  "schemaVersion": "2.0",
  "nid": "045:icle-eo",
  "seipid": "045:icle-eo:2026e1",
  "outputStatus": "active",
  "outputContentType": "event",
  "outputLanguage": ["en"],
  "outputOriginalTitle": "International Conference on Language and Education 2026",
  "outputSubtitle": "Languages for Inclusive Classrooms",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "The eighth annual conference on language teaching, linguistics and education. …" }
  ],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["applied_linguistics_language_teaching", "educational_sciences"],
  "outputContributors": [
    {
      "outputContributorType": "organization",
      "outputContributorName": "Example Society for Language Education",
      "outputContributorRole": "organizer"
    }
  ],
  "outputPublicationDate": "2026-10-08",
  "outputTargetPageLink": "https://icle.example.org/2026",
  "outputAccessModel": "open_access",
  "outputLicence": "cc_by_4_0",
  "outputCopyrightHolder": { "category": "conference_society", "name": "Example Society for Language Education" },
  "outputEdition": "8th",
  "outputEventStartDate": "2026-10-08",
  "outputEventEndDate": "2026-10-10",
  "outputEventType": "conference",
  "outputEventMode": "hybrid",
  "outputEventSubThemes": ["Language assessment", "Inclusive education"],
  "outputPlaceCountry": "PK",
  "outputPlaceCity": "Islamabad"
}

    Example 6: Conference paper

    {
  "schemaVersion": "2.0",
  "nid": "045:icle-eo",
  "seipid": "045:icle-eo:2026e1c3",
  "outputStatus": "active",
  "outputContentType": "conference_paper",
  "outputLanguage": ["en"],
  "outputOriginalTitle": "Mobile Apps for Vocabulary Learning in Rural Schools",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "This paper reports a term-long trial of vocabulary apps in rural schools. …" }
  ],
  "outputKeywords": ["mobile learning", "vocabulary", "rural schools"],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["educational_technology"],
  "outputContributors": [
    {
      "outputContributorType": "individual",
      "outputContributorName": "Bilal Ahmed",
      "outputContributorGivenNames": "Bilal",
      "outputContributorFamilyName": "Ahmed",
      "outputContributorRole": "author",
      "outputCorrespondingAuthor": true,
      "outputContributorAffiliation": [
        {
            "outputAffiliationName": "Example Institute of Technology",
            "outputAffiliationCountry": "PK"
        }
      ]
    }
  ],
  "outputPublicationDate": "2026-10-09",
  "outputTargetPageLink": "https://icle.example.org/2026/papers/3",
  "outputAccessModel": "open_access",
  "outputLicence": "cc_by_4_0",
  "outputCopyrightHolder": { "category": "author_creator", "name": "Bilal Ahmed" },
  "outputPeerReviewed": true,
  "outputRelatedWorks": [
    { "outputRelationType": "is_part_of", "outputRelatedIdentifier": "045:icle-eo:2026e1" }
  ],
  "outputReferences": [
    { "text": "Khan, R. (2022). Vocabulary apps in rural classrooms. Example Journal of Education, 8(2), 45–60." }
  ]
}

    Example 7: Archival resource

    {
  "schemaVersion": "2.0",
  "nid": "023:hda-arch",
  "seipid": "023:hda-arch:2026pid15",
  "outputStatus": "active",
  "outputContentType": "historical_manuscript",
  "outputLanguage": ["sd"],
  "outputOriginalTitle": "Land Revenue Register of Thatta District",
  "outputAbstractOrDescription": [
    { "language": "en", "text": "A handwritten register of land revenue collected in the villages of Thatta District. …" }
  ],
  "outputSubjectGroup": "social_sciences_humanities",
  "outputDisciplines": ["history"],
  "outputContributors": [
    {
      "outputContributorType": "organization",
      "outputContributorName": "Heritage Documents Trust",
      "outputContributorRole": "hosting_institution"
    }
  ],
  "outputPublicationDate": "1890",
  "outputTargetPageLink": "https://archive.example.org/items/ms-214-3",
  "outputAccessModel": "open_access",
  "outputLicence": "public_domain_mark",
  "outputCopyrightHolder": { "category": "public_domain_no_known_copyright" },
  "outputPlaceCountry": "PK",
  "outputPlaceCity": "Thatta",
  "outputArchivalReferenceCode": "MS 214/3"
}

    10. Versioning and Change Control

    This section sets out how the SEIPID Metadata Schema changes over time.

    10.1 Version numbers

    Each version has a number in the form major.minor, such as 1.0, 1.1 or 2.0. New controlled-list values are added only in a new version of the schema.

    • Minor version (1.1, 1.2 …): adds or clarifies the schema. Examples are new Recommended or Optional fields, new values in a controlled list, clearer wording and new examples.
    • Major version (2.0, 3.0 …): changes existing requirements, formats or field availability. Examples are a new Mandatory requirement, a changed value format or a retired field.

    10.2 What never changes

    • Field reference numbers, JSON keys and controlled-list codes are never changed or reused. A controlled-list code keeps its meaning in later versions.
    • Fields are never removed. A field no longer in use is marked as retired and stays documented with its number and key.
    • A controlled-list value no longer in use is marked as retired and keeps its code.
    • A field whose meaning changes substantially receives a new number and a new key.
    • A new version never changes or reassigns any NiD or SEIPID.

    10.3 Records and versions

    Every record states the version it follows, using the key schemaVersion, and is validated against that version of the schema. New records follow the version in effect when they are registered. From the issue date of a new version until it takes effect, new records may already follow it; records registered earlier keep the version they followed, and an update made after the new version takes effect follows the new version.

    10.4 Publication and notice

    Each version is published with its issue date, its effective date and a list of its changes by field number. Each subsequent version takes effect no earlier than 30 days after it is published. The correction of an obvious error in the text may take effect immediately. Earlier versions remain available for reference, each at its own permanent address.

    10.5 Change log

    The change log records, for each version, the fields added or retired, the controlled-list values added or retired, changed requirement levels, changed formats and changed wording.

    Change log
    VersionIssuedEffectiveChanges
    2.0Major version: fields retired and added, requirement levels changed. Details in the table below and in Section 1.4.
    1.0First active version. Version 1.0
    Changes in version 2.0 by field number
    FieldChange
    P5Changed wording: the publisher type is named Scholarly Press and the conference type Event Organizer (codes unchanged); an Event Organizer gives only its basic details.
    P6Changed wording: for a journal the subtype states its focus; subtype workshop_seminar_series labelled Workshop / Seminar / Webinar Series.
    P17Changed requirement level: not for Event Organizers.
    P18Changed values and level: 11 broad subject areas (list 5.18); Optional for repositories and archives; not for Event Organizers.
    P19Changed values and rule: 172 disciplines plus a General choice in each area (list 5.19), from any area, at least one from the chosen area.
    P20Retired.
    P21, P22Changed requirement level: Optional for repositories and archives; not for Event Organizers.
    P23Changed requirement level: not for Event Organizers.
    P24Changed requirement level: not for repositories, archives or Event Organizers.
    P33, P34, P35.3, P35.6, P36Changed scope: also Scholarly Presses (Recommended; P36 Optional); P33 no longer for event organizers.
    P37Changed requirement level: Recommended to Mandatory; outputs use only the selected types.
    P38Recommended values added.
    P39Changed requirement level: Recommended for repositories.
    P42Changed format and level: content type values from list 5.12 instead of text; Optional to Mandatory.
    P43Recommended units added.
    P44Retired.
    P48, P49, P50, P51, P52Retired.
    P53 (P53.1–P53.6)Added: Platform Editorial Team.
    O7Changed wording: the subtitle of an event record holds its theme.
    O8Changed rule: made by the Registry when not supplied.
    O14Changed requirement level: Recommended to Optional.
    O15, O16Changed values, level and rule: as P18 and P19; Mandatory when the content type requires them (Section 6).
    O17Retired.
    O18.5Changed rule: the Registry marks the first author when a new record marks no one.
    O18.6Changed number of values: one to up to 3.
    O20.6, O20.8, O20.11, O20.14Retired.
    O20.10Changed requirement level: Mandatory with the access models Embargoed and Delayed open access, otherwise not given.
    O20.12, O20.13Changed: assigned by the Registry (Section 7.3).
    O26, O35, O49Retired.
    O29.4Added: Output Award Title.
    O34Changed rule: each cited work once, in full; no footnotes or short forms.
    O41Changed requirement level: Mandatory to Optional; the Registry numbers parts in their SEIPID.
    O42Changed scope and values: also event records; recommended values added.
    O45Recommended values added (list 5.32).
    O51Changed requirement level: Recommended to Mandatory.
    O52, O53Changed rule: every event gives its country and city, also when held online; parts of events take the event’s place when they give none.
    O55Added: Output AI Use.
    O56Added: Output Withdrawal Reason.
    O57, O58, O59Added: Output Event Type, Event Mode and Event Sub-themes.
    O60Added: Output External Publisher.
    O61Added: Output Copy Version.
    Lists5.2, 5.3 labels changed; 5.10 doab added and ror retired; 5.12 nine content types added and three labels changed; 5.14 fourteen roles added; 5.16 six identifier types added; 5.17 expresses_concern added; 5.18 and 5.19 replaced, earlier codes retired; 5.26–5.32 added.
    Sections 6, 7, 8Content-type requirements, parent rules and SEIPID numbering of parts, expressions of concern, retraction and withdrawal, the reference list and the order of dates.

    10.6 Maintenance and suggestions

    The SEIPID Metadata Schema is maintained by SEIPID, operated by Xpertno Research Center. Suggestions for changes may be sent through the SEIPID contact page.

    References

    This section lists the standards whose rules values in SEIPID records must follow.

    Appendix A: Glossary (informative)

    This glossary explains general terms used in the SEIPID Metadata Schema. Field names are not repeated here; each field is defined in Sections 3 and 4.

    Glossary
    TermMeaning
    AffiliationThe organization with which a contributor was associated for a particular output, as stated in that output.
    CodeThe fixed value written in JSON for an entry in a controlled list, such as open_access. A code is never changed or reused.
    ConformanceMeeting every requirement of this schema that applies to a record, as set out in Section 8.9.
    Content typeThe category of an output, such as Research Article or Dataset, selected from list 5.12.
    ContributorA person or organization credited with a role in producing an output, such as author, editor or supervisor.
    Controlled listA fixed list of permitted values for a field, set out in Section 5.
    FieldOne item of information in a record, identified by a name, a reference number and a JSON key.
    JSON keyThe name under which a field is written in a JSON record, such as outputOriginalTitle.
    MetadataInformation that describes a platform or an output, such as its title, contributors and dates.
    NamespaceThe place in the SEIPID Registry given to a registered scholarly platform, identified by its persistent NiD.
    NiDThe persistent Namespace Identifier assigned by the Registry to a registered scholarly platform, such as 001:xijir.
    OutputA scholarly work or resource registered under a platform, such as an article, thesis, dataset or event record.
    PartA component of a field, numbered under it, such as O18.2 within O18.
    PlatformA journal, institutional repository, archive, scholarly press or event organizer registered in the SEIPID Registry.
    RecordThe complete set of metadata describing one platform or one output.
    ReferenceAn entry for a work cited by an output, recorded in O34.
    RelationA stated connection between an output and another identified work, recorded in O33, such as “Corrects” or “Part of”.
    Requirement levelWhether a field is Mandatory, Required if it exists, Recommended or Optional, as set out in Section 2.
    SEIPIDThe persistent identifier assigned by the Registry to a registered scholarly output, such as 001:xijir:2025n4.
    SEIPID IdraakThe SEIPID service for metrics and analysis of registered outputs.
    SEIPID RasadThe SEIPID service for discovering and tracking citations.
    SEIPID RegistryThe SEIPID service that assigns persistent NiDs and SEIPIDs and keeps their records.
    SubmitterThe account that submits a record on behalf of a platform.

    Apply the standard to scholarly records

    Open SEIPID Diwan portal Read the metadata guide