Sample Queries for Twitter Channel
Installing the Genesys Driver for Use with Twitter places a file driver-for-twitter-options.cfg in the C:\Program Files\GCTI\eServices 8.1.0\Genesys Social Messaging Server\<SM-Server-Application-name>\media-channel-drivers\channel-twitter directory.
Importing this file into your Social Messaging Server Application object introduces various configuration options, including four that specify sample queries to Twitter. These options are instances of the "class" option qry-<name>, which is described in Twitter Channel.
Search Query Options
These options are imported as part of driver-for-twitter-options.cfg.
|Name||Value||Returns messages that|
|qry-alu||ALU||Contain the text string ALU|
|qry-from-somebody||from:GenesysCustomer||Have a from field equal to GenesysCustomer|
|qry-ipad||iPad :(||Contain the text string iPad :(|
|qry-to-somebody||to:GenesysCustomer||Have a to field equal to GenesysCustomer|
Search queries are regular Twitter search expressions, as described at https://dev.twitter.com/docs/using-search. The results are sets of messages with accompanying attributes like addresses, IDs, and so on. Each message is transferred to Social Messaging Server as a separate message and is submitted to Interaction Server as a separate interaction.
- Timeline queries get statuses from Twitter timelines; more information is at http://dev.twitter.com/doc/get/statuses/home_timeline. The query result is a set of statuses with accompanying data. Each status is transferred to Social Media Server as a separate message and is submitted to Interaction Server as a separate interaction.
- Mention queries are a subtype of timeline query. The result is a set of messages that contain references to the user’s name, such as @JohnD.
- Direct message queries get direct messages sent to an account; more information is at https://dev.twitter.com/docs/api/1.1/get/direct_messages. The query result is a set of direct messages with accompanying data about the sender. Each direct message received is transferred to Social Media Server as a separate message and is submitted to Interaction Server as a separate interaction.