Organization of community Data Explorer queries

We don’t seem to have a live library of Data Explorer queries here on meta.discourse.org at the moment. Would this be worthwhile addressing?

The topic referred to here is unstructured and has been closed as it was a mess:

@SidV has set up a great collection in GitHub:
discourse-data-explorer/querys.md at queries · SidVal/discourse-data-explorer · GitHub

Is the time right for a community managed library here on Meta? I think that many would find it useful.

10개의 좋아요

Yes, that topic got so many questions and responses that it became unreadable.

I think so. Does anyone have ideas about the best way to organize Data Explorer queries on this site? Ideally it would be possible to find existing queries by searching for a few keywords.

6개의 좋아요

A few thoughts:

  1. We could have a separate category with one query per topic. Could require approval from staff for new topics as to avoid clutter.
  2. Could simply have a data-explorer-query tag for individual topics. These topics could reside at #howto:tips-and-tricks
10개의 좋아요

Thanks for having me present :relaxed:

I’m open to changing the classification of the queries list on GitHub, maybe if we all think about a classification there, we can after debugging the categories well, go to something here in Meta (?).

Feel free to submit a PR

5개의 좋아요

각 쿼리를 PR하거나 포크하는 등 다양한 작업을 할 수 있다는 사실을 몰랐습니다. 꽤 멋진 기능이고, 그렇게 한 이유를 이해할 수 있습니다. 하지만 기술에 익숙하지 않은 사람들에게는 혼란을 줄 수 있는 곳입니다. 모든 Discourse 관리자는 Discourse에 익숙하지만, GitHub에 익숙한 사람은 일부에 불과합니다.

'분류(classification)'가 정확히 무엇을 의미하나요? 그 부분에는 태그가 잘 작동할 것 같습니다.

#customization:plugin의 전용 하위 카테고리(sub-category)가 가장 적절하다고 생각합니다.

  1. 쿼리당 하나의 주제 방식을 채택한다면, 주제가 매우 많이 생길 것입니다. @SidV만 70개 이상의 쿼리를 가지고 있고, 외부에는 훨씬 더 많은 쿼리가 존재합니다. 이는 #howto:tips-and-tricks 카테고리를 심각하게 오염시키거나 과부하를 걸게 될 것입니다!
  2. 모든 주제를 위키(Wiki)로 만들고, 첫 번째 게시물로 이동하도록 설정하며, 템플릿으로 권장 구조를 가질 수 있게 해줍니다.
  3. 또한 Customization > Plugin 카테고리의 구성을 그대로 반영할 수 있어 매우 좋습니다!
2개의 좋아요

I propose moving all the helpful and efficient queries to one topic and closing it afterward.

This topic would be “the source of truth” for vetted queries.

We can then be a bit strict about the structure of entries that get added to that topic. Each entry would have a heading that describes it, a short blurb about what it does, and a mention to credit the author.

Once we do that, we can add a table of contents to that topic, and it would have a heading for each query.

To address Simon’s concern here.

The new version of the ToC component will have a real-time, in-post search bar that searches in the heading and the content of each section and looks like this.

(ignore the styles, for now, it’s still a WIP)

The new version will probably be production-ready around the end of the year.

As for the process of sharing/suggesting/requesting new queries, we can create a new topic for that. Good queries shared on that topic would then be added to the “the source of truth” topic that has the ToC.

7개의 좋아요

더 나은 기업 활동은 데이터 탐색기에서 쿼리를 번들링하는 프로세스를 구축하는 것이라고 생각합니다.

예를 들어, 후보 쿼리를 포함하여 Contribute > Feature 태그와 함께 data-explorer #candidate-query를 생성할 수 있습니다. 이 기능은 왜 해당 쿼리가 번들링되어야 하는지, 그리고 그것이 어떻게 독특하고 중요한지를 설명합니다.

그 다음 제안이 유효한지 결정하고, 쿼리를 번들링한 후 이슈를 닫습니다.

원한다면 언제든지 거부된 번들링 요청을 탐색할 수 있습니다.

8개의 좋아요

Expanding the queries natively available in Data Explorer would certainly be very helpful and accessible for a lot of admins/users.

However, I believe there also exists a need for ‘second tier’ queries, and a structured place to discuss them. I come to meta looking for a solution to a problem I have, not to donate clever queries per se.

Perhaps @sam’s and @Johani’s approaches could be combined? A subcategory with some topics/queries tagged as ‘official’ which are bundled with the plugin.

1개의 좋아요

Small update on this one - we now have a #data-reporting category. :tada: :slight_smile:

I’ll have a read back through the suggestions in this topic and see if there are other ideas I can steal. :slight_smile:

5개의 좋아요

Conversation continued in Could we re-open the topic to share Explorer queries?