Forum OpenACS Development: Re: Any good reason content_item__move function only allows folders as parent?

What does it mean for an arbitrary acs_object which is not another item or a folder to have content_item children?

What does it mean, for example, for a content_revision to have content_item children?

It means you don't have to have a separate table to define a relationship between the object and the cr_item.

For a user, that might mean the user's file-storage root folder, and for a revision it could be a thumbnail image of that revision (which we do here).

This allows you to quickly get any items you need for an object in the context of a package, such as file-storage where you need to know which files to show for a specific user, or in a forum where you need to list available attachments.

-- NJL

Jim,

The content repository doesn't define any meaning to the parent_id relationship. The meaning is defined by the applications that use the content repository.

There isn't any restriction or problem to having a content_revision as a parent_id, although it could be confusing if the semantics were not documented in the package that used the content repository in that way.