EDINA <strong>Annual</strong> <strong>Review</strong> 2008/2009associate member <strong>of</strong> <strong>the</strong> OGC for several years, and is actively engaged in implementing OGC interoperabilitystandards as well as contributing to <strong>the</strong> development <strong>of</strong> new standards or pr<strong>of</strong>iles <strong>of</strong> existing standards. (Forexample, staff members within <strong>the</strong> geo-services team have been working with <strong>the</strong> leader <strong>of</strong> <strong>the</strong> OGC SecurityWorking Group on an architecture for securing OGC Web Services using Shibboleth and GeoXACML.) One <strong>of</strong><strong>the</strong> interesting challenges has been <strong>the</strong> integration <strong>of</strong> <strong>the</strong>se standards with <strong>the</strong> o<strong>the</strong>rs promoted and used within<strong>the</strong> JISC IE and e-Infrastructure. However, by deploying services using <strong>the</strong>se standards, EDINA will be in aposition for <strong>the</strong>se services to become components <strong>of</strong> <strong>the</strong> evolving UK SDI.The Geoservices team at EDINA has undertaken project work to effect Shibboleth-based access management ina web-services environment. This activity was undertaken in cooperation with colleagues from Germany andadvice from Chad La Joie <strong>of</strong> SWITCH.EDINA began looking at newer technologies including ontologies, knowledge-based infrastructures, and <strong>the</strong> use<strong>of</strong> third party APIs provided by <strong>the</strong> likes <strong>of</strong> Google and Geonames. Use <strong>of</strong> third party APIs allowed EDINA toexploit services whose content is global compared to <strong>the</strong> UK focus <strong>of</strong> most <strong>of</strong> <strong>the</strong> collections hosted byEDINA. As an example, <strong>the</strong> geoparser, part <strong>of</strong> GeoCrossWalk, was upgraded to georeference documents withplace references outside <strong>of</strong> <strong>the</strong> UK, leveraging <strong>the</strong> Geonames API for geo-coding.The Go-Geo! portal is <strong>the</strong> place to discover geospatial information and services for education and research. Go-Geo! enables users to find data, geospatial services and resources, learn about geospatial metadata and accesstools to create and publish standards-compliant geospatial metadata. Launched as a JISC service in November2008, average monthly page requests doubled during <strong>the</strong> first six months <strong>of</strong> 2009 to over 21,000. With <strong>the</strong>appointment <strong>of</strong> a dedicated portal content coordinator, around 100 monthly additions were made to news,events, conferences, books and o<strong>the</strong>r resources. One particular highlight is that Dr. David Wheatley, arecognised pioneer <strong>of</strong> GIS archaeological applications, has formally incorporated GeoDoc into studentcoursework in <strong>the</strong> Archaeology Department at <strong>the</strong> University <strong>of</strong> Southampton. This has resulted in a privateinstitutional metadata node holding over 250 metadata records. Dr Wheatley said, “The tools provided a usefulway to encourage my students to document <strong>the</strong>ir datasets and introduce ideas about interoperability and repurposingspatial data”.Go-Geo! is a critical component in <strong>the</strong> UK academic SDI and, as a consequence <strong>of</strong> being interoperable, it canalso be a part <strong>of</strong> <strong>the</strong> developing UK SDI. However, to be compliant <strong>the</strong> metadata needs to be presented to <strong>the</strong>UK SDI in <strong>the</strong> correct format. Thus work began on aligning AGMAP with <strong>the</strong> new government GEMINI2 andEuropean INSPIRE metadata pr<strong>of</strong>iles. The Go-Geo! service manager was invited to attend a UK LocationProgramme meeting, part <strong>of</strong> <strong>the</strong> UK SDI development activity, to present on lessons learned from running anational geospatial portal.GeoCrossWalk, now re-branded Unlock, <strong>the</strong> middleware gazetteer and georeferencing infrastructure service, waslaunched as a JISC service in November 2008 and is available for use in <strong>the</strong> Digimap OS Collection pages. Theprincipal purpose <strong>of</strong> GeoCrossWalk is to provide a shared terminology service within <strong>the</strong> JISC InformationEnvironment (IE) that can underpin geographic searching and georeferencing. GeoCrossWalk is designed tomake geographic searching transparent by ‘crosswalking’ <strong>the</strong>se different geographies and is analogous to a sharedterminology service.Ano<strong>the</strong>r middleware service, <strong>the</strong> OpenURL Router was developed to address <strong>the</strong> issue <strong>of</strong> allowing linkage frombibliographic services to OpenURL resolvers. The OpenURL Router provides a central registry detailingOpenURL resolvers, <strong>the</strong> institutions to which <strong>the</strong>y belonged, and certain details (UK Federation identifiers, IPaddresses and domain names) that help in identifying members <strong>of</strong> that institution. This allows referringbibliographic services to address OpenURL links to <strong>the</strong> correct resolver for each end user, without any priorknowledge <strong>of</strong> <strong>the</strong> user or <strong>the</strong>ir institution. The OpenURL Router showed continued strong growth in usage over2008/2009, with <strong>the</strong> number <strong>of</strong> institutions registered rising from 83 to 94.20
EDINA <strong>Annual</strong> <strong>Review</strong> 2008/2009The Shibboleth Development and Support Services (SDSS) Expert group at EDINA released Discovery serviceversion 1.1, which includes dynamic searching and embedded WAYF capabilities. The group is working on anevolving technical design to allow practical inter-federation working via metadata exchange.The SDSS Federation Support team updates and manages <strong>the</strong> metadata that underpins <strong>the</strong> Federation. Themetadata is signed daily to ensure its integrity before being shipped to <strong>the</strong> Federation operator for distribution toFederation members.Sustain and develop a well-founded UK national academic datacentreProvide effective governance and management <strong>of</strong> resourcesGovernanceEDINA operates as a HEFCE-related body under <strong>the</strong> terms <strong>of</strong> a Funding Agreement signed between HEFCEand <strong>the</strong> University <strong>of</strong> Edinburgh. A Management Board that <strong>of</strong>fers specialist advice and guidance has beenestablished under <strong>the</strong> terms <strong>of</strong> <strong>the</strong> Agreement, and it met three times during 2008-2009. The Director <strong>of</strong>EDINA reports to <strong>the</strong> Board. The Chair is chosen in agreement between <strong>the</strong> University and JISC, and in 2008-2009 Pr<strong>of</strong>essor Charles Oppenheim agreed to take <strong>the</strong> Chair. Membership includes representatives from <strong>the</strong>JISC Secretariat, <strong>the</strong> user community, <strong>the</strong> Director <strong>of</strong> EDINA, and <strong>the</strong> University <strong>of</strong> Edinburgh.The Director <strong>of</strong> EDINA sits on <strong>the</strong> Information Services (IS) Executive as director <strong>of</strong> a division <strong>of</strong> IS and, as anemployee, <strong>the</strong> Director reports to <strong>the</strong> Vice Principal and Chief Information Officer <strong>of</strong> <strong>the</strong> University; <strong>the</strong> lattersits on <strong>the</strong> EDINA Management Board.The EDINA Management Team met fortnightly and is responsible for leadership <strong>of</strong> activity, finance andresource planning in <strong>the</strong> data centre. The Business Development Group guides <strong>the</strong> development <strong>of</strong> new projectand service activity within EDINA and met fortnightly.EstateThe move to commercial premises in Edinburgh improved <strong>the</strong> working environment for EDINA staff andprovided additional resources, such as a number <strong>of</strong> meeting rooms that any member <strong>of</strong> staff can reserve.Additional accommodation was secured on ano<strong>the</strong>r floor in <strong>the</strong> same building in 2008-2009 and some staffmembers moved downstairs in early 2009. EDINA’s <strong>of</strong>fice at St Helens College in Newton-le-Willows,Merseyside, closed due to <strong>the</strong> planned closure <strong>of</strong> <strong>the</strong> campus by <strong>the</strong> College. The 4 members <strong>of</strong> staff moved tocommercial premises in Birchwood, Warrington, Cheshire in July 2009.It is anticipated that <strong>the</strong> additional accommodation in Edinburgh and Warrington will address for some time <strong>the</strong>constraints previously faced by <strong>the</strong> organisation due to lack <strong>of</strong> accommodation for staff.FinancePriority was given in 2008-2009 to improving methods <strong>of</strong> projecting income, activity and hence staffing andaccommodation requirements. EDINA started work on improving its management accounting systems to makebetter-informed business decisions. In common with many o<strong>the</strong>r organisations that receive much <strong>of</strong> <strong>the</strong>irfunding from grant money, EDINA faces challenges in being able to react quickly to opportunities when staffmembers are already <strong>full</strong>y committed in <strong>the</strong>ir current work. EDINA’s Strategy and <strong>the</strong> rolling businessdevelopment plans in each <strong>of</strong> EDINA’s business areas address <strong>the</strong> whole <strong>of</strong> <strong>the</strong> activity undertaken by <strong>the</strong> datacentre, and not just its JISC-funded activity. Service Implementation Plans for JISC-funded activity are guided by<strong>the</strong>se documents. The annual Operational Plan for JISC is based on <strong>the</strong> Service Implementation Plans.Managing RiskEDINA provides a Risk Register each year to JISC, as part <strong>of</strong> <strong>the</strong> requirements <strong>of</strong> <strong>the</strong> Funding Agreement andSLD. The Risk Register for 2008-2009 was submitted as required in September 2008. In December 2008,EDINA held two scenario-planning workshops for senior staff. The first addressed financial scenario planning,21