The Resource Discovery Network (RDN) has developed tools that allow educational institutions and other organizations to access and display the output from its Web services with their own branding and look-and-feel. This paper describes the need for such tools and the architectural approach to their development. A potential application of this approach to the incorporation of news feeds is also given
Keywords: Resource discovery, subject gateways, content sharing, re-use, news feeds, RSS, XML.
The Resource Discovery Network (RDN)  is a national service funded by JISC to provide access to high quality Internet resources for the UK Higher and Further Education communities. The RDN is a cooperative network of subject gateways, including SOSIG  (social science, business and law), EEVL  (engineering, mathematics and computing), BIOME  (health, medicine and life sciences), HUMBUL  (humanities) and PSIgate  (physical sciences).
Individual gateways provide search and browse access to databases containing descriptions of high quality Internet resources in their subject area as well as other community-specific services. Although each gateway presents its own Web-based user-interface, they all work within a shared architectural framework that supports interoperability between the services, including the ability to cross-search all the RDN gateways. This results in increased functionality for the end-user and the institutions that make use of RDN services.
The subject gateways have proved popular with the end-user community, and with those institutions that understand the resource commitments required in order to maintain links to high quality resources . However, as Web services play a greater role in their marketing, those institutions are beginning to show increasing concern over the branding of their Web services and a reluctance to provide links to external services which may be perceived (albeit incorrectly) to be in competition with the services they provide. Furthermore, for end-users there is some benefit in being able to access remote services, such as the RDN, in such a way that they retain the institutional look-and-feel with which they are accustomed.
RDN-Include  has been developed to enable institutions to provide access to the RDN cross-search and top-level browse interface, whilst maintaining an institutional look-and-feel and URL. RDN-Include allows the institution to embed an RDN search form and top-level browse hierarchy into appropriate points in their Web site. Search results are also returned with an institutional look-and-feel.
To make use of RDN-Include the institution must install the RDN-Include CGI script on one of their Web servers. All end-user interaction is handled by this script, thus retaining an institutional URL. If the script is not passed any search parameters, it reads a template file held locally. The template file is essentially a normal HTML or XHTML Web page, formatted with a local look-and-feel. RDN content (the RDN search box and browse hierarchy) is added to this template dynamically at run time by including in it one or more XML 'rdni:tag' elements of the form:<rdni:tag val="RDN*"/>
where * represents a unique service identifier. These tags are defined in a tag definition file at the RDN. Based on these tags, the RDN-Include CGI script collects appropriate content from the RDN Web server using HTTP. In this way the RDN can update and/or create tags as new services are developed. Any new tags immediately become available to RDN-Include hosts, so the RDN can add new services without the need to update the RDN-Include script installed on each institutional machine.
Figure 1: RDN-Include
If search parameters are passed to the RDN-Include script, it passes these on to a CGI search script running on the RDN Web server. This script cross-searches all the available RDN gateways, using the search protocols defined in the RDN Interoperability and Standards Framework , and returns results as 'plain' HTML that can be embedded within the institutional template.
RDN-Include has been implemented as both a Perl CGI script and using ASP.
This approach is:
One problem with the approach provided by RDN-Include is the need for the support of the Web server administrator, since it requires the installation of a CGI Perl or ASP script. System administrators have legitimate concerns over the security of third-party scripts. In addition there may be local political barriers to the deployment of such scripts.
Figure 2: RDNi-Lite
Our work on RDN-Include has convinced us of the benefits of offering RDN content in a form that allows others to embedded it within local services. However, even the minimal technical requirements of RDN-Include present a significant hurdle for some service providers. It is hoped that the development of lightweight solutions that can be used directly by HTML authors, such as RDNi-Lite, will overcome some of these problems and encourage the use of shared content.
RDN-Include: Re-branding Remote Resources, Cliff, A., Powell, A. and Kelly, B. WWW 10 Hong Kong, 1-5 May 2010. <http://www.ukoln.ac.uk/web-focus/papers/www10/>