Equipment.Data Logo

Frequently Asked Questions


  1. What is
  2. How does it work?
  3. Can we include equipment or facility data from University X?
  4. Can we include information from some source other than a UK university?
  5. What is the minimum requirement for inclusion?
  6. Which types of information will you accept?
  7. How do we include our data on
  8. What are the accepted formats?
  9. What license should I use?
  10. What is an Organisation Profile Document (OPD)?
  11. How does autodiscovery work?

1. What is is a website that aims to be a one-stop-shop for the UK academic community to share the details of high value research equipment with each other and potential industrial collaborators, to help facilitate equipment sharing.

2. How does it work?

Every night the site fetches data from the participating universities, colleges and research institutes and puts it into a searchable database. This can be as simple as uploading a spreadsheet in the UNIQUIP format to your institution's website or a file sharing service like Google Drive, and giving us a link to it. However, the site is also smart enough to find datasets automatically using an Organisation Profile Document (OPD).

3. Can we include equipment or facility data from University X?

Yes. This site aggregates information from the websites of UK academic organisations. This way you can verify the source of the information yourself, or even build your own aggregator.

4. Can we include information from some source other than a UK university?

Not generally, but in some cases labs or other may be included.

In future it may include information from other organisations or from organisations providing services to UK academia, but currently we limit the scope to keep the service manageable.

5. What is the minimum requirement for inclusion?

The simplest allowed contribution is for you to publish a spreadsheet on your website containing a single column, with "Description" as the heading and each row containing the description of an item of equipment. You then supply us with that URL, your organisation details, location and a default contact for all items of equipment.

Obviously we hope you'll provide more than that, but we have tried to make inclusion as painless as we can

6. Which types of information will you accept?

Information on your equipment, facilities and services. For our purposes:

Facility - This is a very overloaded term so for our purposes this is something your organisation calls a facility. More semantic subclasses are available in RDF, for example to indicate it’s an RCUK costed facility.

Equipment - A physical thing which has a location. We make no rules about how much detail you can go into. A single record could describe a grouping of equipment as a single item, e.g. 3 Vacuum Chambers.

7. How do we include our data on

Step 1. Place your data on the web in one of the accepted formats (see below). The most simple can be created in a spreadsheet. You could use a google-docs spreadsheet for this.

Step 2. Create (or update) an Organisation Profile Document which links to the equipment data and tells us what license you provide it under. This is just a short machine-readable text file which tells us things like what logo to use, and what format your data is in.

Step 3. (optional but recommended) Make your organisation profile document auto-discoverable from your university homepage. If you can’t do this, just drop us a line and we’ll add your profile by hand.

8. What are the accepted formats?

We expect to expand accepted formats in due course.

1. OpenOrg RDF document

The Open Org project describes a basic pattern for publishing facilities and equipment data.

In the future it’s certain that other standards emerge, but it’s possible to use multiple patterns to describe the same entities. A single RDF document could conform to multiple patterns. They are (generally) not mutually exclusive.

See for more information.

Example of how to describe an OpenOrg style document listed in an organisation profile document.

The RDF can be encoded as either RDF+XML or Turtle.

<> oo:organization <> ; oo:corrections <> ; dcterms:subject <> ; dcterms:subject <> ; dcterms:conformsTo <> ; dcterms:license <> .

2. Uniquip spreadsheet

This simple spreadsheet format was designed to be very easy to produce and have a minimal amount of required information.

It was created as a result of an exercise involving representatives from 30 UK Universities and aimed to produce the most basic format that would facilitate equipment sharing in the UK. In brief, each item of equipment (or facility) must have a description, a location and some kind of contact information. Everything else is optional.

This spreadsheet can be formatted in Excel (.xls or .xlsx) or in CSV or Tab-Separated Values.

See to get the specification of what should go in each column.

Assuming the URL of your spreadsheet is "" and your license is CC0 (allow unlimited use)

You would describe it in the organisation profile document as follows:

<> oo:organization <> ; oo:corrections <> ; dcterms:subject <> ; dcterms:subject <> ; dcterms:conformsTo <> ; dcterms:license <> .

3. KitCatalogue JSON document

KitCatalogue is being developed by Loughborough University, funded by the JISC. It’s free, open source software which collects information on an organisations equipment.

It allows the option to publish some or all of your records as open data. Currently we use the JSON to import this information but in future KitCatalogue may include an RDF mode.

<> oo:organization <> ; oo:corrections <> ; dcterms:subject <> ; dcterms:subject <> ; dcterms:conformsTo <> ; dcterms:license <> .

Future formats

Undecided at present. XML and RDF encodings of CERIF are a possibility.

9. What license should I use?

Currently the licenses we accept are described on the website. However, we will also harvest appropriate data without a specific license, if it is available on the web in machine readable form, unless asked not to by the data owner.

10. What is an Organisation Profile Document (OPD)?

To tell us where to find your equipment/facilities data, and the license etc. you’ll need to create an organisation profile document. This is a simple RDF file which describes your organisation and open access documents.

The examples we use in this page are all “Turtle” format but RDF+XML is OK too.

You will require a ‘URI’ to refer to your organisation. You can either use your own, or use one from If you use your own, please include a owl: same as linking it to the URI for your organisation. In our examples we use <> as the URI for your organisation.

sidebar: American spelling of ‘organization’? Yes, we use the American spelling in the data structures. Sorry if that annoys people, but we decided to keep the ‘z’ in all the semantics rather than have a muddle of UK and US spelling which is certain to create errors.

# defining prefixes makes our document easier to read an maintain @prefix skos: <> . @prefix owl: <> . @prefix dcterms: <> . @prefix oo: <> . @prefix foaf: <> . @prefix vcard: <> . @prefix org: <> . # Describe this document and state a license <> a oo:OrganizationProfileDocument ; dcterms:license <> ; foaf:primaryTopic <> . # Some information about the organisation, most of this is optional but the # prefLabel, logo and sameAs to the learning-provider URI is strongly encouraged. <> a org:FormalOrganization ; skos:prefLabel "The University of Example" ; skos:hiddenLabel "Example" ; skos:hiddenLabel "Example U" ; vcard:sortLabel "Example, University of" ; vcard:tel <tel:+441234567890> ; foaf:logo <> ; foaf:homepage <> ; owl:sameAs <> ; owl:sameAs <> . # Describe the source of equipment data, what standard it conforms to, and the license. # delete the dcterms:subject as applicable, but you need to have one of # facilities/equipment to trigger the automatic aggregation of the data. <> oo:organization <> ; oo:corrections <> ; dcterms:subject <> ; dcterms:subject <> ; dcterms:conformsTo <> ; dcterms:license <> .

This isn’t everything that can go in a profile document, but it should be a summary of your organisation, not a complete data catalogue.

We strongly recommend using a CC0 license (public domain dedication) for the organisational document. This makes it easy for 3rd parties to use it and combine many such documents without problems. It is very possible you won’t be willing to CC0 license your equipment data, but the profile document should not contain anything you don’t want widely and freely reused, so CC0 is appropriate for it.

11. How does autodiscovery work?

We offer three ways to get to discover your profile document.


This method uses a specific URL from your university homepage to link to the profile document; if your homepage is then should serve (or redirect to) your profile document.

<link> header

This method of auto discovery uses a header on your organisation homepage header:

<link rel=”openorg” href=”"” />
Which links to the profile document.

Can’t do either of these methods?

Don’t panic!

We understand that the team providing equipment and facilities data for your organisation won’t always be working hand-in-glove with the team that run the homepage and main website. If the above methods are impractical for you, get in touch using the contact form and we will manually register the URL of your profile document.