Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create custom type for shows #9

Open
habuma opened this issue Aug 5, 2019 · 0 comments
Open

Create custom type for shows #9

habuma opened this issue Aug 5, 2019 · 0 comments

Comments

@habuma
Copy link
Collaborator

habuma commented Aug 5, 2019

The original implementation of this skill liberally used AMAZON.LITERAL for all slot types. This worked fine, but when I had to adapt to changes in the backend show JSON, I was unable to deploy the skill because AMAZON.LITERAL is deprecated.

For simplicity's sake, I changed the slots to AMAZON.SearchQuery, which is roughly equivalent to AMAZON.LITERAL, but a wiser move would be to create a custom entity type for shows. In it's simplest form, the type could be hard-coded with an entry to represent all NFJS events (e.g., "Northern Virginia Software Symposium", "Lone Star Software Symposium", "Progressive Web Experience") as well as synonyms for each of those (e.g., "Reston", "Dallas", "Clearwater").

That would work until a new NFJS event is created. Suppose that we decide to do an Australian tour, there would be no entries for Sydney, Melbourne, etc, so the interaction model would need to be updated to include the new events and the skill republished. Instead, it might be wiser still to create a custom type for shows, but make it a dynamic entity (see https://developer.amazon.com/docs/custom-skills/use-dynamic-entities-for-customized-interactions.html) which is populated from actual show data. Then it would be flexible enough to support any new shows that are introduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant