Indexing & Archiving
ASCR is designed for discoverability and long-term stewardship of the scholarly record. This page explains our metadata, identifiers, harvesting, and preservation practices so authors, indexers, and librarians can integrate our content reliably.
Overview
We align our editorial and technical workflows with widely adopted community standards to ensure that every published article is citable, machine-readable, and preserved. Article-level metadata is registered with persistent identifiers, rendered in human- and machine-friendly formats, and exposed for harvesting. Our approach supports aggregation by scholarly databases and search engines and helps institutions track outputs from their researchers.
Discoverability at a glance
- Crossref DOI registration with canonical links (
https://doi.org/). - Structured data embedded in pages (schema.org/Periodical and ScholarlyArticle via JSON-LD).
- Support for OAI-PMH harvesting in widely used formats (Dublin Core; JATS XML where applicable).
- Clear, consistent license metadata (Creative Commons) for open access and text-and-data mining.
Preservation at a glance
- Multiple layers of redundancy (primary hosting backups, off-site snapshots, and participation with third-party preservation networks where available).
- Fixity checks and versioning practices for updates, corrections, and retractions.
- Persistent landing pages and DOI-based redirects to maintain citation integrity.
Identifiers & Core Metadata
Each article is the center of an identifier graph that improves traceability:
| Identifier | Purpose | Rendered as |
|---|---|---|
| ISSN (online) | Serial identity for cataloging and indexing services. | ASCR — ISSN 2576-9537 |
| DOI (Crossref) | Permanent link to the version of record; basis for updates and relationships (corrections, retractions, datasets, preprints). | https://doi.org/10.xxxx/xxxxx |
| ORCID | Unambiguous author and reviewer identification; supports credit and attribution. | https://orcid.org/0000-000X-XXXX-XXXX |
| ROR | Disambiguates institutions and funders; enables institutional reporting. | https://ror.org/0xxxxxx00 |
| Grant IDs | Links articles to funded projects for compliance and discovery. | As supplied by authors and funders in metadata. |
Formats & Machine-Readability
To enable indexing, citation parsing, and accessibility, ASCR delivers multiple representations of the same content:
- HTML as the primary, accessible version with semantic headings, descriptive links, and schema.org JSON-LD in the page head.
- PDF for print fidelity; generated with tagging for assistive technologies and consistent DOI/ISSN headers and footers.
- JATS XML (where applicable) to support archiving and downstream text-mining; includes references with DOIs and standardized contributor roles.
- Supplementary files (datasets, code, multimedia) linked from the article with persistent identifiers when available.
Harvesting via OAI-PMH
ASCR supports harvesting through the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), enabling libraries and indexers to ingest records automatically. We expose commonly used metadata prefixes such as oai_dc (Dublin Core) and, when configured, jats for article-level JATS XML. Requests can be scoped by date ranges and sets (e.g., journal sections or issues) to support incremental harvesting.
- Identify the repository:
?verb=Identify - List available metadata formats:
?verb=ListMetadataFormats - Harvest recent records:
?verb=ListRecords&metadataPrefix=oai_dc&from=YYYY-MM-DD - Retrieve a single record:
?verb=GetRecord&metadataPrefix=oai_dc&identifier=oai:journal:articleID
Note: Exact endpoint path and set specifications are provided to indexers and librarians upon request to ensure stable integrations.
How We Work with Discovery Services
Our content is structured to be compatible with major discovery channels. Inclusion decisions are controlled by each service’s independent criteria; our role is to meet technical and policy expectations, respond promptly to queries, and keep metadata consistent. Typical integration paths include:
Search & Aggregation
Machine-readable schema.org, sitemaps, and accessible HTML support inclusion by scholarly search engines. References include live DOIs to improve citation graph accuracy and linking.
Directories & Indexes
We align with widely recognized transparency and best-practice principles for directories in scholarly communication. Our policies on peer review, licensing, fees/waivers, and ethics are public and consistent.
Linking & Analytics
Crossref deposits include reference lists and license URLs, enabling accurate outbound/inbound linking, funder reporting, and content registration for updates, corrections, and retractions.
Digital Preservation Strategy
Preserving the version of record is essential. ASCR maintains multiple layers of protection across infrastructure and, where eligible, through participation in third-party preservation networks. Our strategy includes:
- Primary platform backups: routine, versioned snapshots and off-site storage for rapid restoration.
- Third-party preservation networks: integration with recognized initiatives (e.g., community preservation services such as LOCKSS/CLOCKSS or Portico) depending on eligibility and publisher arrangements.
- Format durability: preference for open or well-documented formats (HTML, PDF/A, XML) with embedded identifiers and license metadata.
- Fixity and audit: periodic integrity checks with documented remediation procedures.
Versioning, Corrections & Retractions
We maintain a transparent version-of-record policy. Post-publication updates are handled as follows:
- Minor updates (e.g., typographical fixes) are documented in the article’s change log.
- Corrections address substantive errors that do not invalidate conclusions; notices are linked to the article and assigned DOIs.
- Retractions are issued when findings are unreliable due to error or misconduct; the original article remains accessible with a clear retraction notice, and all versions are interlinked via Crossref relations.
- Expressions of concern may be issued while investigations are ongoing, with follow-up notices as appropriate.
All notices include reasons for the change and links to superseding or related records where relevant to keep the scholarly record coherent.
Data, Software & Supplementary Materials
Indexers and readers benefit when datasets and code are easy to find. Authors are encouraged to deposit materials in trusted repositories and to cite them formally. We recognize datasets and software as first-class research outputs and register links in article metadata when supplied.
| Asset | Recommended practice | Indexing implications |
|---|---|---|
| Datasets | Deposit in a domain or general repository; assign DOI or other PID; include README and variable dictionary. | Improves reuse and data citation tracking. |
| Code | Archive a release (e.g., in Zenodo/GitHub integration) with a DOI; specify license and environment details. | Enables reproducibility and linking by indexers that parse software citations. |
| Multimedia | Provide accessible captions, alt text, and formats compatible with web playback; include permissions credits. | Enhances accessibility and discoverability through media metadata. |
For Indexers & Librarians
If you operate a knowledge base, discovery layer, or repository, the following summary may help you configure ingestion pipelines. For integration details, please contact the editorial office.
| Endpoint / Resource | Purpose | Notes |
|---|---|---|
| Journal homepage | Human-readable entry point; links to issues, articles, policies. | Includes schema.org Periodical markup. |
| Article pages | Version of record; references link out with DOIs. | JSON-LD with ScholarlyArticle and license data in the head. |
| OAI-PMH | Automated harvesting of records. | Supports oai_dc; additional formats on request. |
| Sitemap(s) | Discovery for crawlers. | Updated regularly; includes article and policy pages. |
| Crossref | DOI registration and relations (corrections, retractions, datasets). | Metadata includes license URLs and funding data when provided. |
Frequently Asked Questions
Are articles indexed automatically after publication?
Indexing services set their own inclusion policies and schedules. Our role is to provide complete, standards-compliant metadata and accessible content so services can discover and evaluate the journal efficiently.
Do you deposit reference lists?
Where possible, we include references with DOIs in our metadata deposits to strengthen the citation graph and enable accurate linking.
Can I mirror ASCR content?
Mirroring is subject to licensing and preservation agreements. Librarians running preservation nodes should contact the editorial office for specific guidance and, if needed, plugin configuration.
How do I report a broken link or metadata inconsistency?
Please email the editorial office with the article DOI, the affected field, and a short description. We prioritize metadata corrections to maintain discoverability.
Contact for Indexers & Librarians
For OAI-PMH details, preservation coordination, or bulk metadata exports, contact: editorial@clinsurgeryjournal.com · production@clinsurgeryjournal.com