This report summarises the results of work that has been undertaken under workpackage 8 of the SPP and constitutes the project deliverable "Interaction Report". Our initial survey into the availability of shared services concluded that the IESR is the key shared service of value to SPP currently. We have conducted some early proof-of-concept technical trials within SPP - targeting the IESR as a shared service that provides collection level description (CLD) information. This is of value in connection with many of the targets that SPP supports in its cross-search landscapes. Being of a pilot nature, the version of the SPP software that includes this early IESR support is a subsequent version to that of the formal SPP software release at the close of the project. It is however available from SPP's download area. In the introduction to this report we describe the positioning of SPP in respect to IESR in the JISC Integrated Information Environment (IIE), we go on to explain SPP proof-of-concept work in relation to IESR, and finally we indicate the potential for future work in this area. On this latter point we particuarly refer to the potential for using IESR's service (as opposed to collection) level description metadata in order to facilitate automation of SPP's network connections to targets (remote data providers).
The JISC IE Service Registry represents a shared service in the IIE. It offers both Web and Z39.50 interfaces and it is the latter that is of use to the SPP, potentially allowing IESR Collection Level Description (CLD) content to be delivered "seamlessly" through the portal to the end-user and also Service Level Description (SLD) to be used "behind-the-scenes" to automate SPP cross-searching without any prior-configuration required by a technical administrator. In other words, because Collection Level Descriptions are essentially human-readable descriptions of data provider targets that may be included in an end-user's cross-search landscape, the IESR realises the opportunity to hold such descriptions in a central place on the network. In this way multiple SPP administrators (potentially at Hubs - such as SOSIG, EEVL, HUMBUL - across the UK) are not required to each maintain CLD's for SPP targets, instead they are saved the effort and the job is left to the maintainers of the IESR. This applies similarly to the recording and maintenance of SLD for targets. In at least these two ways therefore SPP is potentially a primary client of IESR.
The design of JISC Information Environment Architecture has been encapsulated as this diagram:
And we see from this diagram the positioning of the IESR in relation to Subject Portals.
The SPP can access the IESR network shared service via the Z39.50 protocol currently. SPP already has Z39.50 client support built-in to its system. SPP also has a CLD store and display feature for each of its search landscape targets (data collections), plus a mechanism for cross-searching several Z39.50 (or harvested OAI / web crawled targets) simultaneously. Therefore, in early trials we have considered building the necessary extra support for IESR in two ways:
Without using IESR for collection level descriptions, SPP uses a simple XML file, stored locally to the portal, with manually filled out collection level descriptions for targets. With reference to the screenshot of the SOSIG portal below, if the user should click on the "description" link next to, say, the COPAC listed collection ...
... then the user would see this popup html page containing a basic description of the COPAC data collection:
The local SPP file from which this COPAC description originated has data stored in XML format. Here is a sample SPP XML file segment which includes the COPAC collection description from which the text in the above pop-up window was derived.
<DescriptionsDirectory>.... <Collection collection_id="BOPCRIS" collection_description="BOPCRIS is a searchable database of references to key British Official Publications 1833-1983." url="http://www.bopcris.ac.uk/index.html"/> <Collection collection_id="COPAC" collection_description="COPAC is a union catalogue, giving access to the merged online catalogues of members of the Consortium of University Research Libraries (CURL). There are some 30 million records on Copac representing the merged holdings of 26 CURL member institutions, including the British Library & National Library of Scotland, plus special collections from a small number of non-CURL libraries." url="http://copac.ac.uk/about.html"/> <Collection collection_id="ERIC" collection_description="The ERIC (Educational Resources Information Center) database is sponsored by the U.S. Department of Education to provide extensive access to educational-related literature. The ERIC database corresponds to two printed journals: Resources in Education (RIE) and Current Index to Journals in Education (CIJE). Both journals provide access to some 14,000 documents and over 20,000 journal articles per year." url="http://oh1.csa.com/csa/factsheets/eric.shtml"/> ....<DescriptionsDirectory>
How do the collection technical descriptions get handled technically? Within the SPP portal software, at "start up" time, the software configures itself in numerous ways. Included in this process, the collection level descriptions are configured and stored in java objects during a session. When a user clicks to retrieve a collection description, the java object that contains the CLD hands its data over to the portal (Velocity) layer that handles presentation to the user.
For SPP collections not known to the IESR, the above mechanism is suffficient for storing and displaying CLD (we note of course that the XML file used to hold CLD's will preferably be extended for further granularity and adherence to the recommended CLD schema - such as the IESR example at http://iesr.ac.uk/metadata/templates/coll-example.xml).
For SPP collections known to the IESR, we have trialled a new approach - automatically extracting CLD's from the IESR in readiness for their on-click display to the end-user.
This new approach entails making several Z39.50 connections to the IESR - on a per-collection basis. Via the provider's (data collection's) collection id we are able to query the IESR in a Z39.50 session and retrieve a CLD record from it if it exists. Here is a sample IESR record retrieved in such a Z39.50 session:
[iesr]Record type: XML <?xml version="1.0"?> <iesrDescription xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcmitype="http://purl.org/dc/dcmitype/" xmlns:rslpcd="http://purl.org/rslp/terms#" xmlns:iesr="http://iesr.ac.uk/terms/#" xmlns="http://iesr.ac.uk/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mimas.ac.uk/iesr/ http://iesr.ac.uk/profile/ies r.xsd" > <dcmitype:Collection> <dc:title xml:lang="en-gb">COPAC Academic Library Catalogue</dc:title> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445734- 12758</dc:identifier> <dcterms:abstract xml:lang="en-gb">COPAC is a union catalogue, providing access to the merged online catalogues of major university research libraries in the UK and Ireland, plus the British Library and National Library of Scotland. It offe rs a single point of access to details of materials held in many different locat ions, bringing together the strength of individual collections ranging across th e Arts, Humanities, Social Sciences, Sciences and Medicine. COPAC has c. 27 mill ion records for a wide range of materials such as books, journal titles, researc h reports, music, videos and electronic documents. Documents date from c.1100AD to current and c.300 languages are included. Increasing numbers of records incor porate links to the full-text of the document. Local holdings information is pro vided, for example, the branch library holding the document, the shelf location, and in some cases, whether the document is currently on loan.</dcterms:abstract > <dc:type xsi:type="dcterms:DCMIType">Collection</dc:type> <dc:type xsi:type="rslpcd:CLDT">Catalogue.Library.Text</dc:type> <dc:language xsi:type="dcterms:RFC3066">de</dc:language> <dc:language xsi:type="dcterms:RFC3066">en</dc:language> <dc:language xsi:type="dcterms:RFC3066">es</dc:language> <dc:language xsi:type="dcterms:RFC3066">fr</dc:language> <dc:rights xml:lang="en-gb">Materials contained on this website are subject to c opyright and other proprietary rights. COPAC is a registered trademark of the Vi ctoria University of Manchester.</dc:rights> <iesr:useRights xml:lang="en-gb">Materials contained on this website are subject to copyright and other proprietary rights. COPAC is a registered trademark of t he Victoria University of Manchester.</iesr:useRights> <dcterms:accessRights>Freely available.</dcterms:accessRights> <iesr:hasService xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/108444535 6-9939</iesr:hasService> <iesr:hasService xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/108444556 9-11632</iesr:hasService> <iesr:hasService xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/108444542 2-10577</iesr:hasService> <iesr:hasService xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/108444541 3-10492</iesr:hasService> <iesr:logo xsi:type="dcterms:URI">http://www.mimas.ac.uk/publicity/images/copac. gif</iesr:logo> <dc:subject xsi:type="dcterms:DDC">017</dc:subject> <dc:subject xsi:type="dcterms:DDC">027</dc:subject> <dc:subject xsi:type="dcterms:DDC">100</dc:subject> <dc:subject xsi:type="dcterms:DDC">200</dc:subject> <dc:subject xsi:type="dcterms:DDC">300</dc:subject> <dc:subject xsi:type="dcterms:DDC">400</dc:subject> <dc:subject xsi:type="dcterms:DDC">500</dc:subject> <dc:subject xsi:type="dcterms:DDC">600</dc:subject> <dc:subject xsi:type="dcterms:DDC">700</dc:subject> <dc:subject xsi:type="dcterms:DDC">800</dc:subject> <dc:subject xsi:type="dcterms:DDC">900</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Academic libraries</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Arts</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Books</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Humanities</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Library catalogs</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Library materials</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Nonbook materials</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Online library catalogs</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Periodicals</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Research libraries</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Science</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Social sciences</dc:subject> <dc:subject xsi:type="dcterms:LCSH">Technology</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Academic libraries</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Arts</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Books</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Catalogues</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Documents</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Library collections</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Periodicals</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Recordings</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Science</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Secondary documents</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Social sciences</dc:subject> <dc:subject xsi:type="iesr:UNESCO">Visual materials</dc:subject> <dcterms:temporal xsi:type="dcterms:W3CDTF">1100/</dcterms:temporal> <iesr:usesControlledList xsi:type="iesr:CtrldVocabsList">LCSH</iesr:usesControll edList> <iesr:usesControlledList xsi:type="iesr:CtrldVocabsList">MESH</iesr:usesControll edList> <iesr:usesControlledList xsi:type="iesr:CtrldVocabsList">COMPASS</iesr:usesContr olledList> <iesr:usesControlledList xsi:type="iesr:CtrldVocabsList">PRECIS</iesr:usesContro lledList> <rslpcd:owner xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445246-9 103</rslpcd:owner> <dcterms:isReferencedBy xsi:type="dcterms:URI">http://copac.ac.uk/copac/about.ht ml</dcterms:isReferencedBy> <iesr:admeta> <dc:creator>Leigh Morris</dc:creator> <dc:creator>COPAC service</dc:creator> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-11-10</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </dcmitype:Collection> <dcmitype:Service> <dc:title xml:lang="en-gb">Linking to COPAC</dc:title> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445356- 9939</dc:identifier> <rslpcd:locator xsi:type="dcterms:URI">http://copac.ac.uk/copac/wzgw</rslpcd:loc ator> <iesr:interface xsi:type="dcterms:URI">http://iesr.ac.uk/registry/intf/keys/1084 445356-9939-keys.xml</iesr:interface> <dc:type xsi:type="iesr:AccMthdList">webcgi</dc:type> <dc:type xsi:type="dcterms:DCMIType">Service</dc:type> <iesr:output xsi:type="dcterms:IMT">text/html</iesr:output> <dcterms:accessRights xsi:type="iesr:AuthList">none</dcterms:accessRights> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/linking.html</rslpcd:s eeAlso> <rslpcd:administrator xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084 445246-9103</rslpcd:administrator> <iesr:admeta> <dc:creator>Leigh Morris</dc:creator> <dc:contributor>COPAC service</dc:contributor> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-12-09</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </dcmitype:Service> <dcmitype:Service> <dc:title xml:lang="en-gb">COPAC's Z39.50 Target</dc:title> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445569- 11632</dc:identifier> <rslpcd:locator xsi:type="dcterms:URI">z3950s://z3950.copac.ac.uk:210/copac</rsl pcd:locator> <iesr:interface xsi:type="dcterms:URI">http://iesr.ac.uk/registry/intf/zeerex/10 84445569-11632-zx.xml</iesr:interface> <dc:type xsi:type="iesr:AccMthdList">z3950</dc:type> <dc:type xsi:type="dcterms:DCMIType">Service</dc:type> <dcterms:accessRights xsi:type="iesr:AuthList">none</dcterms:accessRights> <iesr:supportsStandard xsi:type="iesr:StdsList">bath-0-a</iesr:supportsStandard> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/z39.50/zed-support.htm l</rslpcd:seeAlso> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/z39.50/</rslpcd:seeAls o> <rslpcd:administrator xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084 445246-9103</rslpcd:administrator> <iesr:admeta> <dc:creator>COPAC service</dc:creator> <dc:creator>Leigh Morris</dc:creator> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-12-08</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </dcmitype:Service> <dcmitype:Service> <dc:title xml:lang="en-gb">COPAC Web Interface</dc:title> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445422- 10577</dc:identifier> <rslpcd:locator xsi:type="dcterms:URI">http://copac.ac.uk/</rslpcd:locator> <dc:type xsi:type="iesr:AccMthdList">webpage</dc:type> <dc:type xsi:type="dcterms:DCMIType">Service</dc:type> <dcterms:accessRights xsi:type="iesr:AuthList">none</dcterms:accessRights> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/quickguide.html</rslpc d:seeAlso> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/userguide.html</rslpcd :seeAlso> <rslpcd:administrator xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084 445246-9103</rslpcd:administrator> <iesr:admeta> <dc:creator>Leigh Morris</dc:creator> <dc:creator>COPAC service</dc:creator> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-11-10</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </dcmitype:Service> <dcmitype:Service> <dc:title xml:lang="en-gb">COPAC Text Interface</dc:title> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445413- 10492</dc:identifier> <rslpcd:locator xsi:type="dcterms:URI">http://copac.ac.uk/interfaces.html#text</ rslpcd:locator> <dc:type xsi:type="iesr:AccMthdList">webpage</dc:type> <dc:type xsi:type="dcterms:DCMIType">Service</dc:type> <dcterms:accessRights xsi:type="iesr:AuthList">none</dcterms:accessRights> <rslpcd:administrator xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084 445246-9103</rslpcd:administrator> <iesr:admeta> <dc:creator>Leigh Morris</dc:creator> <dc:creator>COPAC service</dc:creator> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-11-10</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </dcmitype:Service> <iesr:Agent> <dc:identifier xsi:type="dcterms:URI">http://purl.org/poi/iesr.ac.uk/1084445246- 9103</dc:identifier> <dc:title>MIMAS</dc:title> <dc:description>Service administrator</dc:description> <iesr:phone>+441612756109</iesr:phone> <iesr:email>info@mimas.ac.uk</iesr:email> <dc:relation xsi:type="dcterms:URI">http://www.mimas.ac.uk/</dc:relation> <iesr:logo xsi:type="dcterms:URI">http://www.mimas.ac.uk/images/mimas/mimas_d2.g if</iesr:logo> <iesr:admeta> <dc:creator>MIMAS</dc:creator> <dcterms:created xsi:type="dcterms:W3CDTF">2003-08-20</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066">en</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/2 .0/</dc:rights> </iesr:admeta> </iesr:Agent> </iesrDescription>
We see above a much fuller description of the COPAC service than our earlier "popup" window image showed. For the SPP proof of concept work we have extracted the contents of several elements - in particular note the "dcterms:abstract " element above. Our use of records from IESR means that we may now include much fuller data in the "popup" window for the end-user - such as subject and language coverage, temporal range of the COPAC collection, and so on. We imagine this would be very useful to the end-user. And the major benefit to SPP is that these CLD's are maintained centrally and expertly by IESR, and are made available to SPP automatically courtesy of the new, trial IESR "plug-in" - thereby permanently removing the burden of local CLD maintenance from SPP administrators.
Collection descriptions, once retrieved, are stored (when triggered by an end-user event) within Java objects that are available to the SPP cross-search API (for display to the end-user as and when required) and also cached within the SPP portal software for a certain number of days.
We have extended the SPP cross-search "collections" Java package to provide IESR "plug-in" support. A new sub-package of "collections" has been added, called "providers". It contains a Java interface class named "DescriptionsProvider" which encapsulates the functionality that any implementing DescriptionsProvider classes must be able to support (such as 'addDescription', 'getDescription' methods for each collection, plus an 'addCollection' so that each CLD may then effectively be registered with the SPP cross-search in readiness for display). The "providers" package also contains an abstract Java class named "AbstractDescriptionsProvider", which implements the "DescriptionProvider" interface and effectively represents a core template upon which its extensions may be based. We have provided two such extensions currently:
In SPP, to support the transformation of Z39.50 and other record formats to a core format (for consistent record display to the user), we use XSLT files. The SPP XSLT file for IESR currently extracts IESR content (as exampled in the above COPAC record obtained from IESR) from the following XML elements: "dcterms:abstract", "dc:rights", "dcterms:accessRights" and "iesr:logo" and cocatenates them as the "Description" of the particular data collection. It also extracts the content from the the dc:title and url identifier elements, the final content being saved to three summary fields: Title, Description and URL. It is these that are ultimately displayed to an end-user.
Caching is supported in SPP software, and for DescriptionProviders, the software has been configured to allow the specification of the CLD cache period in days, - this is defined in the provider's definition: cache_ttl.
Here's the above COPAC example using data drawn from the IESR
Reliance on IESR means just that for data quality and service availability. Using IESR does not mean a less efficient SPP service in some way, because records are retrieved from IESR and then cached for use in the portal (rather than records being retrieved "on the fly"). In addition, as "backup" to IESR, SPP software could maintain default data in the local CLD file to cope with the unlikely event of IESR downtime. In summary, we do not see any technical drawbacks to using the IESR "plug-in" to derive CLD and SLD.
However we would make a note regarding the point of contact with data providers: supposing RDN hubs manage portal software locally in future, then we might anticipate that they are potentially in a strong position to strike up/maintain mutually beneficial relationships with subject-specialist data providers that offer search targets. Already several SPP targets came to be included in search landscapes as a result of good relationships between hub managers and data provider managers. This sort of relationship can be characterised by, for example, specially negotiated content access on an institutional / user group basis, or technical discussions that help improve network access to data (for example a hub might influence a data provider's decision to move from providing website-only access to their data to additionally providing an OAI or even SRW server for machine2machine access). These issues are clearly related to servlce level access. If the IESR (instead of Hub portal administrators) is the main point of contact for data providers across the full range of subject specialisms - a broker service in this context - then it might be helpful to analyse further the way in which IESR will come to represent its portal client base in future.
Unlikely at this stage as Z39.50 access works sufficiently well for SPP. Should SOAP or SRW fully replace Z39.50 as a standard in the future however, then SPP would simply switch to using SOAP access to IESR in a very similar way (technically, this would basically require replacing the Z39.50 client of the IESR "plugin" with a SOAP/SRW client).
Aside from outstanding issues related to the technical improvement of our early trials with IESR (which are: i) a requirement to ensure IESR descriptions are stored in the appropriate Java object at portal startup time (at present the retrieval of cached CLD's is triggered by user interaction with the portal interface which can slow down the display of the search portlet if no valid cached copies already exist at that point) ii) a requirement for a configurable daemon to operate the "plug-in" at set intervals, ii) a possible requirement to extract fuller IESR record metadata for SPP than currently provided), we have some suggestions for the enhancement of IESR's service to/interaction with SPP. These suggestions (in no particular order) are:
<dcmitype:Service> <dc:title xml:lang="en-gb" iesr:idx="n">COPAC's Z39.50 Target</dc:title> <dc:identifier xsi:type="dcterms:URI" iesr:idx="n">1084445569-11632</dc:identifier> <rslpcd:locator xsi:type="dcterms:URI">z3950s://z3950.copac.ac.uk:210/copac</rslpcd:locator> <iesr:interface xsi:type="dcterms:URI">http://iesr.ac.uk/registry/intf/zeerex/1084445569-11632-zx.xml</iesr:interface> <dc:type xsi:type="iesr:AccMthdList">z3950</dc:type> <dc:type xsi:type="dcterms:DCMIType">Service</dc:type> <dcterms:accessRights xsi:type="iesr:AuthList">none</dcterms:accessRights> <iesr:supportsStandard xsi:type="iesr:StdsList">bath-0-a</iesr:supportsStandard> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/z39.50/zed-support.html</rslpcd:seeAlso> <rslpcd:seeAlso xsi:type="dcterms:URI">http://copac.ac.uk/z39.50/</rslpcd:seeAlso> <rslpcd:administrator xsi:type="dcterms:URI">1084445246-9103</rslpcd:administrator> <iesr:admeta> <dc:creator>COPAC service</dc:creator> <dc:creator>Leigh Morris</dc:creator> <dc:contributor>MIMAS</dc:contributor> <dcterms:created xsi:type="dcterms:W3CDTF">2003-12-08</dcterms:created> <dcterms:modified xsi:type="dcterms:W3CDTF">2004-05-13</dcterms:modified> <dc:language xsi:type="dcterms:RFC3066" iesr:idx="n">en-gb</dc:language> <dc:rights xsi:type="dcterms:URI">http://creativecommons.org/licenses/by-nc-sa/1.0/</dc:rights> </iesr:admeta> </dcmitype:Service>In the case of Z39.50 targets, SPP software uses critical Z39.50 connection data to make client connections to a targets Z39.50 server. For COPAC this data is given (in the rslpcd:locator element) as "z3950s://z3950.copac.ac.uk:210/copac". Further studies would be required in order to determine if and how additional information from IESR (for example that a target supports the Bath profile standard for Z39.50, or that there is/is not Athens - or other - access control for this target, or that a target supports certain Z39.50 'fields' for searches, as indicated in IESR ZeeRex files) might be used by SPP.