recovery strategy based on knowledge that vast number of requests were for current year -- since the full system recovery takes days (or weeks?) they now deposit objects from current year so they can be restored first and quickly. Similarly with Solr optimisation -- having done a lot of generic optimisation they were still finding performance (query response times) far too slow on very larges sets of documents. By analysing how the system was used they were able to perform some very specific optimisations (I think this was around increasing the filtercache settings) to achieve a significant reduction in query response times. Inter-repository Linking of Research Objects with Webtracks This session being presented by Shirley Ying Crompton. Shirley describing how the research process leads to research data and outputs being stored in different places with no links between them. So decided to use RDF/linked data to added structured citation links between research objects (and people -- e.g. creators). However, different objects created in different systems -- so how to make sure objects are linked as they are created? Looked at existing protocols for enabling links to be created: Trackbacks -- use for blogs/comments Semantic pingback -- an RPC protocol to form semantic links between objects Salmons -- RSS protocol ... Decided to take 'webtracks' approch -- this is an inter-repository communication protocol. The Webtracks InteRCom protocol -- allows formation of links between objects in two different repositories. InteRCom is two stage protocol -- first stage is 'harvest' to get links,