Harvesting & search-engine indexing¶
A big reason to deposit in the repository is reach: published items are exposed to search engines and academic indexes automatically, so the world can find Amoud's research. This page explains how that works — useful for librarians, indexers, and administrators.
Search engines & academic indexes¶
Every public item is laid out so that Google, Google Scholar, BASE, and CORE can crawl and index it. You don't need to do anything — once a reviewer approves an item and it goes public, it becomes eligible for indexing (which can take indexers a little while to pick up).
Help indexing along
Good, complete metadata — an accurate title, authors, date, abstract, and type — is what indexers read. The better the description, the better the item ranks and the more likely it is to be found.
OAI-PMH — for systems that harvest records¶
The repository publishes its metadata over OAI-PMH, the standard protocol other systems use to harvest records in bulk. The endpoint is:
A few useful requests:
| To… | Use |
|---|---|
| See repository info | ?verb=Identify |
| List the available sets | ?verb=ListSets |
| List records (Dublin Core) | ?verb=ListRecords&metadataPrefix=oai_dc |
Records are offered in several metadata formats, including oai_dc (simple Dublin
Core), qdc (qualified DC), mods, mets, rioxx, and the thesis-oriented
etdms and uketd_dc — so harvesters that specialise in electronic theses can take
them in the right shape. Records are also grouped into sets by community/collection, so
a harvester can take just one part of the repository.
Identifiers travel with the record¶
Because every published item carries a DOI and an ARK, harvested records point back to a permanent address — not a link that breaks when the site changes. See DOIs & ARKs explained.