3
edits
Changes
Lessons learned - OneGC Alexa Proof-of-Concept (view source)
Revision as of 14:07, 1 August 2018
, 14:07, 1 August 2018→Structuring data
== Structuring data==
== Structuring data==
* Works better with well-formed, well-described data
* Works better with well-formed, well-described data
* The data set should not contain HTML tags
* The data set should not contain HTML tags or any other artifacts
* The data set should consistently label data used for set purposes (e.g. description field should hold a description)
* The data set should consistently label data used for set purposes (e.g. description field should hold a description)
* Fields with similar names need to be renamed (e.g. type1, type2, type3 => adultRate, childRate, seniorRate)
* RSS feeds used in Flash Breifings need to comply with Alexa's minimum requirements
* Descriptive data sets such as food and car recalls need to be summariezed in plain English with simple words.
* Descriptive data sets such as food and car recalls need to follow the 1 breath design guidance. If it takes more than 1 breath to read the sentence, it means that the sentence need to be further broken down.
* A natural conversation flow need to happen between Alexa and the user. One need to design the dialog in a way that lets the user drive the conversation by letting him/her know that they can say "tell me more" or followup with a question such as "what are the side-effects?".
* The Alexa service share only 1 information about the user with the developed Alexa Skills. And that is the User ID, a unique identifier. It is up to the developer/designer of the Alexa Skill to ask the user the right question at the right time such as "What is your name?", "What food allergies do you have?", "What is your car make, model and year?" and to store this information in DynamoDB for future use such as "Hello John!", "There are 5 food products that have been recalled.", "There is a new recall concerning your vehicle."
== Hello, world Skill ==
== Hello, world Skill ==