I am fine with posting my email in the wiki so everyone can see it. It's not a secret and I think it will help.
And yup, it is yet another big storage app. I know that solving the storage issue is very important to Wilson, and we will keep plugging at it.
It is true the Touchstone as it currently exists won't do web services.
I believe that we need to address this issue. It's a thorny one, in fact no one has really solved it well. But I'm not afraid to take it on 
-c
Qing Dong wrote:
> Thanks Catherine. It made things much clearer now. Can I post your
> email in wiki's meeting minutes so other people can see it or would
> you rather make it private for now?
>
> This project will require lots of storage also, so we need to figure
> out our storage solution soon.
>
> We also heard that touchstone will not support web services. This will
> impact the ECM development. If we have to use application certificate,
> the ECM web service will not be as open as we want it to be.
>
> Qing Dong
> Programmer Analyst
> Information Services and Technology
>
> W92-144
>
> dongq@mit.edu
>
> 617-253-2546
>
>
> ----Original Message----
> From: Catherine Iannuzzo [mailto:iannuzzo@MIT.EDU]
> Sent: Friday, March 21, 2008 1:11 PM
> To: Qing Dong
> Subject: ecm
>
> Hi Qing, I apologize that I haven't been able to talk with you in more
> detail this week.
>
> Here is what I am thinking...
>
> I want to build the "My Files" application. This application will use
> the ECM backend and give us a chance to work through some of the tough
> problems.
>
> This is what I think "My Files" should do:
>
> - support WebDAV, so users can map to it as a remote drive on PC and
> Mac
> - provide a web client that allows the following:
> - browsing folders/files
> - assigning permissions to folders/files
> - assigning metadata aspects to folders/files (i.e. give it a "type")
> - tagging
> - searching based on metadata, etc.
> - simple kinds of workflow
>
> The "workflow" part comes in because if files are dropped into a
> folder using WebDAV they will not have metadata attached. However, in
> Alf you can define workflow tasks that will happen when you do that,
> and they could be designed to provide some of that metadata. For
> example, people can use a "drop box" folder that fires off a workflow
> for anything dropped into it. A "Stellar upload" drop box could
> automatically turn anything in it into a Stellar course material, or
> whatever. We could even do the same thing w/Thalia eventually. Put all our thumbnail, etc.
> generation into a workflow triggered on the Alfresco side.
>
> This ends up being a fairly full-fledged app. In a way, it does almost
> everything all our other apps do (or will do).
>
> This app will use our "new" ECM API, and give us a chance to test that
> out (I think).
>
> Josh Scott will be coming to help us work on the ECM project, doing
> the project planning, requirements, etc. I know we need to make this
> less vague and more real.
>
> is this any help at all?