Qlik Community

Community Corner

Discussion board for questions about the Qlik Community, its features, sharing information, general discussions and even some fun. This is for both new and longtime community members. Everyone is welcome!

Highlighted
MVP & Luminary
MVP & Luminary

Further thoughts on Qlik Community Guidelines

It's good to see that there are now some published Usage Guidelines for Qlik Community , thank you Sara Leslie for adding these to the site.  I had been thinking this was something that was required and drafted my thoughts on what should go into some guidelines.  Some of these items have been addressed in the official guidelines, others have not.  I would welcome the thoughts of others as to whether any of these should be incorporated into the official site guidelines.

1. Please search for answers before asking your question, some common questions have been asked (and answered) many times already.

2. Please mark answers as correct or helpful when they are either of these things - this helps other users find answers to their questions and assists those looking to give advice to find where their input can be useful.

3. Do not post the same question into many groups - pick the one that is most appropriate.  This reduces duplication of threads and means that thoughts on resolutions to issues are all in one place.

4. Please use the Community to increase your knowledge to solve your own problems - you should however not expect other contributors to necessarily provide fully working applications in response to your queries.  No one has a specific duty to do your job for you!

5. Posts that simply state that you agree with another contributor add little to a thread and can often simply add clutter.  If you think a response is a good one please use the Like button to acknowledge this - future readers can then see that a much Liked response may be worth extra consideration.

6. Do not upload other peoples work without proper attribution - or better still post a link to the other material so that it can be viewed in context.  Under no circumstances post copyrighted material to the Community.

7. Be careful when uploading data to the Community - an example of an issue can be helpful but please ensure you are not sharing sensitive information.

8. Get involved and enjoy!  Qlik Community is a great resource and you will get out of it what you put in.

Those are just my thoughts, I'm sure others in the Community will have their own thoughts.  Feel free to share your comments below.

Steve

30 Replies
mov
Esteemed Contributor III

Re: Further thoughts on Qlik Community Guidelines

7b.  Please reduce your applications before uploading!
(Speaking for myself - I'm not downloading any MB-sized applications)

Re: Further thoughts on Qlik Community Guidelines

7c. Switch off Section Access before uploading! Threads tend to get bulky when visitors that are eager to solve a problem (and earn some points) discover an inaccessible upload.

Re: Further thoughts on Qlik Community Guidelines

5b. Read the entire thread before replying to a question. Someone may have posted the same solution before you.

Not applicable

Re: Further thoughts on Qlik Community Guidelines

Steve,

Completely agree with all your remarks.

I would say

1b

1 thread = 1 question (not 5, not 10)

1 question answered = 1 closed theread (if another question, another thread)

1c

read the docs that other people recommend you to read to get your question answered

(many times, I see people that ask new questions wihout reading the appropriate docs that were recommended)

Fabrice

Not applicable

Re: Further thoughts on Qlik Community Guidelines

For myslef:

7d Upload script also into text files (qvw and txt): some people (like me) have Personal Edition. the community is a perfect place where I learn much. And I am often frustrated by solutions that I cannot open ...

Fabrice

puttemans
Valued Contributor

Re: Further thoughts on Qlik Community Guidelines

In addition to it, I'd make a strong claim to think not once, twice or 3x over your title for the question, but 10x. Things like 'urgent help needed' are actually helping no-one, and make the reader lose time if he/she finds out the topic is not in his/her area of knowledge. Try to define the topic as specific as possible, which will make you get an answer much faster, and, referring to number 1 in the list, will help someone searching as well.

MVP & Luminary
MVP & Luminary

Re: Further thoughts on Qlik Community Guidelines

Hi Aunez - yes!  Too often I will respond with a solution and someone will reply, "great, that's answered my original question - but what I really want to do is...".  The thread then remains open and gets confusing very quickly.

MVP & Luminary
MVP & Luminary

Re: Further thoughts on Qlik Community Guidelines

Hi Johan.  I now tend to ignore the threads with URGENT!!!! in the title - as those tend to be the ones that you get little thanks for your efforts with.

mov
Esteemed Contributor III

Re: Further thoughts on Qlik Community Guidelines

When I see "urgent", I think that the person should call QT Support, or better hire someone to help...