Waseda University

Waseda University Repository (OAI-PMH)

OAI-PMH 2.0 metadata harvesting for the Waseda University Repository. The collection, the administrative contact (repository@list.waseda.jp) and the identity are Waseda's; the host and the WEKO3 software are NII's JAIRO Cloud, so the operator is tenant and no contract is saved under Waseda's name. Identify confirms protocolVersion 2.0, earliestDatestamp 2016-07-05, deletedRecord transient, granularity to the second. Seven metadata formats are served — jpcoar_2.0, jpcoar_1.0, jpcoar, jpcoar_v1, oai_dc, ddi and lom — a configured JPCOAR deployment. The endpoint answers a plain client with 200 and a desktop-browser User-Agent with 406; that is a content-negotiation quirk on NII's nginx, not an outage.

GitHub

Documentation

📖
Documentation
https://www.openarchives.org/OAI/openarchivesprotocol.html

Other Resources

🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/waseda/refs/heads/main/conformance/waseda-conformance.yml
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/waseda/refs/heads/main/examples/waseda-examples.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/repository-oai"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: waseda:repository-oai
name: Waseda University Repository (OAI-PMH)
x-operator: tenant
description: OAI-PMH 2.0 metadata harvesting for the Waseda University Repository. The collection, the
  administrative contact (repository@list.waseda.jp) and the identity are Waseda's; the host and the WEKO3
  software are NII's JAIRO Cloud, so the operator is tenant and no contract is saved under Waseda's name.
  Identify confirms protocolVersion 2.0, earliestDatestamp 2016-07-05, deletedRecord transient, granularity
  to the second. Seven metadata formats are served — jpcoar_2.0, jpcoar_1.0, jpcoar, jpcoar_v1, oai_dc,
  ddi and lom — a configured JPCOAR deployment. The endpoint answers a plain client with 200 and a desktop-browser
  User-Agent with 406; that is a content-negotiation quirk on NII's nginx, not an outage.
humanURL: https://waseda.repo.nii.ac.jp/
baseURL: https://waseda.repo.nii.ac.jp/oai
tags:
- Repository
- OAI-PMH
- Open Access
- Research
- Metadata
- JPCOAR
properties:
- type: Documentation
  url: https://www.openarchives.org/OAI/openarchivesprotocol.html
- type: Conformance
  url: conformance/waseda-conformance.yml
- type: Examples
  url: examples/waseda-examples.yml