Create a new subdomain

Creating a new theme/subdomain
If your organisation or project has data which you feel should be granted a subdomain, please join the mailing list and make your case, within the guidelines below. If the consensus is that it seems a good idea, then you can set up a website on your web-servers using a *** domain.

One organisation can't and shouldn't run all the services. We believe in creating a community or ecosystem of services, interlinking them when that adds value, but not putting all the eggs in one basket. We're looking for organisations interested in being part of this.


  • Your idea should be reasonably sustainable
    • Where possible, keep it simple and easy to keep running
  • The service should either:
    • provide data of relevance to UK academia
    • provide a data-driven service for UK academia
  • The sub-domain should be named after what it actually does
    • Very specific names like ‘’ will only be granted to organisations with a good case to run them
    • Subdomains will never be granted based on regions, e.g.,,
    • Subdomains will never be granted based on project names because projects end, services don't
    • Subdomains will never be granted on organisation names, e.g. or In these cases the data should either be hosted under the organisations own domain, or a more descriptive name should be chosen
    • The goal of these restrictions is to allow a domain to be smoothly passed between managing organisations, and therefore increase sustainability
  • You must try to hand over control of the site to another party if it has value to the community and you are no longer able to support it
  • We encourage the data to be open, and under one of our recommended licenses but this is not a requirement. Sometimes there may be legal reasons the data can only be provided to a restricted set of users
    • But you must provide a clear license, so people know what they can and can't do
  • You must describe where the data comes from, how it is updated, and how often
  • You must provide a route for people to use to submit corrections to the data
  • No payment should be required for the use of any data or service hosted on
  • These are guidelines not strict rules. We will firm up policy over time, based on experience
  • We really like RDF, Linked data and Cool URLs. We *recommend* these technologies for, but certainly don't insist upon them
  • RDF isn't for everyone. It can be a barrier to non-experts using the data. For this reason, we ask that wherever possible, you also make your data available in really easy formats such as CSV or TSV (tab separated values). This lowers the costs of getting started with data, and allows people with more general skills to get immediate value out of it
  • Where possible, providing basic search, browse and visualisation tools makes it easier for people to get value from your data
  • If you provide an API to your data, please always also provide a ‘dump’ location where people can download everything in one go without having to 'crawl' the site
  • We encourage the use of RESTful principles in site and URL design
  • You should provide a ‘corrections’ page or link for every dataset so that people have a route to get it corrected