V · 37

OpenURL Builder

Fill in the fields, pick a metadata format, and press Build to assemble a conformant OpenURL 1.0. Everything runs in your browser.

The builder produces OpenURL 1.0 (Z39.88-2004) links in the form SAP1 resolvers expect: a KEV ContextObject sent with the Inline transport over HTTP GET. Choose the metadata format that fits the item (journal article, book or chapter, dissertation, patent) and the form shows the keys defined for that format. Empty fields are skipped and values are URL-encoded as described in Appendix E of the standard. Need your institution's base URL? See How to find your library's OpenURL resolver.

Builder

Resolver and source

Resolver base URL Source identifier (rfr_id, info:sid/...)

Referent format

Metadata format rft_id: identifier URI(s), optional, separated by spaces Requested service (svc, sch_svc format, optional) Requested service (svc, sch_svc format, optional) Requested service (svc, sch_svc format, optional) Requested service (svc, sch_svc format, optional) Requested service (svc, sch_svc format, optional)

Output

Awaiting input.

Notes

Output follows SAP1: a KEV ContextObject sent with the Inline OpenURL transport over HTTP(S) GET.
Every URL includes url_ver=Z39.88-2004, url_ctx_fmt, ctx_ver=Z39.88-2004 and ctx_enc (UTF-8), plus rft_val_fmt whenever metadata fields are filled in.
Empty fields are omitted from the output; only descriptors with values appear in the URL.
The "Source identifier" field appears in the output as rfr_id=info:sid/<value>.
Enter the first author in the family/given-name fields and each further author on its own line; each line becomes a separate rft.au (or rft.inventor) pair.
Check the result with the validator.