Ready to Learn?Ex Libris products all provide open APIs

Rapid Service Indicator

General Purpose

The Rapid Service Indicator API (RSI) offers an interface for querying the SFX KnowledgeBase for the availability of specific journals and books identified by identifiers such as ISSN/ISBN/LCCN/OBJECT_ID/CODEN. By default, it checks only for full text services. It replaces the deprecated Journal Subscription Index API (JSI).
The following information describes how to use the Rapid Service Indicator (RSI).
The improvements in the RSI over the JSI include:
  • RSI includes not only journals, but also books.
  • RSI allows searching not just by ISSN, but also by OBJECT_ID, ISBN, LCCN, and CODEN.
  • RSI has full support for consortia APIs. It also takes into account institute specific activation and allows the sending of IP information so that SFX can determine the appropriate institute.
  • RSI can respond with YES/NO and also a third value "MAYBE" when multiple objects are found.
New syntax:
XML requests should be sent to the following address/program:
<SFX server>:<port>/<sfx_instance>/cgi/core/rsi/rsi.cgi
The request can be sent using GET or POST method, using the parameter request_xml. The POST method is recommended due to the length of the XML query.
 

Setup

To use this API, an index containing all active objects and the limitations of their availability needs to be created. To create this index, run the Rapid Service Indicator Indexing process, available via server_admin_util.
For SFX 4:
1. Build the RSI table.
  • Access the server as the instance user (e.g. sfxlcl4)
  • Type da to move to the admin directory.
  • Start the server Admin utility by typing ./server_admin_util
  • Select option 11 and then option 1:
 
11 build RSI index RSI Tools
1 (Re)build the RSI index
2 Show scheduled RSI index builds
3 Schedule an RSI index build
Please select [1-3,q,m]: 1
 
You will see this:
 
Running the index builder may take a long time, possibly hours depending on the amount of active portfolios.
Are you sure you want to continue? [y/n] y
beginning preparation:creating tables,checking consortia
Checking for consortia records... Consortia check done.
build RAPID_SERVICE_INDICATOR table.
build RSI_IDENTIFIERS table. Preparation done.
fetching active portfolios.
uploading identifiers active portfolios to RSI_IDENTIFIERS
Done uploading records to RSI_IDENTIFIERS
receiving active portfolios from RAPID_SERVICE_INDICATOR_TEMP.
Done uploading records to RAPID_SERVICE_INDICATOR_TEMP.
uploading active portfolios to RAPID_SERVICE_INDICATOR.
Done uploading records to RAPID_SERVICE_INDICATOR Preparation done.
 
2. Set up the cron job for RSI.
  • Access the server as the instance user (e.g. sfxlcl4).
  • Type da to move to the admin directory.
  • Start the Admin utility by typing ./server_admin_util
  • Select option 11 and then option 3 Schedule an RSI index build.
The process will look like this:
Please enter scheduling parameters
Time must be in the form HH:MM where HH can be: 00-23for midnight-11PM
or for every hour MM can be: 00-59
or for every minute
Enter the time to run [00:00]:00:00
Would you like to schedule for a certain weekday? [Y/n] N
Please enter month (1-12 for January-December respectively or '*' for every month) [*]: *
Please enter day of the month (1-31 or '*' for every day) [1]: 1
Successfully added the refresh task to your crontab.
 
3. If your instance has been set up to use services from another instance via Consortia API, add a section for RSI in the config/consortium.config file of your instance.
More information can be found in the Setting up Model 2 - Including Services in the SFX Menu Screen from a Different SFX Instance section of the Using SFX in a Consortium Environment document.
After set-up has been completed, it is possible to use either the JSI syntax as described in El Commons or use the RSI syntax (recommended since it has more options).
No changes are needed in Metalib/Primo or other external applications since the RSI still supports the JSI syntax, although both products are expected to move to using RSI syntax in future.
4. By default, the RSI Index includes those types of services that are defined in the Configuration > A-Z List section of the SFX Admin Center. It is possible to change this by using the config/rsi.config file of the local instance.
The following is an example of the rsi.config file:
#This file contains the list of serviceTypes which will be included in the RSI index.
#The RSI index is used for both RSI API and A-Z - so it is recommended
# to set to 'Y' all serviceTypes which you would like to use in either RSI or A-Z list.

Section "retrievalType"
# Set next parameter to 1 for automatically detect serviceType settings defined in A-Z configuration (all profiles taken into account)
# If you set this parameter to 0 or no A-Z profiles defined in current instance serviceTypes will be taken from next section ("serviceTypes")
Automatically 1
EndSection

Section "serviceTypes"
getFullTxt Y
getSelectedFullTxt N
getAbstract N
getTOC N
getHolding N
EndSection

#NOTE: for customers with consortia API, we will need to recommend
# that they manually define the serviceType settings in the 'shared'
# instance - as their local A-Z configuration may not correspond to what
# serviceTypes the local instances want in their A-Z.
 

Input Parameters

The following are Rapid Service Indicator API input parameters:

ElementDescriptionValueDefaultStructure
?xml version="1.0"?Description of XML version usedno value  
IDENTIFIER_REQUESTThis is the main element of the request  root element
VERSIONVersion information. Fixed value.string1.0attribute of IDENTIFIER_REQUEST
xsi:noNamespaceSchemaLocation?string"ISSNRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"attribute of IDENTIFIER_REQUEST
IDENTIFIER_REQUEST _ITEMThis is a mandatory element containing all sub-elements pertinent to the  request of a single ContextObject.no value sub-element of IDENTIFIER_REQUEST
IDENTIFIERThis is a mandatory element containing a single IDENTIFIER. This element can be repeated more than once denoting multiple identifiers to be searched.Key:value where key
can be: ISSN/ISBN/LCCN/OBJECT_ID/CODEN
 sub-element of IDENTIFIER_REQUEST_ITEM
YEARThis is an optional element containing a year written in 4 digits. If included, the API will look for availability of the journal/book for the given year alone. If no year is specified, the API will check whether YEAR information exists in the RSI index. If no year information exists in the RSI, the resulting XML will be 'found'. If year information exists, the response will be 'not found'. string sub-element of IDENTIFIER_REQUEST_ITEM
VOLUMEThis is an optional element containing a volume number.string sub-element of IDENTIFIER_REQUEST_ITEM
ISSUEThis is an optional element containing an issue number.  sub-element of IDENTIFIER_REQUEST_ITEM
INSTITUTE_NAMEThis is an optional element containing an institute name. This element can be repeated more then once denoting multiple institutes to be searched for availability.string sub-element of IDENTIFIER_REQUEST_ITEM
IPThis is an optional element containing an IP addressstring sub-element of IDENTIFIER_REQUEST_ITEM
REQUESTED_SERVICESDefines the type of service that is checked in RSI. In order to be able to send RSI queries for services other than full text, special configuration is needed. Refer to the set-up section information in the rsi.config configuration file.String - values can be: getFullTxt, getSelectedFullTxt, getAbstract, getTOC, getHolding.
Only one service can be checked - this is not a repeatable tag.
getFullTxt - This is the service type that is checked if a tag is not included.sub-element of IDENTIFIER_RESPONSE_DETAILS

 

Input XML Format

Example:

<?xml version="1.0" ?>

<IDENTIFIER_REQUEST VERSION="1.0" xsi:noNamespaceSchemaLocation="ISSNRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<IDENTIFIER_REQUEST_ITEM>

<IDENTIFIER>issn:0000-0001</IDENTIFIER>

<IDENTIFIER>LCCN:110997393589006</IDENTIFIER>

<IDENTIFIER>object_id:1000000000020922</IDENTIFIER>

<YEAR>1995</YEAR>

<VOLUME>1</VOLUME>

<ISSUE>15</ISSUE>

<institute_name>science_lab</institute_name>

<IP>10.1.1.1</IP>

</IDENTIFIER_REQUEST_ITEM>

</IDENTIFIER_REQUEST>

 

Output Parameters

The following are Rapid Service Indicator API output parameters:

ElementDescriptionValueDefaultStructure
?xml version="1.0"?Description of XML version usedno value  
IDENTIFIER_RESPONSEThis is the main element of the responseno value root element
VERSIONVersion information. Fixed value.string1.0attribute of ISSN_REQUEST
IDENTIFIER_REQUEST_RESULTThis element reports the status of the query. Possible value of the REQUEST attribute are: 
-         OK - If the query was run correctly 
-         MalformedRequest -  If the XML request was not properly constructed 
-         ServiceUnavailable - If the API is unavailable 
string sub-element of IDENTIFIER_RESPONSE
IDENTIFIER_RESPONSE_ITEMThis is a mandatory element containing all sub elements pertinent to a single response.no value sub-element of IDENTIFIER_RESPONSE
IDENTIFIER_REQUEST_ITEMThis is the IDENTIFIER_REQUEST_ITEM as it was sent in the API request.no value sub-element of IDENTIFIER_RESPONSE_ITEM
IDENTIFIERThis is a mandatory element containing a single IDENTIFIER. This element can be repeated more than once denoting multiple identifiers to be searched. Key: value where key can be ISSN/ISBN/LCCN/OBJECT_ID/CODEN sub element of IDENTIFIER_REQUEST_ITEM
YEARThis is an optional element containing a year written in 4 digits. The API will look for availability of the journal for the given year alone. If no year is specified, the API will ignore date thresholds and search for any availability of the journal.string sub-element of IDENTIFIER_REQUEST_ITEM
VOLUMEThis is an optional element containing a volume number.string sub-element of IDENTIFIER_REQUEST_ITEM
ISSUEThis is an optional element containing an issue number.string sub-element of IDENTIFIER_REQUEST_ITEM
INSTITUTE_NAMEThis is an optional element containing an institute name. This element can be repeated more then once denoting multiple institutes to be searched for availability.  sub-element of IDENTIFIER_REQUEST_ITEM
IPThis is an optional element containing an IP addressString sub-element of IDENTIFIER_REQUEST_ITEM
IDENTIFIER_RESPONSE_DETAILSThis element contains the details of the response from the server.no value sub-element of IDENTIFIER_RESPONSE_ITEM
CONTENTIncludes error messages returned by RSIstring sub-element of IDENTIFIER_RESPONSE_DETAILS
RESULTISSN availability. Possible values are FoundNotFound, and Maybe.string sub-element of IDENTIFIER_RESPONSE_DETAILS
PEER_REVIEWEDThis element will include one PEER_REVIEW entry when the result is 'Found' and multiple PEER_REVIEW entries seperated by a comma when the result is 'Maybe'. Possible values are 'YES' or 'NO'.string sub-element of IDENTIFIER_RESPONSE_DETAILS
OBJECT_IDThis element will include one SFX OBJECT_ID when the result is 'Found' and multiple results seperated by a comma when the result is 'Maybe'.string sub-element of IDENTIFIER_RESPONSE_DETAILS
AVAILABLE_SERVICESThis element will include one 'getFullTxt' entry when the result is 'Found' and multiple 'getFullTxt' entries seperated by a comma when the result is 'Maybe'. RSI API is currently limited to the getFulltxt service.string sub-element of IDENTIFIER_RESPONSE_DETAILS

 

Output XML Format

Example:

<?xml version="1.0" ?>

  <IDENTIFIER_RESPONSE VERSION="1.0">

  <IDENTIFIER_REQUEST_RESULT RESULT="OK" />

  <IDENTIFIER_RESPONSE_ITEM>

  <IDENTIFIER_REQUEST_ITEM>

  <IDENTIFIER>object_id:111082404606014</IDENTIFIER>

  <ISSUE>15</ISSUE>

  <VOLUME>1</VOLUME>

  <YEAR>1995</YEAR>

  <institute_name>science_lab</institute_name>

  </IDENTIFIER_REQUEST_ITEM>

  <IDENTIFIER_RESPONSE_DETAILS>

  <AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>

  <OBJECT_ID>111082404606014</OBJECT_ID>

  <RESULT>found</RESULT>

  </IDENTIFIER_RESPONSE_DETAILS>

  </IDENTIFIER_RESPONSE_ITEM>

  <REQUESTED_SERVICES />

  </IDENTIFIER_RESPONSE>

 

 

More Rapid Service Indicator examples

RSI request examples

1. Example with ISBN, where no active full text services were found:

Request:
<sfx_base_url>/cgi/core/rsi/rsi.cgi?request_xml=<?xml%20version="1.0"%20?><IDENTIFIER_REQUEST%20VERSION="1.0"%20xsi:noNamespaceSchemaLocation="IBSNRequest.xsd"%20xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISBN:979-0-051-93376-1</IDENTIFIER></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>

Response:
<?xml version="1.0"?>
<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISBN: 979-0-051-93376-1</IDENTIFIER>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES/>
<OBJECT_ID/>
<PEER_REVIEWED/>
<RESULT>not found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>

2. Example with ISSN, where at least one active full text service was found.
List of supported identifiers: ISSN, ISBN, CODEN, LCCN, OBJECT_ID

Request:
<sfx_base_url>/cgi/core/rsi/rsi.cgi?request_xml=<?xml%20version="1.0"%20?><IDENTIFIER_REQUEST%20VERSION="1.0"%20xsi:noNamespaceSchemaLocation="ISSNRequest.xsd"%20xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:0000-0019</IDENTIFIER><YEAR>2006</YEAR><ISSUE>6</ISSUE><VOLUME>253</VOLUME></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>

Response:
<?xml version="1.0"?>
<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:0000-0019</IDENTIFIER>
<ISSUE>6</ISSUE>
<VOLUME>253</VOLUME>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>
<OBJECT_ID>954921332001</OBJECT_ID>
<PEER_REVIEWED>NO</PEER_REVIEWED>
<RESULT>found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>

3. Example with RSI request in case more than one CTXO is sent in one request:

<sfx_base_url>/cgi/core/rsi/rsi.cgi?request_xml=<?xml%20version="1.0"%20?><IDENTIFIER_REQUEST%20VERSION="1.0"%20xsi:noNamespaceSchemaLocation="ISSNRequest.xsd"%20xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:0000-0019</IDENTIFIER><YEAR>2006</YEAR><ISSUE>6</ISSUE><VOLUME>253</VOLUME></IDENTIFIER_REQUEST_ITEM><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:1120-9879</IDENTIFIER><YEAR>2006</YEAR></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>
<?xml version="1.0"?>

<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:0000-0019</IDENTIFIER>
<ISSUE>6</ISSUE>
<VOLUME>253</VOLUME>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>
<OBJECT_ID>954921332001</OBJECT_ID>
<PEER_REVIEWED>NO</PEER_REVIEWED>
<RESULT>found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:1120-9879</IDENTIFIER>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES/>
<OBJECT_ID/>
<PEER_REVIEWED/>
<RESULT>not found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>

4. Request can be restricted to specific services only (single or list).
In the example below getFullTxt and getAbstract are used for restriction.

<sfx_base_url>/cgi/core/rsi/rsi.cgi?request_xml=<?xml version="1.0" ?><IDENTIFIER_REQUEST VERSION="1.0" xsi:noNamespaceSchemaLocation="ISSNRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:0000-0019</IDENTIFIER><REQUESTED_SERVICES>getAbstract,getFullTxt</REQUESTED_SERVICES><YEAR>2006</YEAR><ISSUE>6</ISSUE><VOLUME>253</VOLUME></IDENTIFIER_REQUEST_ITEM><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:1120-9879</IDENTIFIER><YEAR>2006</YEAR></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>

<?xml version="1.0"?>
<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:0000-0019</IDENTIFIER>
<ISSUE>6</ISSUE>
<REQUESTED_SERVICES>getAbstract,getFullTxt</REQUESTED_SERVICES>
<VOLUME>253</VOLUME>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>
<OBJECT_ID>954921332001</OBJECT_ID>
<PEER_REVIEWED>YES</PEER_REVIEWED>
<RESULT>found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:1120-9879</IDENTIFIER>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES/>
<OBJECT_ID/>
<PEER_REVIEWED/>
<RESULT>not found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>

5. Request can be restricted on institute or group(single only). 
In below example institute name is: instA.
Institute/Group can be detected by SFX automatically by IP range if configured.

<sfx_base_url>http://il-sfx04:3420/michael/cgi/core/rsi/rsi.cgi?request_xml=<?xml version="1.0" ?><IDENTIFIER_REQUEST VERSION="1.0" xsi:noNamespaceSchemaLocation="ISSNRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:0000-0019</IDENTIFIER><REQUESTED_SERVICES>getAbstract,getFullTxt</REQUESTED_SERVICES><INSTITUTE_NAME>instA</INSTITUTE_NAME><YEAR>2006</YEAR><ISSUE>6</ISSUE><VOLUME>253</VOLUME></IDENTIFIER_REQUEST_ITEM><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:1120-9879</IDENTIFIER><YEAR>2006</YEAR></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>

<?xml version="1.0"?>
<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:0000-0019</IDENTIFIER>
<INSTITUTE_NAME>instA</INSTITUTE_NAME>
<ISSUE>6</ISSUE>
<REQUESTED_SERVICES>getAbstract,getFullTxt</REQUESTED_SERVICES>
<VOLUME>253</VOLUME>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>
<OBJECT_ID>954921332001</OBJECT_ID>
<PEER_REVIEWED>YES</PEER_REVIEWED>
<RESULT>found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:1120-9879</IDENTIFIER>
<YEAR>2006</YEAR>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES/>
<OBJECT_ID/>
<PEER_REVIEWED/>
<RESULT>not found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>

6. If year/volume/issue information is not available or not wished to be used one can specify to ignore date threshold check (works exactly as specifying sfx.ingnore_date_threshold=1 in OpenURL):

<sfx_base_url>/cgi/core/rsi/rsi.cgi?request_xml=<?xml version="1.0" ?><IDENTIFIER_REQUEST VERSION="1.0" xsi:noNamespaceSchemaLocation="ISSNRequest.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><IDENTIFIER_REQUEST_ITEM><IDENTIFIER>ISSN:0000-0019</IDENTIFIER><IGNORE_DATE_THRESHOLD>1</IGNORE_DATE_THRESHOLD></IDENTIFIER_REQUEST_ITEM></IDENTIFIER_REQUEST>

<?xml version="1.0"?>
<IDENTIFIER_RESPONSE VERSION="1.0">
<IDENTIFIER_REQUEST_RESULT RESULT="OK"/>
<IDENTIFIER_RESPONSE_ITEM>
<IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER>ISSN:0000-0019</IDENTIFIER>
<IGNORE_DATE_THRESHOLD>1</IGNORE_DATE_THRESHOLD>
</IDENTIFIER_REQUEST_ITEM>
<IDENTIFIER_RESPONSE_DETAILS>
<AVAILABLE_SERVICES>getFullTxt</AVAILABLE_SERVICES>
<OBJECT_ID>954921332001</OBJECT_ID>
<PEER_REVIEWED>YES</PEER_REVIEWED>
<RESULT>found</RESULT>
</IDENTIFIER_RESPONSE_DETAILS>
</IDENTIFIER_RESPONSE_ITEM>
<REQUESTED_SERVICES/>
</IDENTIFIER_RESPONSE>