ich hatte früher eine Idee… ja, ja, ich weiß, denk nicht dran, oder?
Mir ist nämlich aufgefallen, dass viele unserer kreativen Nutzer oft Dinge posten, an denen sie arbeiten, und das über eine Vielzahl von Themen hinweg und für unterschiedliche Kurse in unserem Fall. Ich habe mich gefragt, ob sie vielleicht eine Art Portfolio-Funktion schätzen würden.
Meine Überlegung war: Ein Nutzer erstellt ein Thema und fügt dann Screenshots, Videoclips, Codebeispiele oder was auch immer hinzu. Anschließend könnte er zu seinem Thema zurückkehren und von Zeit zu Zeit eine Antwort mit etwas Neuem hinzufügen.
Etwas verwässern könnte das Ganze, wenn auch andere Nutzer antworten dürften. Anstatt eines laufenden Portfolios an Arbeiten könnte es dann zu einem Durcheinander an Gesprächen in der Mitte kommen, was vielleicht besser in den bestehenden Themen untergebracht wäre, um das Portfolio sauber zu halten.
Meine Frage also: Ist es derzeit möglich, Berechtigungen so zu erstellen, dass nur der Autor eines Themas (mit Ausnahme von Admin-Mitarbeitern) darauf antworten darf? Ich habe gesehen, dass es Erstellen / Antworten / Anzeigen, Antworten / Anzeigen und nur Anzeigen Berechtigungen gibt, und dass diese Berechtigungen verschiedenen Gruppen hinzugefügt werden können. Ich bin mir nicht sicher, ob es eine Kombination gibt, die das oben Genannte ermöglicht?
Vielen Dank im Voraus für jegliche Hilfe oder Gedanken.
Perhaps the easiest would be for members to send a message to themselves. This would be equivalent to them having their own personal topic that others could not access unless invited into it.
So, they create a topic that everyone can see, but they are the only ones who can reply to it. I appreciate that they could just edit their original topic rather than replying to it, but I don’t expect a vast amount of our users would do that, equally, it may be beneficial to have the timestamp that comes with a reply against each update that they make to their portfolio.
You’d need to set up a whole category for this to wrap permissions around it.
That would have been the plan, e.g. have a category for them to post their portfolio topics in, but from what I can see, there isn’t then a way to then restrict the replies to only the author of a topic in that category.
Why can’t you simply ask people not to post in the topic, if you don’t want anyone else to post in it? I’m a little unclear why “just put a notice on it” isn’t sufficient?
The author could flag any post they don’t want in their topic.
Yeah, I guess we could do that, there is the “About the xxxxxx category” topics where I suppose this message could go, and it could be pinned… I just have a feeling that as soon as people start seeing other people’s work it would be “Hey man, that’s really cool”…
I do understand the point of Discourse is one of conversation and what I was thinking of above kinda goes against that.
Not to worry, just wondered if it was possible with the current permissions etc.
I’m not sure how well that would work for us in practical terms though. It would mean having to have an entire category for a portfolio/user, as opposed to just a topic, which means if we had sat a thousand people that wanted to do that we’d have a parent category with then a thousand sub-categories. I suspect this would then introduce some UX issues too as unless the users name was near the beginning of the alphabet they would potentially be doing a lot of scrolling, as would anyone else just passing through that wanted to look at someone else work.
There would be perhaps more overhead on creating all of those sub-categories too, as well as the ongoing maintenance of them.
I think I had envisaged the solution being topics-in-a-category.
For the time being I’ve shelved the idea as I don’t think Discourse would be the most suitable solution, not because of any limitations of the product, more because of my seemingly off the wall demands
IIRC, there have been discussions about members having a type of “personal topic” page under their Profile. But AFAIK they never got anywhere.
Even then that might not be what you’re thinking of, if you’re thinking of displaying public “topics” that aren’t intended to be discussions in topic lists.
I was thinking in terms of a user having a portfolio, a topic (possibly several if they wanted to separate the subject matter of their work) which they could post to but to literally only show their work, as opposed to having the extra noise of comments that people may add as they see the posts and work.
The only way I could see that working would be to limit who could post on that topic to only the topic owner, and obviously mods/admin. This would prevent others from adding noise, but they could still like topics to show their appreciation of the work.
