[Zope-PTK] Chowning content

[Jens Vagelpohl]

your (excellent) question touches another point that came up in conjunction
with the user management on zope.org. what will happen to content that was
created by a member that has not visited the site in a long time and that
can be considered to be "expired"? the solution could be that we have a
script that is run at certain intervals to check if a user has not logged in
for a certain amount of time. if the user does not have any content in his
own area it just gets deleted. but what if there is content that is probably
linked to from elsewhere as well?

the solution where all content is "taken away" from the user upon publishing
and becomes owned by the portal is unsatisfactory, at least in the case of
zope.org. people like to control what they produce and what if i want to
change an item after publishing? do i have to go to the site manager and beg
for access?

the other solution, where the content is only brought into a common area and
ownership goes to the portal upon expiration of a member's account is a
better way, but it will break internal and external links that point to the
old location for the given piece of content.

from a pure technical side it is probably easier to write a script that can
be run once in a while to "repossess" content and bring it into a common
location in the portal. changing the policy so that publication means taking
the item out of the author's hand is possible as well, but it requires going
into the python source code at this point and as such is not "upgrade
proof".


either way, using python it is easy to do a "cut and paste" operation on a
content object and change its ownership. the final decision depends on your
situation.

jens


on 2/19/01 19:33, Nolan Darilek at nolan_d@bigfoot.com wrote:

> I started playing with the PTK/CMF a few weeks ago after the
> introduction of skins, and have been slowly piecing together a site
> based upon it. I must say that I'm extremely impressed with skins. I'm
> probably a PTK/CMF zealot; I wanna use this in most of my projects. :)
> Congratulations on an excellent product!
> 
> Anyhow, as you've probably guessed, I do have a question. This is
> probably more of a zope issue, but I'd be interested in hearing what
> others think.
> 
> I'm developing a community-oriented site in which the community
> changes very often. I'm a college student developing a website for a
> student organization whose membership changes yearly. However, despite
> the volatile membership, some content should be permanent. I'm trying
> to create a system for automating our newsletter creation and
> publishing; traditionally we've used paper/mail which is
> expensive. Electronic creation/publishing allows us to decrease
> costs while increasing the amount of published content, and we'd like
> to publish member contributions.
> 
> When members create accounts, they'll be able to create portal content
> which, when approved, can be added to the newsletter. Since the member
> account will vanish when the member leaves the organization, I'd like
> for old content to remain, so I'd like to change the content's owner
> to the site administrator user. Is it possible to do this without
> recreating a new object, cut-n-pasting the old content into it and
> re-approving?
>