California Speaks update of 4/25

Team Name (tag this post with your team name as well): California Speaks

What we did the past week: Fully implemented the search function (“search for {term}”) in the skill, and have uploading of files reside on Amazon S3 (not any personal server).

Issues we had with gathering material (finding sources, verifying facts, interviews, etc.):

Issues we had with producing the content (writing, recording, editing, etc.): It looks like California Speaks won’t be updating for a while, so there won’t be new content in the near future.

Technical issues (with WordPress or Alexa, etc.): I struggled with running ffmpeg on AWS, it’s just running manually on my laptop for now.

Other questions we ran into:

What we are going to do this week. Things to improve. Who is doing what: Publish the skill, and respond to user feedback.

How we are going to test our skill this week: Go through the flow diagram and make sure each path works as expected.

Help we need:

Team California Speaks update 2018-04-11

What we did the past week:
I spent the past week learning about how Amazon Web Services works, and modifying the existing skill code to store all of the files on AWS. It should theoretically work using the AWS Lambda interface that Alexa recommends but I don’t think it actually does yet.
Technical issues (with WordPress or Alexa, etc.):
A lot of the AWS documentation seems outdated. But I got it mostly working with trial and error.
Other questions we ran into:
How much money are people willing to pay to make this work? It seems like we will pass the free limits eventually.
What we are going to do this week. Things to improve. Who is doing what:
I’m going to make sure the basic functionality works, and the downloading and encoding process fully works on AWS. If there’s time afterwards I’m going to implement the “search” functionality.