Re: OGo and asterisk, SUMMARY

On Tuesday 28 November 2006 07:42, Adam Tauno Williams wrote:

> To be useful though I think the interface would have to be smart enough
> to provide different properties (for creation) based upon the type of
> file.  That makes it a bit more complicated.  It seems like it would
> have to be configurable somewhat like extended attributes are
> configurable.

The way this is addressed in zope/plone world is that they separate mime types 
from keywords. Keywords are tags that are either established by the admin 
and/or users pending rights allowing users to add this tag to a particular 
file. 

So for example creating or uploading a .doc file called testrun the mime type 
would be .doc (and this is assigned automatically) but the keyword (in this 
example) would be system_test. This keyword is selected from a list by the 
user and associated with the document. This is done via an edit form 
associate with the particular file.  If the user has permission they can 
first add a new keyword and then associate it with the file. 

The principle here is simple as it allows indexing and searching based on 
keywords independent of the file type. Sorting then becomes very simple. 

So in a journal context if I want a listing of all documents that pertain to X 
provided that all documents were indeed marked with the keyword X a simple 
search would provide the listing which then can be saved, linked to or 
stored.

From an asterisk perspective pending on where the data is stored, (voice mail 
for example) keyword may or may not be that useful. 


> But if you are automatically importing some content then setting a set
> of properties is pretty straight forward.

Ya thats how I understand it. 

/ch

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss