8
edits
Changes
Jump to navigation
Jump to search
Line 29:
Line 29: + +
Lessons learned - OneGC Alexa Proof-of-Concept (view source)
Revision as of 09:49, 11 July 2018
, 09:49, 11 July 2018→Parks fees
** Transforming the data into a state in which it could be imported into DynamoDB was a lot of effort due to the dataset being designed for a relational database system and the poor documentation of DynamoDB.
** Transforming the data into a state in which it could be imported into DynamoDB was a lot of effort due to the dataset being designed for a relational database system and the poor documentation of DynamoDB.
** Querying data from DynamoDB is case-sensitive, but Alexa lower-cases everything. We had to duplicate the 'park name' attribute to have properly-cased and lower-case instances so that we could both search it and display it.
** Querying data from DynamoDB is case-sensitive, but Alexa lower-cases everything. We had to duplicate the 'park name' attribute to have properly-cased and lower-case instances so that we could both search it and display it.
** The Alexa service can't handle park names containing non-English names or words.
* What to do next time
* What to do next time
** 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.
== Flash briefing ==
== Flash briefing ==
