Search API (deprecated)

To return search results in XML format, the URL string should be in this format:

The available variables are as follows:

id_issue is the issue id of the issue to be searched. This can be found in the dashboard under Distribution Links -> Digital Edition -> This Issue as the number after "i=".

keyword is the search term or terms (URL encoded).

searchin is one of the following:

0 = current issue,

1 = latest issue of publication of which this is an issue (ordered by issue date),

2 = all issues with an issue date of the current year

3 = all issues of this publication

4 = all issues of all publications for this publisher

mode is one of the following search modes:

any = match any term in the search string,

all = match all terms in the search string,

phrase = match the exact phrase in the search string

The URL will return an XML document similar to this:

<search issueid='15466' page='4' type='2' url_mag=' server' title='Page 4' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
4 14 This eWEEK Amid all the talk about the new ways in which enter- prises will communicate, Microsoft Exchange Server is the platform on which many do communicate. Best of The best of eWEEK on the Web
<word page='4' x='505' y='414' x2='600' y2='441'>Exchange</word>
<word page='4' x='600' y='414' x2='666' y2='441'>Server</word>
<search issueid='15466' page='6' type='2' url_mag=' server' title='Page 6' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
contents 18 Labs@Work Microsoft Exchange Server 2010 Beta 1 offers a richer Webmail client, consis- tency across browsers and improved management capabilities. 22 Jim
<word page='6' x='439' y='200' x2='534' y2='228'>Exchange</word>
<word page='6' x='534' y='200' x2='600' y2='228'>Server</word>
<search issueid='15466' page='12' type='2' url_mag=' server' title='Page 12' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
This A Debra Donston Exchange rating fter loads of buzz about the potential new ways enterprises will be communicating in the future&#x2014;via blogs and
<word page='12' x='293' y='210' x2='595' y2='286'>Exchange</word>
<word page='12' x='564' y='473' x2='642' y2='499'>Exchange</word>
<word page='12' x='291' y='497' x2='348' y2='523'>Server.</word>
<word page='12' x='516' y='522' x2='591' y2='547'>Exchange</word>
<word page='12' x='588' y='522' x2='642' y2='547'>Server</word>
<word page='12' x='540' y='569' x2='592' y2='595'>server</word>
<word page='12' x='563' y='664' x2='643' y2='689'>Exchange,</word>
<word page='12' x='291' y='711' x2='368' y2='737'>Exchange</word>
<word page='12' x='369' y='711' x2='425' y2='737'>Server</word>
<word page='12' x='412' y='924' x2='490' y2='950'>Exchange</word>
<word page='12' x='291' y='948' x2='346' y2='973'>Server</word>
<word page='12' x='421' y='1184' x2='498' y2='1210'>Exchange</word>
<word page='12' x='497' y='1184' x2='553' y2='1210'>Server</word>
<word page='12' x='659' y='380' x2='735' y2='405'>Exchange</word>
<word page='12' x='733' y='380' x2='787' y2='405'>Server</word>
<word page='12' x='526' y='775' x2='675' y2='817'>exchange</word>
<word page='12' x='675' y='775' x2='775' y2='817'>server</word>
<word page='12' x='350' y='1255' x2='405' y2='1281'>server</word>
<word page='12' x='419' y='1303' x2='496' y2='1328'>Exchange</word>
<word page='12' x='550' y='1350' x2='603' y2='1376'>server</word>
<search issueid='15466' page='20' type='2' url_mag=' server' title='Page 18' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
that Micro- soft faces in putting together the first new version of its messag- ing and communications platform since Exchange Server 2007 was released in 2006. The next version of Exchange needs to work well in the new more
<word page='20' x='132' y='1279' x2='223' y2='1305'>Exchange</word>
<word page='20' x='225' y='1279' x2='288' y2='1305'>Server</word>
<word page='20' x='101' y='1327' x2='189' y2='1353'>Exchange</word>
<word page='20' x='502' y='1327' x2='589' y2='1353'>Exchange</word>
<word page='20' x='590' y='1327' x2='650' y2='1353'>Server</word>
<word page='20' x='132' y='437' x2='519' y2='534'>Exchange</word>
<word page='20' x='318' y='634' x2='438' y2='667'>Exchange</word>
<word page='20' x='441' y='634' x2='523' y2='667'>Server</word>
<word page='20' x='927' y='1327' x2='1012' y2='1353'>Exchange</word>
<search issueid='15466' page='22' type='2' url_mag=' server' title='Page 20' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
on help desk calls. Clicking on the Options link in the Outlook Web Access client brings up the Web-based Exchange Control Panel. From here, users can carry out stan- dard self-service tasks such as updat- ing contact information and
<word page='22' x='826' y='262' x2='906' y2='288'>Exchange</word>
<word page='22' x='106' y='628' x2='179' y2='653'>Exchange</word>
<word page='22' x='78' y='690' x2='181' y2='713'>EXCHANGE</word>
<word page='22' x='180' y='690' x2='256' y2='713'>SERVER</word>
<word page='22' x='78' y='711' x2='135' y2='737'>Server</word>
<word page='22' x='197' y='806' x2='280' y2='832'>Exchange</word>
<word page='22' x='279' y='806' x2='336' y2='832'>Server</word>
<word page='22' x='252' y='948' x2='342' y2='974'>Exchange,</word>
<word page='22' x='78' y='1066' x2='162' y2='1092'>Exchange</word>
<word page='22' x='162' y='1066' x2='220' y2='1092'>Server</word>
<word page='22' x='419' y='1071' x2='562' y2='1105'>Exchange</word>
<word page='22' x='565' y='1071' x2='662' y2='1105'>Server</word>
<word page='22' x='632' y='1100' x2='702' y2='1124'>Exchange</word>
<word page='22' x='700' y='1100' x2='749' y2='1124'>Server</word>
<word page='22' x='851' y='1143' x2='920' y2='1167'>Exchange</word>
<word page='22' x='918' y='1143' x2='967' y2='1167'>Server</word>
<word page='22' x='580' y='1187' x2='649' y2='1211'>Exchange</word>
<word page='22' x='648' y='1187' x2='699' y2='1211'>Server,</word>
<word page='22' x='628' y='1250' x2='697' y2='1276'>Exchange</word>
<word page='22' x='696' y='1250' x2='745' y2='1276'>Server</word>
<word page='22' x='714' y='640' x2='799' y2='666'>Exchange</word>
<word page='22' x='799' y='640' x2='858' y2='666'>Server</word>
<word page='22' x='746' y='853' x2='832' y2='879'>Exchange</word>
<word page='22' x='871' y='948' x2='956' y2='974'>Exchange</word>
<word page='22' x='956' y='948' x2='1015' y2='974'>Server</word>
<search issueid='15466' page='23' type='2' url_mag=' server' title='Page 21' pic_url='' issue_name='April 20, 2009' publication_name='eWEEK Magazine'>
How- ever, there is a greater use of tools such as wizards to ease the configuration of many common Exchange settings. The Exchange Federation Gateway feature makes it possible for organi- zations to share Exchange data eas- ily across
<word page='23' x='214' y='262' x2='297' y2='288'>Exchange</word>
<word page='23' x='142' y='285' x2='225' y2='311'>Exchange</word>
<word page='23' x='224' y='333' x2='309' y2='359'>Exchange</word>
<word page='23' x='237' y='380' x2='322' y2='406'>Exchange</word>
<word page='23' x='232' y='664' x2='301' y2='690'>servers,</word>
<word page='23' x='469' y='167' x2='539' y2='193'>servers.</word>
<word page='23' x='642' y='191' x2='704' y2='217'>server,</word>
<word page='23' x='437' y='214' x2='493' y2='240'>server</word>
<word page='23' x='518' y='522' x2='604' y2='548'>Exchange</word>
<word page='23' x='602' y='522' x2='661' y2='548'>Server</word>
<word page='23' x='504' y='593' x2='592' y2='619'>Exchange</word>
<word page='23' x='898' y='309' x2='986' y2='337'>Exchange?</word>
<word page='23' x='850' y='391' x2='924' y2='418'>Servers?</word>

Each of the search elements is a hit and only one search element is displayed per page.

The attributes returned are as follows:

<issueid> is the issue id of the issue with the hit.

<page> is the sequential page number or the page.

<type> attribute has no meaning and is just there for historical reasons.

<url_mag> attribute is the URL that, when appended to "" (or the appropriate masked domain), will bring up the issue at the page on which the hit occurred.

<title> is the name of the page on which the hit occurred.

<pic_url> is a URL that shows a thumbnail of the page on which the hit occurred.

<publication_name> is the name of the publication.

<issue_name> is the name of the issue.

Between the opening and closing of the search element is contextual text in which the hit occurred. There is one <word> element for every hit, even if there is more than one per page. Each <word> element displays the sequential page number (the <page> attribute), the x and y flash coordinates of the hit (X, Y, X2, and Y2). And finally between the opening and closing of the <word> element is the search term.