The Toucan Vocabulary¶
Do you speak Toucan?¶
Find here our most used terms, words from the Toucan Toco’s world.
Missing something? Let us know!
You instance is like your library of application. It’s your own app-store.
To access your instance, you should type in something like this in your browser : mycompanyname.toucantoco.com
Your instance gathers all the small apps of your organization. Depending to the status of your users, they might see them all, or only a few - you decide !
Your small-app is where you tell your stories. It’s your own book.
I create a Retail Monitoring small-app to manage my department stores over multiple regions.
This is the landing page of your small app. The cover of your book. The introduction of your story. You tell your users what you’re going to share with them.
Right away I see evolution of my major KPIs, footfall, net margin, and latest store advertising
Right away I see the total trips made, total distance made, % of car usage. Then ranking of vehicules, in distance and consumption. Finally, maintenance main informations
This is the point of view of your story.Your navigation scenario.
To whom are you telling your story? Views adapt the story to your users. If you have several Views inside your app, your users can select one of them directly on the home or in the stories.
I want to share a global overview, a focus by region, by managers, and by stores of my activity.
I want to share a global overview and a focus on brand of my car usage.
What is the message I want to share?
A story is a chart plus some context elements (commentary, recommendations, sources…).
Reading a story, I should be able to answer a clear established business need. As concepteur, we are familiar with what we’re doing, so things appear easy. It may not be the case for your users. Teach them, take them by the hand, and make them comfortable reading complex information.
How is my revenue evolving over the last 12 rolling months? Wich of my regions is performing the best? Where can I filter by category of product?
What is overall distance made? What are my upcoming maintenances? Where can I change current to year to date data?
How do I want to share the information?
You’ll define here what viz you’d like to use to tell the story.
These are the required parameters for the viz/chart you chose. The chart won’t show-up if you don’t set them up.
You can also customize the chart you choose with many options. Like order, additional values, color coding…
See the Reference section for a complete overview of each chart options.
These are your raw data. The data you receive that would be the base of your small-app.
See datasources as “untouched” data. Datasources are coming directly from the organisation, you haven’t done anything on it yet to fit your needs in the small-app.
Thinks of it as the original version of your data. Well, the source :)
Datasets are the results of the prepare dataset operation.
You take the datasources, you do some cool stuff (like merging them, aggregate them, calculate new fields, etc…), and they become datasets available in the small-app.
Queries are specific requests you make on a dataset to fit exactly your story.
A query is a custom view of the datasets, based on the information your showing and user selection (view and filters).
It’s your datasets with specific adjustment to fit exactly one story in particular.
All images, pdf and other custom visual elements of your small-app.
They are used to customized your small-app.
This is the version of the small-app the end-user will see.
This the live version of your small-app.
This is where a contributor can create content (tiles or stories) for the app.
It’s like a sandbox version of the application.
Some stories or tiles created there, can be unavailable to your end-users. You can work in peace.