Base endpoint

CJNCP’s platform exposes an OAI-PMH base URL (sometimes referred to as the “OAI endpoint”). In many OJS/PKP and journal platforms this takes one of the following forms:

• https://www.nursingpracticejournal.com/oai (common on hosted journal platforms)
• https://www.nursingpracticejournal.com/index.php/index/oai (typical for OJS 3 installations)
• https://www.nursingpracticejournal.com/index.php/journalPath/oai (multi-journal OJS setups)

If your library needs the exact endpoint for this instance, contact the editorial office; we will confirm the configured base URL and sets. The legacy site signals OAI compatibility but may not display the literal endpoint on every page.

Supported metadata formats

Harvesters can request records in widely used formats. The following are typically available on journal platforms and are supported for CJNCP harvesting:

• Dublin Core (oai_dc): baseline, broadly compatible across repositories and library systems.
• Modified DC / DataCite (oai_datacite or platform-specific): includes richer fields for identifiers and contributors where supported.
• PKP/OJS native schemas (when enabled): provide fine-grained article and issue metadata for downstream mapping.

Article pages and the journal site also embed human- and machine-readable licensing signals (e.g., CC licenses) to clarify reuse rights.

Example requests

Replace {BASE} with the confirmed OAI endpoint for CJNCP. These requests are safe to run in a browser or via curl for quick testing.

Typical ListRecords response (truncated)

<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/">
2025-09-22T12:00:00Z
{BASE}

A Case-Study of the Anatomy of a Miscommunication...
Pritchard, C.
Latham, J.
2018
https://www.nursingpracticejournal.com/articles/cjncp-aid1006.php</dc:identifier
>
doi:10.29328/journal.cjncp.1001006
Creative Commons license as stated on the article page



xyz123...

Your repository may render the response differently; use UTF-8 and treat resumption tokens as opaque.

Sets and scoping

Harvesters can limit requests to specific sets when a repository exposes them (e.g., journal-wide sets, issue sets, article types). This reduces payloads and supports selective re-harvests. Use ListSets to discover available setSpec values, then pass &set= in your ListRecords/ListIdentifiers calls.

For multi-journal platforms, sets often follow predictable patterns (for example, journal:cjncp). Check your Identify and ListSets results to confirm exact naming.

Incremental harvesting

To keep local repositories current without re-downloading everything, run incremental harvests:

• Use from and until parameters with the repository’s supported granularity (see Identify).
• Process and store resumptionToken responses for large result sets; resume until no token is returned.
• Re-harvest recently updated windows (e.g., last 7–14 days) to catch metadata corrections and post-publication updates.
• Throttle requests reasonably (e.g., 1–2 per second) and back off on HTTP 429/503 responses.

Field mapping (practical guide)

Below are the most common CJNCP fields and how they map in oai_dc. Local crosswalks may add richer mappings (e.g., to MARC, MODS, DataCite, or schema.org).

Best practices for librarians and harvesters

• Normalize identifiers: Canonicalize DOIs (e.g., https://doi.org/) and CJNCP article URLs; store both.
• Respect license signals: Populate local rights fields from dc:rights and, where available, license URIs; CJNCP articles are published under Creative Commons terms.
• Preserve versioning: If an article receives a correction or update, re-index the record; CJNCP maintains the scholarly record and publishes corrections transparently.
• Accessibility metadata: Where your system supports it, store captions/alt-text pointers for figures and indicate the availability of accessible HTML galleys.
• Stability checks: If your harvester runs nightly, include a small overlap window (e.g., re-harvest the prior 7 days) to capture late updates.

Troubleshooting and support

Still stuck? Contact the editorial office (see journal website) with the failing query URL, timestamp, and the response snippet. We’ll help verify endpoint status and configuration.

Compliance, openness, and discoverability

CJNCP is an open-access journal with content intended for wide reuse. Licensing and repository policies on the site confirm Creative Commons reuse and support for archiving. Our OAI-PMH exposure complements article-level schema.org metadata and human-readable license notices. Together, these help services such as search engines, institutional discovery layers, and aggregator platforms discover CJNCP content.

Frequently asked questions

Do you expose full text via OAI-PMH?

OAI-PMH transports metadata. Full text remains on article pages (HTML/PDF) and in supplementary files. Use the persistent article URL (and DOI if assigned) in your repository record.

Which license should my repository display?

Display the license from dc:rights or the article page (e.g., CC BY). Include the license URI where available for machine readability.

What is CJNCP’s ISSN?

The e-ISSN is 2639-9911; include it in your journal-level records and source fields.

Are corrections and withdrawals reflected in metadata?

When needed, we correct or withdraw content and preserve the scholarly record. Re-harvesting recent windows helps propagate status changes.

Is there a list of where CJNCP content is discoverable?

The site highlights multiple discovery services (e.g., search engines and open archives). OAI-PMH enables many of these to harvest reliably.

Quick setup checklist for harvesters

Related CJNCP policies

Open Access Policy • Licensing Policy • Withdrawal Policy • Privacy Statement

Tags: OAI-PMH Metadata Dublin Core Open Access Repository