A Conversation for Magrathea's Workshop - Permissions and User Roles
- 1
- 2
Magratheas Workshop - Permissions and User Roles - Documentation
Magrathea Started conversation Feb 20, 2011
This thread is to discuss the documents linked from the entry. Post info about spelling mistakes, typos, formatting etc here.
Thanks
Mrs Zen / a broad called Ben
Magratheas Workshop - Permissions and User Roles - Documentation
8584330 Posted Feb 21, 2011
1) I don't see a check in the un-hide row.
2) Are we addressing in this document how noonoohootoo would work with collaboratively written entries?
Magratheas Workshop - Permissions and User Roles - Documentation
Mrs Zen Posted Feb 21, 2011
1) Good catch, and thank you. The Creator and the Publisher have un-hide permissions by default, I guess. I'm not sure if the Sub / Co-Author should have un-hide. What do you think?
2) Yep. My thought was that the Creator should be able to assign co-author rights. In this case I would be able to assign co-author rights to any of the Magrathea's Workshop entries to relevant peeps because I created them, and they could go in *using their own account* and edit the entry.
Does that explain the thinking, HN?
Ben
Magratheas Workshop - Permissions and User Roles - Documentation
8584330 Posted Feb 21, 2011
>>> The Creator and the Publisher have un-hide permissions by default, I guess. I'm not sure if the Sub / Co-Author should have un-hide. What do you think?
thinking ... thinking ...
Suppose you're my co-author on an entry. I have hidden the entry from everyone but ourselves. Unfortunately I get arrested by Vogons for failure to improperly filling out a form. I suppose you can always ask one of the Curators to give you permission during my incarceration.
>>> 2) Yep. My thought was that the Creator should be able to assign co-author rights...
Very useful. I've been wanting something like that for a long time.
Magratheas Workshop - Permissions and User Roles - Documentation
Mrs Zen Posted Feb 21, 2011
Me too.
I want to pass ownership of content over to the creators much more than it is at present. Two reasons: one is that I think it will make it much easier to collaborate on stuff, and the other is it will take adminny pressure off the Editors, (I assume we'll have some sort of Editors in the Brave New World).
I really like the blogging model, where it's your party and you can cry if you want to - er - assign user rights to other people without asking WordPress for permission to do so.
Magratheas Workshop - Permissions and User Roles - Documentation
Milla, h2g2 Operations Posted Feb 23, 2011
Magratheas Workshop - Permissions and User Roles - Documentation
Vip Posted Feb 23, 2011
I'm struggling because I can't access the documents from work - firewalls block everything and anything. I suppose it's fair enough, but this is my lunchbreak... ah well.
I'll try to remember when I get home though.
Magratheas Workshop - Permissions and User Roles - Documentation
8584330 Posted Feb 23, 2011
>> pass ownership of content
Yes, indeed!
It would also mean that we'd have fewer dead clubs, causes, and groups in h2g2 when people move on.
As a newbie I remember looking through the Post's classified ads for clubs, and many of them had little to no activity. It made h2g2 seem unnecessarily sad and deserted. Even this club for chocolate. I mean, chocolate! It's isn't like has gone out of fashion.
There should be a graceful way for retiring leaders to hand over the admin duties for a group's page to the current leadership, just as there is in real life.
Magratheas Workshop - Permissions and User Roles - Documentation
Z Posted Feb 23, 2011
And going through the list of clubs and quitely, retiring (not deleting) those that are not active wouldn't do any harm.. but not trying to promote clubs with very few members.
Magratheas Workshop - Permissions and User Roles - Documentation
Vip Posted Feb 24, 2011
Hopefully I'm not repeating anyone above. I took copies of these documents last night so hopefully not a lot has changed since then.
I'm reading for layout as well as content, I hope that's OK.
Word document
Creating and Editing
Nobody at all can unhide a document as it stands. I assume that should be ticks for Creator and Publisher.
When you say assign rights, we may need to define exactly which rights
Need to make the cell wider on the row heading 'Categorise'
ie --> i.e.
Should the Creator be able to categorise their Entry, or should that be with the Publisher alone?
Promote and Publishing
Did we make a decision on whether anyone can put an article into a Review forum? At the moment that is a feature that never works; either a author waits for their entry to be picked by someone else or Entries are put in where authors have or don't want it to be reviewed. I'm happy to go with the majority on this, but I think we should leave that decision to the creator. After all, they will have to make the changes and do the work, or they can decide to assign creator rights over to someone else under this new system.
Craeating Entries
I would make sure that we can have multiple 'Written By' names, not just one, so that we can have true Collaborative Entries. I like having 'With help from' as it allows those who have contributed to be recognised without detracting from the person who did the work putting it all together and originated the idea.
I hope this helps,
Magratheas Workshop - Permissions and User Roles - Documentation
Vip Posted Feb 24, 2011
Excel document
If higher roles are additive, it needs to be defined which are higher than other. Does Sub contain all of Scout roles, I think is the one that needs to be defined clearly as at the moment Sub can't Scout. User Acccount Keeper may not be able to do things that the Editor can and vice-versa as well.
Set status on Entry - Editor. Surely the Editor changes the status to 'Approved' as well as 'Draft' (back to Entry, in case it proves not Guide-worthy in the end).
The Word document says that the creator can tag Entries. Let's give them an x rather than a ? in the Excel document so they match.
Credit Entry - Again, on the word document has Creator-Sub-Publisher so let's make them match.
Assign - as above - should be Creator and Publisher.
Again, I hope that helps.
Magratheas Workshop - Permissions and User Roles - Documentation
Haragai Posted Feb 24, 2011
> Nobody at all can unhide a document as it stands. I assume that should be ticks for Creator and Publisher
I'd say that is for the Publisher (or whomever decided to hide the Entry besides the Creator) after a discussion with the Creator.
> Should the Creator be able to categorise their Entry, or should that be with the Publisher alone?
The Creator can categorise the Entry but it is up to the Publisher to check and possibly correct that categorisation.
> anyone can put an article into a Review forum?
It is for the Creator to decide to put an entry up for review. This has nothing to do with being picked for publication.
> they can decide to assign creator rights over to someone else
Uhm, no. The Creator will always be attached to the Entry. The Creator can assign editing rights to someone else as a co-writer whom will be named in the credits.
! Martin
--- jus' puttin' a muddy boot in
Magratheas Workshop - Permissions and User Roles - Documentation
Haragai Posted Feb 24, 2011
> If higher roles are additive ...
True. We need to define the rights (and responsibilities) of each role seperately without inheritance of rights of a 'lower' role. This also diminishes discussion of hierarchical levels.
> Set status on Entry
Oh dear, hierarchy is back. Any level should be able to re-set the status to at least 'one lower' or all the way back to 'Draft'. The Creator must also be able to re-set the status to 'Draft' is he/she/it decides to work on the entry some more.
This implies that editing an Entry cannot be done past a certain Status.
! Martin
--- jus' puttin' a muddy boot in
Magratheas Workshop - Permissions and User Roles - Documentation
paulh, vaccinated against the Omigod Variant Posted Feb 24, 2011
" I would make sure that we can have multiple 'Written By' names, not just one, so that we can have true Collaborative Entries. I like having 'With help from' as it allows those who have contributed to be recognised without detracting from the person who did the work putting it all together and originated the idea." [Vip]
I like that idea a lot. "All" my edited guide articles have been collaborations.
"> they can decide to assign creator rights over to someone else
Uhm, no. The Creator will always be attached to the Entry. The Creator can assign editing rights to someone else as a co-writer whom will be named in the credits." [Martin/Haragai]
That's fine if the Creator has not left the site forever. As far as I can figure, a researcher who wants to write a guide article on a topic that someone else started (but never submitted for editing)
is supposed to try to approach the other person and offer to help finish their article, or take it over completely. This doesn't work when the other person has left, and it's kind of dicey to have to
write an entry that *might* seem close enough to the other person's work to be seen as copyright infringement if miraculously reappears and gets upset.
Magratheas Workshop - Permissions and User Roles - Documentation
Milla, h2g2 Operations Posted Feb 24, 2011
Right.
I have updated the Excel document, or actually the Google document which is the source:
https://spreadsheets.google.com/ccc?key=0AkE-1k4J7btrdElRRWt4NVVhOV9NVXRPbnRaNnZ3RkE&hl=sv&authkey=CPLnrpII#gid=0
(Copy and paste is necessary, I'm afraid)
The Hide Unhide issue: As I see that as a document status, it is now included in that document, where the "swim lanes" show who can do what, and arrow heads show what is reversible:
https://docs.google.com/drawings/edit?id=1kxgwrI_-2ZCVZusT25PKp07nQnWom3mFVjQPVVVlGds&hl=sv&authkey=CIOt4-sD
The Credits; Is part of the User Requirements, but who can credit at which status, is in the Roles and Rights google doc.
Additive roles:
Have removed sentence about "Higher roles include lower rights" and put more x's in the boxes.
Creator has :
I suggest that the Publishers can assign Creator rights to an entry if the original author is no longer around, as part of the Update Process (which is a whole n'other bucket of eels).
Magratheas Workshop - Permissions and User Roles - Documentation
Haragai Posted Feb 24, 2011
About 'ed Entries:
We can have a stipulation that when an Entry has a co-writer, the editing and determination whether an Entry is up for review is delegated to the co-writer when said co-writer can convince The Editors that the Creator has left the building.
The name of the Creator still stays on the Entry.
In such a case the Editor could add some sort of by-line on the Entry like "The creator has not responded therefore the co-writer (name)has been granted delegated ownership of this Entry".
Entries without co-writers can be stowed in the bin after a pre-determined period where the can pick it up again when they un-.
! Martin
---"No worries" he said. NOW I'm worried.
Magratheas Workshop - Permissions and User Roles - Documentation
Haragai Posted Feb 24, 2011
In the 'Status' swimmingpool: add a uni-directional arrow from 'Queued' to 'Hidden' because a Publisher can hide an Entry before it is published.
We could consider adding the option "Submit for Review"-button so that a Researcher does not have to wait for the Scouts to spot the Entry?
! Martin
--- jus' puttin' a muddy boot in
Magratheas Workshop - Permissions and User Roles - Documentation
Vip Posted Feb 25, 2011
Excal doc: A lot of this is much clearer, well done. Especially the tag line, which now makes much more sense where you have specified at which time each role can add/remove tags.
Magratheas Workshop - Permissions and User Roles - Documentation
paulh, vaccinated against the Omigod Variant Posted Feb 25, 2011
Magratheas Workshop - Permissions and User Roles - Documentation
Milla, h2g2 Operations Posted Feb 26, 2011
Haragai,
Creators and Co-Authors can put en entry from Draft to For Review. From there scouts pick up.
Or do we need an extra status for things in the Peer Review forum, which signals that the Creator(s) consider it ready for picking? I think it adds an unnecessary layer, but do convince me otherwise
It's good and it's bad, that I have several documents, as they do affect eachother, but I'll keep it, because I think it visualises.
Entry status:
https://docs.google.com/drawings/edit?id=1kxgwrI_-2ZCVZusT25PKp07nQnWom3mFVjQPVVVlGds&hl=sv&authkey=CIOt4-sD
Roles and rights:
https://spreadsheets.google.com/ccc?key=0AkE-1k4J7btrdElRRWt4NVVhOV9NVXRPbnRaNnZ3RkE&hl=sv&authkey=CPLnrpII#gid=0
User requirements:
https://docs.google.com/document/d/1ngidRXXYP_eUs9nHKTl8jL699h8ukhyEEKFhsvS99BI/edit?hl=sv&authkey=CLL6gusL#heading=h.tp546b-6yowur
Also: Update process:
https://docs.google.com/drawings/edit?id=1UvY2mh3VT2zMq1Hlh40MmHT40QD5a-jvue60j1m4q9A&hl=sv&authkey=COWLua4N
Key: Complain about this post
- 1
- 2
Magratheas Workshop - Permissions and User Roles - Documentation
- 1: Magrathea (Feb 20, 2011)
- 2: 8584330 (Feb 21, 2011)
- 3: Mrs Zen (Feb 21, 2011)
- 4: 8584330 (Feb 21, 2011)
- 5: Mrs Zen (Feb 21, 2011)
- 6: Milla, h2g2 Operations (Feb 23, 2011)
- 7: Vip (Feb 23, 2011)
- 8: 8584330 (Feb 23, 2011)
- 9: Z (Feb 23, 2011)
- 10: Vip (Feb 24, 2011)
- 11: Vip (Feb 24, 2011)
- 12: Haragai (Feb 24, 2011)
- 13: Haragai (Feb 24, 2011)
- 14: paulh, vaccinated against the Omigod Variant (Feb 24, 2011)
- 15: Milla, h2g2 Operations (Feb 24, 2011)
- 16: Haragai (Feb 24, 2011)
- 17: Haragai (Feb 24, 2011)
- 18: Vip (Feb 25, 2011)
- 19: paulh, vaccinated against the Omigod Variant (Feb 25, 2011)
- 20: Milla, h2g2 Operations (Feb 26, 2011)
More Conversations for Magrathea's Workshop - Permissions and User Roles
Write an Entry
"The Hitchhiker's Guide to the Galaxy is a wholly remarkable book. It has been compiled and recompiled many times and under many different editorships. It contains contributions from countless numbers of travellers and researchers."