portal_relationships (was Re: [Zope-CMF] Future CMF)

[Ausum Studio]

I knew about OrganizationObjects proposal since last year, although I didn't
dive into the details. As it still seems, it's clearly tied to Zope3
development and its announced ObjectHub.

What I have in mind is a portal tool for the CMF that takes over the
relationships between objects at an end-user level, that provides a reliable
big picture of the knowledge context surrounding any content object. I'm
after getting to know an object's "tribe" without the aid of any
just-aproximated algorithm-based crawler/search-engine, because the kind of
relationships we'll be dealing with are most of the time human-determined,
when not automatically generated by means of previously stored relations
info.

In a highly stressed media company, content may arrive from different
sources, even without have been properly catalogued. (Metadata is almost
always filled the moment the stress is gone, generally the day after) and
so, photos, Flash animations, clips of audio & video, texts, documents, and
tables can get the editors workspaces without any context information,
leading many times to the fact that important and relevant information is
not to be considered by the authors at the editing hour. My thought is that,
after throwing everything in to a Zope-based dream system, everything could
get into context by just starting to qualify the very first objects.

How much of this can be provided by the ObjectHub and OrganizationObjects? I
guess is you, the Zope3 team, the ones who could tell us.  :)


Ausum


----- Original Message -----
From: "Ken Manheimer" <klm@zope.com>


> I'm not sure this will have immediate impact on the discussion, because it
> involves longer-range (and slightly soft) plans rather than anything
> likely to land immediately.  However, the discussion is getting to verge
> on the same issues, particularly with stuff like:
>
> On Tue, 8 Oct 2002, Ausum Studio wrote:
>
> > Coud duplicate ZCatalog's functions. Maybe we use a special index (or
index
> > type) for the objects's stored relationship info.
>
> A while back, i informally proposed something i was calling
> "organization objects", which are essentially indexes specialized for
> specific object relationships, depending on provisions for tracking
> changes to objects so that the relationship records could be revised
> as the relationships change (eg, when objects are resituated in the
> folder system or in their abstract relationships to each other).
>
> The proposal is at:
>
>   http://cmf.zope.org/rqmts/proposals/OrganizationObjects
>
> Zope3 is being developed with some of the necessary plumbing,
> specifically the Object Hub:
>
>   http://www.zope.org//Wikis/DevSite/Proposals/ObjectHub
>
> and the Event Channel:
>
>
http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/EventChanne
lProposal
>
> The object hub and event channel are becoming as real as anything in
> Zope3, and the Zope3 effort is getting to the determination of Content
> as an entity.  Meanwhile, in the course of a customer gig i get a
> chance to work on a specialized object to handle hierarchy/dependency
> relationships, which may get a start on one (fairly widely useful)
> aspect of object relationships.
>
> Like i said, i'm not sure how this helps the discussion, except you
> may find a number of your concerns reflected in the organization
> objects proposal...
>
(...)
> --
> Ken
> klm@zope.com
>