To share data from a single project, we would generally recommend publishing it in your institutional repository and/or on the project website. As always, include a license which defines how people may reuse it.
Datasets relevant at the national level
If your data is likely to be of use to many users in the .ac.uk community, to link to or use as the basis of other datasets, then you may want to register a Data.ac.uk subdomain to give it a permanent address and URIs. Please visit the Create a new theme/subdomain page which explains the process to establish a new sub-domain.
This is data about your own organisation. Some Universities share data about their organisation; such as staff, buildings, courses, equipment, services, vacancies, publications, news, events, and so forth.
We recommend you publish your data in ways similar to those of existing services; that will let you reuse some of the tools and techniques.
You should then create a ‘discoverable’ profile document which lets other people find out what you have published and how you are willing to allow people to reuse the data. See below for details.
Organisational Profile Document
To tell us where to find your open data (e.g. equipment, facilities or capabilities), and associated licences etc. You will need to create an organisation profile document. This is a simple rdf file which describes your organisation and open access documents.
The examples used in this document 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 learning-provider.data.ac.uk. If you use your own please include a owl:sameAs linking it to the learning-provider.data.ac.uk URI for your organisation. In our examples we use http://id.example.ac.uk/ as the URL for your organisation.
# defining prefixes makes our document easier to read an maintain
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix oo: <http://purl.org/openorg/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix org: <http://www.w3.org/ns/org#> .
# Describe this document and state a license
a oo:OrganizationProfileDocument ;
dcterms:license <http://creativecommons.org/publicdomain/zero/1.0/> ;
foaf:primaryTopic <http://id.example.ac.uk> .
# 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 <http://www.example.ac.uk/example-logo.png> ;
foaf:homepage <http://www.example.ac.uk/> ;
owl:sameAs <http://id.learning-provider.data.ac.uk/ukprn/12345678> ;
owl:sameAs <http://dbpedia.org/resource/University_of_Example> .
# Describe the source of equipment data, what standard it conforms to, and the license.
oo:organization <http://id.example.ac.uk/> ;
dcterms:subject <http://purl.org/openorg/theme/facilities> ;
dcterms:conformsTo <http://equipment.data.ac.uk/uniquip.html> ;
dcterms:license <http://creativecommons.org/publicdomain/zero/1.0/> .