Skip to content

Docs for Qlik and MicroStrategy #68

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

Merged
merged 3 commits into from
Dec 4, 2018
Merged

Docs for Qlik and MicroStrategy #68

merged 3 commits into from
Dec 4, 2018

Conversation

bpintea
Copy link
Collaborator

@bpintea bpintea commented Nov 22, 2018

This PR adds the config steps to use ODBC with Qlik Sense Desktop and MicroStrategy Destkop applications.

Copy link
Contributor

@debadair debadair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can add some more detailed comments later if they're helpful.

[testenv="platinum"]
[[sql-odbc-applications-microstrat]]
=== MicroStrategy Desktop

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anchor and heading need to be updated to Qlik:

sql-odbc-applications-qlik
Qlik Sense Desktop

[testenv="platinum"]
[[sql-odbc-applications-microstrat]]
=== MicroStrategy Desktop

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few general comments:

I would strongly advise minimizing the use of screen captures. Keeping screen caps up to date is time consuming, keeping things up to date for third party applications that change without notice is especially challenging. Step-by-step procedures can also be problematic, but in this case there's not much way around it.

Stick to present tense instead of future tense. Just tell the reader what to do, not what they will need to do. :-)

In general, we follow the Google UX writing guidelines for talking about UI elements: https://developers.google.com/style/ui-elements.

==== Data loading

Once the application is launched, you'll first need to create a _New Dossier_:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd replace this with an intro that sets the context--something like: "To use the Elasticsearch ODBC driver to load data into MicroStrategy:"

image:images/apps_microstrat_newdossier.png[]

To import into the _New Dossier_ just opened, press on the _New Data_ button in the _DATASETS_ column:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of using headings for the images, I'd turn these into numbered steps. The description of the step should follow the step text, rather than precede it:

. Create a Dossier.

. Click New Data in the DATASETS column to import data into the dossier. This opens a dialog where you can select a data source.

. Click the _Databases_icon to select the data source.

And so on...

- fix anchor and heading for Qlik page
- switched steps to numbered lists
- few rephrasings
@bpintea
Copy link
Collaborator Author

bpintea commented Nov 27, 2018

Thanks for the suggestions and needed fixes. Hopefully addressed with last commit.

@bpintea bpintea mentioned this pull request Nov 28, 2018
Closed
@bpintea
Copy link
Collaborator Author

bpintea commented Dec 4, 2018

as agreed with @debadair, will merge now and open issues later if need be.

@bpintea bpintea merged commit 24fc600 into elastic:master Dec 4, 2018
@bpintea bpintea deleted the feature/docs_qlik_mcrostrat branch December 4, 2018 17:54
bpintea added a commit that referenced this pull request Dec 4, 2018
* add MicroStrategy Desktop to list of applications

* add Qlik Sense Desktop to the list of applications

* various fixes, formatting and content

- fix anchor and heading for Qlik page
- switched steps to numbered lists
- few rephrasings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants