Discuss
Topics
Hi guys, a question about the ability for a topic owner to be able to change the name of that topic. Is this ownership at all exchangable?
I am about to go on leave and want to allow my replacement the right to alter the name of the topics in our production forum. We are using this (changing the name) as a way of tagging a topic as 'asleep' or requiring no further input.
any comments on this one?
Actually for that matter this question (above) could be posed to an entire forum. What rights does the forum owner have, apart from asthetics and the name of the forum itself?
Heya general disaster.
About the topic editing - the person who starts the topic can also edit it, as can the forum creator.
The forum owner is able to delete any topic or message, not only their own. That's about it for now.
It sounds like you're looking for more resources, in which case, these might help:
I have already checked out these resources. Alot of stuff there, but more general info rather than specific stuff that would pertain to us.
Our user group is starting to take up Tangler as a business tool so as you can expect, the special requests, that would normally not be part of a casual forum start to come up.
The concept of transferability of ownership of a topic or entire forum is something that I think could open a lot of use case solutions within Tangler
You're more than welcome to raise those issues here. I was just pointing them out in case you hadn't seen them
I'm interesting to know how transferability would help. Could you give me a few examples?
Well if a popular forum needed to get more organised with administration, then the 'god' power can be shared or transfered between people for one example. I imagine that as you guys develop more and more stuff, there will be more and more stuff linked to the forum owner. So the ability to make the ownership transferable would open a wide door to solving unforseen 'painted in corners' that always inevitably arrise.
I imagine that at the moment the ownership is simply a flag in a database somewhere, but together with this I guess the non transferability is abit of a firewall. I am sure that you guys would have to tread carefully with such a thing.
Passing around 'god' rights should never be done lightly.
Am I just talking myself out of wanting this?? 
LOL!
Naaa, I do have a legit use case though
I imagine there'd be some system in the future where one could 'bestow' admin rights upon others, as opposed to transferring it.
I think this is a good idea. Let the forum owner have the privilege of assigning rights to users of their choice. Ultimately, the forum owner would have overall power, and could give and remove the rights as they seem fit, as well as administer changes that the secondary user may undertake.
Users with secondary rights would not have the same overall power, however this is something that would need further discussion.
the forum owner has not got the rights to change the name of a topic though, have they?
can they delete a topic out right?
Yeah, agreed Morgan.
Having options are always good. It's just a matter of *how* urgently needed they are
Yes on both counts gen d
options are the bane of developers
there is that multiplier factor - user wants 2 options - dev has to write in 8 of them.... and so on
Yeah, exactly...
i c you have run into this one already
Most certainly have
A workaround could be to create a Tangler account for the company and use that to create topics... not ideal I know, but like I say... a workaround.
It is a way to deal with it. We've done a similar thing for some of the beta testing forums we set up early on.
The traditional way to work such things is to have roles. Privileges are assigned to roles and accounts are assigned to roles. When a person leaves or is re-assigned they are removed from the role and another account takes their place.
Yeah, I get you drdec. That would be an elegant way to do it.
drdec, I have to say that my experience with forums and such is not so extensive. I am not quite sure of the exact working of such a system. Seems complicated to implement. On the up side, sounds like it would be quite flexible, but with every flexible system comes a steeper learning curve for newbies. When the curve is too steep, alot of starters fall by the way side. Less users means less revenue, means less pizza and less of everything else.
Well, the role concept really is not specific to forums, it can be used in any system where you have permissions and managed resources, etc. It is more complicated to create so for relatively unimportant* things like forums it is usually not done.
*Unimportant in the sense that is it not usually mission critical or exposing liability, etc. No offense to Tangler intended.
In that case then I understand completely. Especially when it comes to security focused systems, then a roles system with assignable privilages gives a huge amount of scope to fine tune the systems to work in may different scenarios.
The implementation and administration are not to be sneezed at though. Let alone the adjustment in the users to this system.
If this forum is to have a future in the use case that I use it for (professional group, business orientation) then there would have to be some improvement in the transferability of ownerships etc...
In fact there is a list of things that we are starting to get together that would make Tangler much better suited to our use case. This list is in preparation for a possible migration from Tangler to a company server based system where the forum truly becomes a closed system totally in our control.
Not that we are not happy with Tangler at the moment though. Tangler was an experiment to see if our team would benifit from this kind of a communication tool, and it seems to be working for us at the moment. Still early days though.
