1
edit
Changes
Lessons learned - OneGC Alexa Proof-of-Concept (view source)
Revision as of 10:47, 27 July 2018
, 10:47, 27 July 2018no edit summary
** Using a relational database system would have been easier than using DynamoDB.
** Using a relational database system would have been easier than using DynamoDB.
* What needs to be fixed to make it better
* What needs to be fixed to make it better
** Improve Alexa service to recognise non-English words and names.
** Improve Alexa service to recognize non-English words and names.
== Health Canada Recalls and Safety Alerts ==
* What went well
** Integrating with the existing RSA API over HTTPS was seamless and worked as expected.
** After looking at examples from other collaborators and the web, creating the skill itself was relatively easy.
* What could have gone better
** The ability to index the RSA data with a search engine without a high associated cost would have been ideal.
** Having properly structured data would have freed up more time to further develop the skill, rather than massaging the data to work with Alexa during the development process.
* What to do next time
** Come prepared with restructured data that is more suited to generic use cases.
** Index data with search engine to provide more helpful results
* What needs to be fixed to make it better
** RSA Data needs to be restructured and reformatted so it can be more easily consumed by different use cases.
*** It is tied too tightly to the UI is was originally designed for. HTML content should be removed and added dynamically by the applications that consume it instead of existing that way in the database.
*** This has been an ongoing issue that has been further highlighted through this proof-of-concept.
** Having the ability to create dynamic slot types would be ideal since new data is constantly published.
** Amazon (AWS+Alexa) documentation is not the greatest and many tutorials are outdated and/or provided misleading information.
== Flash briefing ==
== Flash briefing ==