JISC MediaHub Machine-to-Machine Interfaces

Terms of Use of metadata disseminated by the JISC MediaHub machine-to-machine interfaces

The JISC MediaHub machine-to-machine interfaces are currently provided for testing only. Metadata may be retrieved for the purposes of developing and testing client software. No metadata may be distributed via another online resource base or publicly accessible web site.

How to obtain access

Subject to these terms, access to these interfaces available free of charge. Please contact edina@ed.ac.uk

Note: Metadata records from all collections hosted by JISC MediaHub can be retrieved via these interfaces. JISC MediaHub also contains metadata records from collections hosted on other web sites; the owners of a number of these collections have opted not to make their records available via these interfaces. For more details of the collections, please see http://jiscmediahub.ac.uk/about

SRU Interface

OAI-PMH Interface

Record format

Linking to JISC MediaHub


SRU Interface

This interface is a beta. Please report any problems to edina@ed.ac.uk

Base URL: http://m2m.edina.ac.uk/sru
Port: 80
Database Name: mediahub
Authentication No authentication required
Supported Operations explain, searchRetrieve
Supported Parameters
explain
operation, version
searchRetrieve
operation, version, query, startRecord, maximumRecords
Indexes
cql.serverChoice
The default index; this will be searched if your CQL query specifies no index. This is equivalent to the basic search in the JISC MediaHub user interface, and is recommended unless you have a specific requirement for one of the other indexes.
dc.title
Record title. Searches only title text of records.
dc.subject
Record subject. Searches only subjects of records.
mhub.collection
Collection identifier. Each record returned contains the identifier of the host collection; this value can be used with a query of the mhub.collection index to retrieve all other records in that collection.
dc.identifier
Record identifier. May be used to retrieve a record from its identifier.
dc.date
Temporal coverage. Dates should be specified in YYYYMMDD format; month and day are optional. A range can be specified as YYYYMMDD..YYYYMMDD. For example dc.date=1990..1995 would retrieve all records with a date between 1 January 1990 and 31 December 1995. The temporal coverage of a record may itself be a date range, in which case any overlap between the query date range and the record date range is considered a match: for example a record with a range of 1988..1991 would match the query dc.date=1990..1995.

OAI-PMH Interface

This interface is a beta. Please report any problems to edina@ed.ac.uk

Base URL: http://m2m.edina.ac.uk/oai/mediahub/
Version: 2.0
Metadata formats:
oai_dc
Pure Dublin Core metadata. Providing this is mandatory under OAI-PMH but we strongly advise the use of the oai_mhub format instead.
oai_mhub
The preferred JISC MediaHub record format.
Sets:
hosted
Items hosted within JISC MediaHub.
open
Items freely available on another web site. JISC MediaHub contains a record with a description and (usually) a thumbnail image for each item, but to access full sized still images, video or audio the end user will have to go to the hosting web site. JISC MediaHub provides the link.
restricted
As for open, except the hosting web site may ask the end user to log in to access the item.
For more details see http://jiscmediahub.ac.uk/about

Record format

JISC MediaHub records are returned as XML. This record format is used by both the SRU and OAI-PMH interfaces. This uses Dublin Core elements plus additional MediaHub elements for metadata that cannot be adequately described by Dublin Core. The MediaHub elements use the namespace http://m2m.edina.ac.uk/ns/mediahub, prefix mhub.

All the elements listed below are children of the record container element mhub:record

Element Repeatable Optional Description
dc:identifier no no The record identifier.
mhub:relevancy-score no yes
(never included in OAI-PMH responses)
A relevancy score. This is used for ranking the results. The value depends on how well the metadata for the record match the search term, and may be expected to be comparable within each result set but we do not recommend comparing results from different searches. EDINA may tweak the relevancy ranking algorithm from time to time, so a relevancy score retrieved at one time may differ from that retrieved at a later date, even for the same search.
mhub:collection-access no yes This describes how the item may be accessed. There are three classes:
hosted
The item is hosted within JISC MediaHub.
open
The item is freely available on another web site. JISC MediaHub contains a record with a description and (usually) a thumbnail image, but to access full sized still images, video or audio the end user will have to go to the hosting web site. JISC MediaHub provides the link.
restricted
As for open, except the hosting web site may ask the end user to log in to access the item.
Note that all records within any given collection always share the same mhub:collection-access value. Further details are available at http://jiscmediahub.ac.uk/about
dc:relation [@xsi:type="dcterms:URI"] yes yes A URL for the web site of the original collection to which the item belongs.
dc:type [@xsi:type="dcterms:DCMIType"] no no The DCMI Type of the item.
dcterms:extent [@xsi:type="xsd:duration"] yes yes The duration of a video or audio item expressed as an XSD duration
mhub:duration-in-seconds yes yes The duration in seconds of a video or audio item.
dc:title no no The title of the item
dc:description no no The description of the item. May contain simple HTML tags such as <p> (though always escaped). Deleting any tags should provide perfectly usable unstructured text.
mhub:link-to-mediahub [@xsi:type="dcterms:URI"] no no A persistent URL that may be used to view the item record within JISC MediaHub.
mhub:thumbnail-url [@xsi:type="dcterms:URI"] yes yes The URL of a thumbnail image for the item.
dc:created [@xsi:type="xsd:date"] yes yes The date the item was created. Note this may refer to a particular representation of an original item; for example, for a digitized photograph, this may be the date of digitization rather than the date of the photograph. For most purposes, mhub:temporal-coverage is likely to be preferable to dc:created.
mhub:credit yes yes The person(s) and/or organization(s) who must be credited when an item is displayed.
mhub:rights yes yes A rights statement for the item.
dc:contributor yes yes These describe person(s) or organization(s) who had some role in the creation or provision of the item (either the original; a respresentation of it, such as a digitized version; or a process or service by which the item has been made available).
The contents of these elements are poorly defined because of variability in the original metadata acquired by JISC MediaHub, and inconsistencies in the original cataloguing. As far as is possible, dc:creator is used when the role was creative; dc:publisher when the role was publishing or otherwise providing an item; and dc:contributor when the specific role is not defined at all.
You cannot display this information with any implication that it is a definitive description of the role played by any person or organization.
dc:creator
dc:publisher
dc:subject yes yes A subject term for the item.
dc:coverage [@xsi:type="dcterms:Point"] yes yes The geographic location of the subject of the item, expressed in DCMI Point notation.
mhub:geo-location yes yes The geographic location of the subject of the item. Differs from dc:coverage by using a more usefully named container with child elements for geographic data, rather than the delimited text notation employed by DCMI Point.
This element may contain zero or more of the following elements: north, east, name, elevation, units, zunits and projection. The contents of these elements are defined to be the same as those of components of the same name in DCMI Point.
dc:coverage [@xsi:type="dcterms:Period"] yes yes The temporal coverage (date, date range or a named event/period in time) of the subject of the item, expressed in DCMI Period notation. At the present time only the start, end, and name components are used.
mhub:temporal-coverage yes yes The temporal coverage (date, date range or a named event/period in time) of the item. Differs from dc:coverage by using a more usefully named container with child elements for temporal data, rather than the delimited text notation employed by DCMI Period.
This element may contain zero or more of the following elements: start, end, scheme and name. The contents of these elements are defined to be the same as those of components of the same name in DCMI Period.

Linking to JISC MediaHub

The mhub:link-to-metadata element provides a link to view the record in the web interface. For example:

http://jiscmediahub.ac.uk/record/display/022-01861640

Contact us at: edina@ed.ac.uk
EDINA, Causewayside House
160 Causewayside, Edinburgh
United Kingdom EH9 1PR

EDINA is the Jisc-designated national data centre at the University of Edinburgh.

jisc logo