Alias Entity Creator about absolute-pin HOT 3 CLOSED

External note: anyone can create aliases in their personal community and apply them across any communities they want... Is that sufficient?

Internal note: the way it currently works:

• Anyone can create an alias share
• It will not be applied until endorsed by an admin/moderator
• Any content publisher can modify a share that is solely contained in communities they can publish in
• Changes to a share currently require it to be re-endorsed

I think perhaps content publishers should be able to modify shares also? If you can create a share you should probably be allowed to set an alias also... If I made that change then anyone could edit the "master" alias list for a community...

I want to talk this through with Caleb and Andrew

from absolute-pin.

Is there any downside to permitting anyone who has access to a community to view and create new aliases without having been designated the “owner” or without an endorsement? Not sure why this would create any problems but open to the discussion if there is an issue.

From: Alex [mailto:[email protected]]
Sent: Thursday, March 21, 2013 3:17 PM
To: IKANOW/Absolute-Pin
Cc: Scott Schneiderman
Subject: Re: [Absolute-Pin] Alias Entity Creator (#68)

External note: anyone can create aliases in their personal community and apply them across any communities they want? Is that sufficient?

Internal note: the way it currently works:

• Anyone can create an alias share
• It will not be applied until endorsed by an admin/moderator
• Any content publisher can modify a share that is solely contained in communities they can publish in
• Changes to a share currently require it to be re-endorsed

I think perhaps content publishers should be able to modify shares also? If you can create a share you should probably be allowed to set an alias also... If I made that change then anyone could edit the "master" alias list for a community...

I want to talk this through with Caleb and Andrew

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/68#issuecomment-15259568.

from absolute-pin.

The default access rights of a community member is "read only" with regards to artifacts that affect the rest of the community's experience - currently this extends to sources and aliases (this may in the future affect shared widget settings on a widget-per-widget basis). This is a pretty standard policy, and not one I'm inclined to change.

Consistently with that policy, any person can change their own aliases. Groups of non-admins can also create a shared alias experience by creating their own community, making themselves moderators, and then creating an aliases share in there.

The only question is whether "content publishers" should have the right to set other people's experience, or if that should be restricted to moderators. I initially went conservative, but I'm going to get some thoughts from other people with a background in the secure gov community (like me).

EDIT: and everyone else's! :)

from absolute-pin.