[OGo-Discuss] OGo and asterisk, SUMMARY

[chris h]

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 ty=
pes=20
from keywords. Keywords are tags that are either established by the admin=20
and/or users pending rights allowing users to add this tag to a particular=
=20
file.=20

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

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

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

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


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

Ya thats how I understand it.=20

/ch