SMS Message from OPAC

This is a very simple and elegant way of capturing the title and call number within the OPAC interface to forward to a script that generates an email to the mobile service providers' email-to-SMS gateways. While my previous implementation of SMS capabilities is much more cumbersome and elaborate to set up, relying on Index Data's YAZ open-source Z39.50 software, it does capture real-time circulation status and item locations, in addition to the call number and title. I have not been able to figure out how to grab those pieces of information from the holdings display section in the OPAC using native XML/XSLT as Paul has, but would be very interested if anyone can come up with a solution that can do so.

--Steve Watkins, California State University, Monterey Bay

swatkins at csumb.edu

I was able to re-write the asp code into php and get the title and call number SMS messaging working from my opac.  I still can't figure how to extract the location and item status via callSearch.xsl

-Ryan Edwards, CSU Channel Islands

I did the same thing as Ryan Edwards. I did get the location and item status (for each holdings,
parse out in your PHP code). Here is what I have. BTW great application, kudos to Paul.

Relevant sections of files:

/m1/voyager/xxxdb/tomcat/vwebv/context/vwebv/ui/yourskin/xsl/contentLayout/display/display.xsl
<!-- WVC1 Added this template, which is called by callSearch.xsl. The purpose of
this template is to get location information to be passed to SMS script jsh 11-6-2009 -->

<xsl:template name="JHLOCATE">

<!-- xsl:variable name="holdingsData" -->
<xsl:for-each select="$HoldXML/mfhd:mfhdRecord">

<xsl:variable name="mfhdId" select="@mfhdId"/>
<xsl:for-each select="$holdingsConfig">

<xsl:call-template name="buildMarcDisplay">
<xsl:with-param name="mfhdID" select="$mfhdId"/>
<xsl:with-param name="recordType" select="'mfhd'"/>
</xsl:call-template>

</xsl:for-each>

</xsl:for-each>
<!-- /xsl:variable -->

</xsl:template>

/m1/voyager/xxxdb/tomcat/vwebv/context/vwebv/ui/yourskin/xsl/callSearch.xsl
<xsl:template name="recordCallSearch">

<xsl:variable name="titlename">
<xsl:call-template name="BMDProcessMarcTags">
<xsl:with-param name="field" select="'245'"/>
<xsl:with-param name="indicator1" select="'X'"/>
<xsl:with-param name="indicator2" select="'X'"/>
<xsl:with-param name="subfield" select="'a'"/>
<xsl:with-param name="mfhdID" select="$bibID"/>
<xsl:with-param name="recordType" select="'bib'"/>
</xsl:call-template>
</xsl:variable>
<xsl:variable name="holdingsdata">
<xsl:call-template name="JHLOCATE"/>
</xsl:variable>
<!-- Replaced spaces, ampersands, question marks with underscores in holdings data and title -->
<xsl:variable name="titlename0">
<xsl:value-of select="translate($titlename, ' ', '_')"/>
</xsl:variable>
<xsl:variable name="titlename1">
<xsl:value-of select="translate($titlename0, '&', '_')"/>
</xsl:variable>
<xsl:variable name="titlename2">
<xsl:value-of select="translate($titlename1, '?', '_')"/>
</xsl:variable>

<xsl:variable name="locationname0">
<xsl:value-of select="translate($holdingsdata, ' ', '_')"/>
</xsl:variable>
<xsl:variable name="locationname1">
<xsl:value-of select="translate($locationname0, '&', '_')"/>
</xsl:variable>
<xsl:variable name="locationname2">
<xsl:value-of select="translate($locationname1, '?', '_')"/>
</xsl:variable>

etc.

Another way to retrieve Call Number, Location, and Status information is to define variables directly at the top of display.xsl

<xsl:variable name="hamLoc" select="//hol:mfhdCollection/mfhd:mfhdRecord/mfhd:mfhdData[@name='locationDisplayName']"/>
<xsl:variable name="hamCall" select="//hol:mfhdCollection/mfhd:mfhdRecord/mfhd:mfhdData[@name='callNumber']"/>
<xsl:variable name="hamStatus" select="//hol:mfhdCollection/mfhd:mfhdRecord/mfhd:itemCollection/item:itemRecord/item:itemData[@name='displayStatus']"/>

and then call these in callSearch.xsl and edit the php or other files used to assemble the SMS text.