The links under Interoperability in the footer are machine interfaces, not ordinary web pages. Other systems read them to discover and copy SLADS records. This page explains each one; the readable views show the same data in a form people can browse.
For aggregators & libraries
OAI-PMH 2.0 endpoint
The Open Archives Initiative Protocol for Metadata Harvesting lets services such as BASE, CORE, OpenAIRE and WorldCat automatically collect the description (title, authors, abstract, subjects, rights, link) of every published SLADS record in the international Dublin Core format. This is how SLADS research appears in global academic search engines. Only approved, published records are exposed.
Base URL — give this to an aggregator
https://repository.slads.sc.tz/api/oaiExample requests
For search engines
Sitemap
A list of every public page — 213 URLs, including each research record and author profile — so Google, Bing and Google Scholar can find and index all of them, not only the pages they happen to reach.
https://repository.slads.sc.tz/sitemap.xmlFor crawlers
robots.txt
Instructions every search-engine crawler reads first: 13 public areas to index (including the full-text files Google Scholar needs) and 11 private areas to stay out of — the admin, staff and student portals and account pages. It also points crawlers to the sitemap.
Built into every record page
Metadata that travels with each paper
Google Scholar tags
citation_title, citation_author, citation_pdf_url and more — the tags Google Scholar requires to list and link each paper.
Dublin Core meta
DC.title, DC.creator, DC.date… in each page head, read by library discovery systems.
schema.org JSON-LD
ScholarlyArticle / Thesis structured data for rich results in general search engines.
Citation exports
One-click APA, BibTeX and RIS for Zotero, Mendeley and EndNote, with a stable accession number.
Standards:OAI-PMH 2.0Dublin Coresitemaps.org 0.9Robots Exclusion Protocol (RFC 9309)Highwire / Google Scholarschema.org