Re: Local ECM Provider
Some comments about workspaces.
Workspace and Sections are concepts defined in CPS.
They are regular folder resources that may contains other resources but
with the particularity that a Workspace folder is "editable"
(contents and children may be modified) while Section folders contains
read only resources (published content)
Each type of folder may impose it's own workflow and actions (on a
resource inside sections we may have available the action "unpublish"
while inside a workspace this action is not existing)
Anyway each, ECM provider may defines it's own type of folders. Other
provider than CPS may have more specialized folders or may not have the
workspace / section concepts.
This should be transparent to Apogee. Each ECM provider should be able
to define it's own object model, workflow and security rules.
Apogee will only know about allowed actions that can be done on a
resource in a given context.
So, Apogee should not be aware on the fact that CPS have workspace and
sections but it should only know what kind of operations a resource is
supporting
This can be done by querying the ISiteController (that will consult the
right ECM provider bound to the current) thorugh the
ISiteController.isOperationEnabled() method. This method may delegate
the query to the underlying ECM provider but may also do some checks on
the local side such as if this type of operation was registered by the
ECM provider.
Bogdan
Workspaces are folders from
Eric Barroca wrote:
> Hi Sato,
>
> Sato a écrit :
>
>> I'd like to understand typical real world usages(workflow, security,
>> etc).
>> Could you suggest me some documents?
>>
>
> Here it is... 
>
> Security:
> - in a workspace (let's use this term to define a space where
> several people can share and work on document), you put some document
> - you define rights on this workspaces for example applying roles
> to users (let's say you applied 2 roles: reader and contributor)
> - user A has the contributor role while user B has the reader role
> - when user A access to the workspace via Apogee, he needs to be
> able to modify the document (thus apogee need to display the Modify
> action / menu on the document)
> - when user B access to the workspace, we have to hide all
> actions/menu items his role doesn't have access to
>
> Apogee needs, for that, to have a security model that can be mapped to
> the ECM security model so that user actions / menu items available on
> resources can depends on access rights defined by the server.
> Extension of this:
>
>
> Workflow:
> - on my workspace, I have a document on which I have to do some
> workflow action
> - Apogee needs to know what workflow actions are to be done for the
> current user on a resources
> - moreover, apogee need to know where to find the interface to
> display to the user so that he can do the workflow action
>
> Then, Apogee need to have a generic model to get actions from the
> remote ecm platform (what we call operations in the model, I have well
> understood - Bogdan, correct me if I'm wrong 
.
>
>
> Does it answer to you questions? (I hope to be enough clear on what I
> have in mind on those points, do not hesitate to ask more .
>
>
> Thanks,
>
> EB.
>
--
--
Bogdan Stefanescu - Apogee project Team Leader
Nuxeo - Open Source ECM - www.nuxeo.com
Apogée - the rich client platform for ECM
http://apogee.nuxeo.org/ - http://www.nuxeo.com/en
RSS Feed