[development] Multiple user aliases - Multiple user node ownership

[zeljko blace]

On Jan 13, 2008 12:42 PM, Karen Stevenson <karen at elderweb.com> wrote:
> I think this would be a step in the right direction. But even a revision
> might have multiple authors. Take the case of a group of people that has
> been working together to solve a problem and publish the results. They all
> ought to get credit as authors, instead the credit will go only to the
> person who input it into the system (who might even just be an assistant and
> not one of the authors).

if there is a way to asign authorship and authoring rights to  Organic
Group, that would be great!

> The new 'add more' AHAH button in D6 could be useful here to build a list of
> authors.

Could any of this be done in time for D6 Final release?

>
> Karen
>
>
>
> ----- Original Message ----
> From: FGM <fgm at osinet.fr>
> To: development at drupal.org
>
> Sent: Sunday, January 13, 2008 2:08:02 AM
> Subject: Re: [development] Multiple user aliases - Multiple user node
> ownership
>
> Actually, I'd be tempted to say that in most cases, nodes should not have
> one author, but revisions should, and nodes be characterized by the set of
> the authors of the revisions. This is actually probably best for
> intellectual property issues. This would credit actual contributors more
> efficiently than the current system, where all goes to the latest modifier,
> as exemplified by the recent problem with the handbook reorganization, in
> which lots of authoring credit was thus lost.
>
> ----- Original Message -----
> From: "ekes" <ekes at aktivix.org>
> To: <development at drupal.org>
> Sent: Sunday, January 13, 2008 2:47 AM
> Subject: [development] Multiple user aliases - Multiple user node ownership
>
>
> > I've had several requests to: (i) To be able to have nodes that can be
> > (owned) edited/deleted by multiple users (group posts); (ii) To be able
> > to post under aliases - without logging into multiple accounts.
> >
> > Obvious answers: (i) Something nasty with Node Access; (ii) CCK field to
> > be displayed replacing the the usual user field, trouble of having
> > reusable or identifiable aliases as well.
> >
> > (in/sane?) answer: Write module that - (i) Creates a (blocked) user to
> > register 'nicks' (ii) Links 'nicks' with user(s) 1->1 or 1->many (iii)
> > uses nodeapi to add 'nick' to node form (iv) adds edit/delete to nodes
> > that relate to user 'nick's (just skipping and adding different access
> > control to present node functions).
> >
> > Just a check if I'm looking the wrong way, or if I'm just hanging out in
> > the marginal 20% as usual.
> >
> > ekes
> > http://drupal.org/user/10083