컬렉션

[Alteras (Steven Chang)]

	요약	사용자가 연결된 주제(Topic)의 컬렉션을 생성할 수 있습니다
	저장소 링크	https://github.com/Alteras1/discourse-collections
	설치 가이드	Discourse에서 플러그인 설치 방법

미리보기

모바일

컬렉션

이 플러그인은 사용자가 연결된 주제를 볼 때 해당 주제들이 포함된 컬렉션을 생성하고 표시할 수 있게 해줍니다. 컬렉션에는 어떤 URL이든 포함될 수 있으며, 연결된 모든 주제에서 표시됩니다. 컬렉션은 섹션으로 조직화할 수 있으며, 컬렉션에 대한 모든 변경 사항은 연결된 모든 주제에 반영됩니다. 연결할 주제를 제한하지 않으므로, 사용자는 카테고리/태그를 넘나들며 컬렉션을 생성할 수 있습니다.

제목 및 설명

입력이 가능한 선택 사항입니다. 제공된 경우, 목록 상단에 표시됩니다.

섹션

선택적인 조직 기능입니다. 섹션 헤더를 추가하면 컬렉션을 섹션으로 나눌 수 있으며, 접을 수 있는 섹션이 표시됩니다.

서브컬렉션

사용자는 단일 주제에서만 표시되는 서브컬렉션을 생성할 수도 있습니다. 이를 통해 사용자는 관련 URL(예: 특정 게시물/외부 리소스)을 단일 주제에 대해서만 연결할 수 있습니다. 추가된 주제 URL은 연결되지 않습니다.

권한

이 플러그인은 사용자가 자신의 주제에 대한 컬렉션을 생성할 수 있도록 허용합니다. 기본적으로 사용자는 자신의 주제에만 연결할 수 있으며, 다른 사용자를 유지관리자(maintainer)로 추가해야만 해당 사용자가 자신의 주제를 컬렉션에 추가할 수 있습니다. 이 설정을 비활성화하면, 특정 그룹(기본값: Staff & TL4)만 모든 컬렉션에 대한 전체 제어 권한을 가질 수 있습니다.

권한 데모

설정

이름	설명
collections enabled	플러그인 활성화/비활성화. 기본값: true
collection by topic owner	주제 게시자(OP)가 컬렉션을 생성할 수 있도록 허용. 기본값: true
collection by topic owner allow groups	컬렉션을 생성할 수 있는 주제 게시자(OP) 제한. collection by topic owner를 제한합니다. 기본값: TL1
subcollection by topic owner allow groups	서브컬렉션을 생성할 수 있는 주제 게시자(OP) 제한. collection by topic owner를 제한합니다. 기본값: TL1
collection modification by allowed groups	모든 컬렉션의 생성/수정이 허용되는 그룹. 기본값: Admin Moderators TL4.
sections in subcollection	서브컬렉션에서 섹션 헤더 사용 허용. 기본값: true

---

대안

이 플러그인은 Discourse Doc Categories 플러그인에 깊은 영감을 받아(한때 이를 기반으로 하여) 개발되었습니다. Doc Categories 플러그인은 좋은 인덱싱 메커니즘과 훌륭한 표시 방식을 제공하지만, 모든 것이 단일 카테고리에 정리되는 위키 스타일 페이지를 위한 설계였습니다. 마찬가지로, 인덱싱은 별도의 주제에 포맷된 텍스트를 입력하는 데 의존하며, 이는 각각 장단점이 있습니다.

DiscoTOC - automatic table of contents 테마 컴포넌트도 게시물 본문 밖에서 링크를 조직화할 수 있게 하지만, 단일 주제에 제한됩니다.

목적이 단순히 위키 스타일 조직이라면, https://meta.discourse.org/t/discourse-doc-categories/322376이 더 적합할 것입니다. 일부 페이지에만 연결된 주제가 필요할 경우, https://meta.discourse.org/t/discotoc-automatic-table-of-contents/111143이 더 좋습니다.

참고 사항

이것은 제가 소속된 포럼이 Discourse로 마이그레이션하는 것을 지원하기 위해 처음 설계되었습니다. 글쓰기에 초점을 맞춘 포럼인 만큼, 사용자는 다양한 목적으로 별도의 주제를 유지 관리하고 있어, 카테고리 간 주제 링크가 사실상 필수적인 상황이 되었습니다. 이를 돕기 위해, 사용자가 스스로 조직화할 수 있도록 이 플러그인을 만들었습니다.

이것이 플러그인이 아니라 테마 컴포넌트인 또 다른 타임라인이 있습니다. 이 경우, 사용자가 다른 게시물로 가는 URL을 포함하는 div를 입력하여 인덱싱이 이루어집니다. 하지만 도구의 90%를 개발한 후, 이렇게 하는 것이 가치가 없으며 사용자가 작성된 모든 튜토리얼을 건너뛰고 여전히 작동하지 않는 것에 대해 불평할 가능성이 높다는 것을 깨달았습니다. 그래서 그 경로는 포기했습니다. 솔직히 나쁜 해결책은 아니며, 플러그인보다 훨씬 가볍지만, 사용자가 게시물 하나뿐 아니라 여러 게시물에 대해 올바른 포맷을 유지하도록 하는 데 불필요한 부담을 주었을 것입니다.

현재 UI 기능(예: 아이콘)과 권한 시스템에 대해 100% 확신이 서지 않아 #experimental로 표시해 두었습니다. 또한 자동화 단위 테스트를 추가해야 합니다.

[Jagster (Jakke Flemming)]

FYI: all videos were broken (iPad)

[Alteras (Steven Chang)]

Huh, I thought iOS Safari supported WebM…

I’ve swapped out the videos for MP4. Ty!

[satonotdead]

It’s possible to enable 'public‘ collections like on Discourse Docs?

[Alteras (Steven Chang)]

Sorry if it wasn’t clear, all collections are “public.” All users will see the same collection on the same topic. This plugin is meant to organize topics, not be a kind of private “folder of bookmarks” for users.

[Alteras (Steven Chang)]

Updated the plugin with support for Emojis and Color Squares in sidebar!

https://github.com/Alteras1/discourse-collections/pull/17

[nathank (Nathan Kershaw)]

정말 매우 인상적입니다. 그리고 문서화도 훌륭하네요! meta.discourse.org에서 문서화가 가장 잘 된 #customization:플러그인으로 이 플러그인을 추천합니다!!

토픽 목록까지 포함하도록 확장하는 것을 고려해 보셨나요?

카테고리별 또는 태그별 링크 모음이 있다면 매우 유용할 것 같습니다. 예를 들어, 특정 그룹을 위한 비공개 카테고리가 있고, 여기에 다른 도구들(예: Google Docs의 몇 가지 폴더, 지방 정부 포털, 관련 채팅 채널, 그룹 공용 메일함 등)이 함께 사용되는 경우가 있습니다. 이 경우 카테고리 관리자가 이를 제어할 수 있다면 이상적일 것입니다.

[Alteras (Steven Chang)]

Thank you very much!

It’s definitely something I’ve considered before, but I don’t think it would fit well with the current design of being a user driven way to organize topics. Not ideal for category/tag level, as it would have to be limited to moderator control. The original use case was to cover linking related topics too big for 1-2 topics, but too small for a tag/category.

Making topic lists display the indexing in the sidebar for categories can be done via Discourse Doc Categories plugin, albeit with a different configuration method. Definitely a hassle having to have two plugins do two very similar things, but I think the original philosophy for each is different enough to warrant the separate approaches.

Adding a compat extension for the Private Topics Plugin is a very cool idea from a user standpoint. I’ll have to consider that…

That just leaves the per-tag level. Making a PR for Discourse Doc Categories (or making a new plugin/TC) for tags is an option tho, but not actively on my mind. Perhaps in the future.

[nathank (Nathan Kershaw)]

@Alteras

Making topic lists display the indexing in the sidebar for categories can be done via Discourse Doc Categories plugin,

Actually, this would probably work nicely for my use-case. I’m not sure if it is adaptable enough for it though (will play around with it later this week).

@Alteras

Adding a compat extension for the Private Topics Plugin is a very cool idea from a user standpoint. I’ll have to consider that…

Sounds very interesting. What use case do you have in mind?

[Alteras (Steven Chang)]

@nathank

What use case do you have in mind?

To regular users, the category with Private Topics enabled would only display their own topics. So I could see this being one of the few places where letting the Collections plugin hoist a collection from the topics level to the category level per user makes sense.

The forum I’m part of actually has a private category for users to use as a personal drafting/testing ground. And they make alot of topics, so user driven topic organization sometimes happen here.

[Hyteller]

I was really hoping it’s a system of collection where users can create categories and put there topics of their choice, like a gallery. Oh well.

[denvergeeks]

How is this not that?

[Heliosurge (Dan DeMontmorency)]

You can’t create categories is my guess.

[denvergeeks]

I really appreciate this Plugin’s drag-and-drop UI for creating arbitrary sequences of Topics like chapters of a book, which can be easily re-arranged.

I’ve initiated a Theme Component to add sequential navigation for Collections such as < Previous and Next > and Paging in a Modal …

Here is my working repository

https://github.com/denvergeeks/discourse-collections-navigator

[jordanjay29]

Much needed, looking into this today and this was the last component it seemed to need.

@Alteras I’m having a bug with the modal close X on the Create Collections modal. It can be hovered and clicked but does not close the modal until a page refresh.

[Alteras (Steven Chang)]

@denvergeeks

Theme Component to add sequential navigation for Collections

Oooo, this is a nice concept. I love the modal for quick viewing the different linked topic posts. Also helps inform users that there is a collection for those who don’t have/keep the sidebar open 24/7.

I’m curious about the decision to swap the contents of the post instead of just redirecting to the user to the topic.

I really like the idea of using < Prev and Next > above the timeline to navigate across topics without needing the sidebar. Maybe it could be with the timeline like the toc, so that it can be easily accessed on long 1st post topics without having to scroll back up… Or maybe just decorate the top/bottom post itself…

If you’re okay with it, I’d like to explore adding some of those ideas directly into the plugin, maybe with extra site settings for admins. Of course I have no objection to having a TC built off of the plugin, more customization to the users. Let me know if you need any help with your TC. You should be able to pull the currently displayed collection information from the ember service service:collection-sidebar without having to parse the DOM.

@jordanjay29

bug with the modal close X on the Create Collections modal

Hmm… that’s truly odd. I can’t seem to replicate it. I recently made some changes updating the plugin to address some deprecation issues, so that might have affected it? Please check if the plugin is updated. Please also share the details of your setup (browser, mobile/desktop, discourse version).

[jordanjay29]

@Alteras

I recently made some changes updating the plugin to address some deprecation issues, so that might have affected it?

I’m outdated, maybe that’s why. I was still on the Nov 6 commit.
ETA: Disregard, updating solved.

[denvergeeks]

@Alteras

I’m curious about the decision to swap the contents of the post instead of just redirecting to the user to the topic.

I like the quickness. Not a reasoned design. My initial vision is that the modal pops up a content-focused slideshow.

@Alteras

I really like the idea of using < Prev and Next > above the timeline to navigate across topics

Since arbitrary ordering of items is the opportunity here, where sequencing is decidedly not tethered to any timeline, my initial aim is to reuse the nested horizontally scrolling menu behaviors from core as we have in the display of User Profiles, e.g. where, beneath the (stationary) Collection Title and Description (if/when present), are two horizontally scrollable/swipeable rows – Section Headers and their associated Topic Titles below those.

Also within the modal is a collapsible (quick slide in/out from left) vertical display replicating the behavior of the left sidebar outside of the modal. I like the idea that what rises up off the page in the modal looks and feels mostly the same as what is seen and experienced (in the centered, non-modal view), including navigation elements, but just surrounding the cooked content.

I’m working also toward re-purposing your provided Subcollections to also display in a modal – iframes in a slider – which can display sequences of external links, and can also re-use internal content (since currently a Topic can only be used in one Collection.)

@Alteras

If you’re okay with it, I’d like to explore adding some of those ideas directly into the plugin, maybe with extra site settings for admins.

Please, Go For It !

I can also see adapting this TC, or otherwise providing these types of navs and displays for Doc Categories

[jordanjay29]

Now that I have it working (thanks for the head’s up on the update above), a couple things that I found:

1. Collections button is visible even when the user is not part of the allowed groups. Results in an Internal Server Error (displayed gracefully in a red bar on the modal) when attempting to create a collection.
2. On the collections sidebar, the button at the bottom offers the original Create Collection option. Have to use the button on the original post in order to manage it, it would be very useful to have a Manage option immediately from the button on the collection sidebar.
3. Would it be possible to separate Collection and Subcollection permissions? Subcollections could be immensely useful for individuals who would like to collate topics on their own, without the widespread impact a Collection has on all linked topics.

Lastly, how does this plugin handle two collections linking the same topic? Two subcollections? This makes me lean more into suggestion #3 for easier management of overlapping goals for users who like the collections feature.

EDIT: I realized #1 is an error related to Collection modification by allowed groups that allows non-owned topics. Still, a better error message could be useful!

[Alteras (Steven Chang)]

@jordanjay29

• Collections button is visible even when the user is not part of the allowed groups. Results in an Internal Server Error (displayed gracefully in a red bar on the modal) when attempting to create a collection.
• On the collections sidebar, the button at the bottom offers the original Create Collection option. Have to use the button on the original post in order to manage it, it would be very useful to have a Manage option immediately from the button on the collection sidebar.

@jordanjay29

Collection modification by allowed groups that allows non-owned topics.

So the setting collection modification by allowed groups is meant for staff and users who are highly privileged, i.e. helpers maintaining wikis. Though it seems like I’ll need to fix the errors.

@jordanjay29

Would it be possible to separate Collection and Subcollection permissions? Subcollections could be immensely useful for individuals who would like to collate topics on their own, without the widespread impact a Collection has on all linked topics.

As long as collection modification by allowed groups is set properly high enough, collection and subcollections should only be created/modified by the topic owner (and staff). Topic owners should be able add ordinary users as maintainers to collections or subcollections, who can then add their own topics. I’m not quite sure of what your settings are to warrant separating them.

@jordanjay29

Lastly, how does this plugin handle two collections linking the same topic? Two subcollections?

Two collections cannot link to the same topic. An error should be displayed when attempt to link a topic already in a collection. Similarly, only one subcollection is allowed per topic. This is because the collection are all public and should only be made by topic owners.

---

Hmmm… I get the feeling that it might be better to make a separate plugin that’s just folders of bookmarks that can be viewed publicly or privately… “Personal Collections?” “Bookmark Library?” “Topic Playlists?” Or maybe I just extend this one. But the underlying code and philosophy would be quite different between the two features… It’s a bit unfortunate the name “Collections” is quite broad and can be interpreted in quite a number of ways.