Isokangas, Erik HTC/DE/FRA writes:

I'm struggling a bit with the product LocalFS and hoping someone can point me in the right direction.

LocalFS installs and seems to work fine out-of-the-box. However, I would like to catalog each file (and contents of each file) in the file system being served. The properties of my LocalFS object has a "catalog" option which claims to catalog files in the filesystem. However, this doesn't seem to do anything.

I'm using Zope 2.6.0 on Suse8.0 Linux. I have a Zcatalog object installed with only two indices (fulltext, keywords) - no metadata fields currently defined.

What is the process that LocalFS uses to catalog files in the filesystem? How does LocalFS know which catalog, indices, metadata to use, etc.? It does not.

Zope's cataloging works as follows: It interpretes the index names and the names in the meta data table as names of attributes of an object to be cataloged. If there is no such attribute, the object does not provide a value for the name. If it is, the attribute is called without arguments (if it is callable) and the value taken, otherwise, the attribute value itself is taken. This value is the objects value for the given name. It is uses as base for indexing or meta table column. Read the ZCatalog section in <http://www.dieter.handshake.de/pyprojects/zope/book/chap3.html> for more details. Dieter