Date: Feb 05, 2008
People: Craig Counterman, Mike Moretti, Qing Dong, Robin Colodzin, Catherine Iannuzzo, Derek Jaeger
Purpose: Review Qing's proposed generic ECM API; get more information on Stellar's needs and data model
On first review, the generic ECM API which Qing proposed seems to meet Stellar's needs. The next step to confirm this is mapping Stellar's objects to the ECM generic nodes. Craig will create a Java API against the proposed ECM to begin this process.
Needs for further information:
ECM team needs a list of Stellar roles, and what each role can do in what context; What is the relationship between roles and contexts?
As part of this discussion, Craig talked some about Fair Use material - access control markup language. Is this something that Stellar currently uses, or is it something that Stellar would like to use in future?
Next Steps:
Qing needs access to oracle database
Qing will look into schema language, how ECM will be represented in XML
Craig's task:
Create first pass of Java API that talks with REST API
• Model for documents
• Business methods and managers
Qing's action items:
1. Check the xml schema language and jaxb.
2. check how alfresco does versioning.
stellar database schema
document on authorization/permission
stellar2-schema-content.gif
stellar2-schema-auths.gif
revised ECM model
revised ECM REST API
stellar's proposed java api
1 Comment
Qing Dong
how Alfresco does versioning:
It seems that Alfresco does versioning in two ways. There is a cm:versionable aspect (http://wiki.alfresco.com/wiki/Versioning_Behaviour). The web service api also has an authoring service that allows us to create new version, get version history, delete all versions etc.
There are also the AVM, Alfresco's advanced versioning model, which is a versioned repository which is similar to svn (http://wiki.alfresco.com/wiki/Versioned_Directories). We have to use the AVM Service api and is not supported by the web service api.