[silva-dev] problems with metadata

[Samuel Schluep]

Well, there are also other problems with reindexing and acquired 
metadata items:

1. If acquirable metadata items are revised the properties tab of a 
Silva Document (Version) which acquires the metadata values displays the 
correct values. However the index of the document version is not 
properly updated.

2. If a 'save' button in the properties tab is pressed and a document 
version is published afterwards the indexer looses the value of an 
acquired metadata item.

I don't know, if these problems are caused by the same bug(s) Clemens 
has found. It reminds me to some discussion a long time ago, see 
http://infrae.com/mailman_/pipermail/silva-dev/2003q3/000462.html . But 
these problems should have been resolved. The current findings might 
represent new bugs.

Kind regards
Sam

(Tested with Silva 1.3-all, Zope 2.7.7-final, Python 2.3.5)

>Hey!
>
>I'm doing some zcatalog queries on metadata, in Silva-1.3,SilvaMetadata 0.10, 
>Zope 2.7.5. I think I've found two problems with the reworked metadata tab.
>
>1)  It appears that in Silva/views/edit/save_metadata.py, the 
>binding.setValuesFromRequest doesn't pass along reindex=1, as the old script 
>did.  
>2) Even after adding reindex=1, the object isn't reindexed in the catalog upon 
>metadata save.  Downgrading to Silva-1.2.1/SilvaMetadata 0.8, saving metadata 
>reindexes the object.
>3) Following the execution path, the method setValuesFromRequest doesn't pass 
>the variable reindex to self._setData
>
>However, even after passing reindex to self._setData, and verifying that 
>_setData was reindexing the object, the catalog still wasn't actually 
>updated.
>
>Any ideas what is going on?  
>
>Thanks,
>Andy
>  
>
-- 
Samuel Schluep | ETH Zürich
Center for Organizational and Occupational Sciences (ZOA)
Unit Man-Machine Interaction
+41 1 632 74 24 | schluep at ethz.ch | http://www.zoa.ethz.ch