|
|
|
|
The following issue has been updated. |
|
Updater: Olivier Grisel
Date: 30/05/07 15:38
Comment:
typos
|
|
| Field |
Original Value |
New Value |
|
Change By
Olivier Grisel
on 30/05/07 15:38
|
|
Description
|
In the future we will probably based the folder / workspace / section content views on stateful query model based search results to allow the user to quickly filter / sort the content.
However, this require synchronous indexing of the metadata that are used to perform the filtering (for instance ecm:type, ecm:currentLifecycleState, ...) whereas will still want to perform the fulltext indexing asynchronously (text extraction of a 50Mo PDF might take a while ...).
Thus we need the setup of the search service to choose which field is to be indexed synchronously by a core event listener (to be written as was done in the EURPCF project) and which field is to be indexed asynchronously by the existing JMS topic listener.
|
In the future we will probably base the folder / workspace / section content views on stateful query model-based search results to allow the user to quickly filter / sort the content of the folder she is browsing.
However, this requires synchronous indexing of the metadata that are used to perform the filtering (for instance ecm:type, ecm:currentLifecycleState, ...) so that we copy / pasting / deleting or dropping new file onto the folder we don't have an inconsistent view of the content of the folder.
However will still want to perform the fulltext indexing asynchronously (text extraction of a 50Mo PDF might take a while ...).
Thus we need the setup of the search service to make it possible to choose which field is to be indexed synchronously by a core event listener (to be written as that was done in the EURPCF project) and which field is to be indexed asynchronously by the existing JMS topic listener.
|
|
In the future we will probably base the folder / workspace / section content views on stateful query model-based search results to allow the user to quickly filter / sort the content of the folder she is browsing.
However, this requires synchronous indexing of the metadata that are used to perform the filtering (for instance ecm:type, ecm:currentLifecycleState, ...) so that we copy / pasting / deleting or dropping new file onto the folder we don't have an inconsistent view of the content of the folder.
However will still want to perform the fulltext indexing asynchronously (text extraction of a 50Mo PDF might take a while ...).
Thus we need the setup of the search service to make it possible to choose which field is to be indexed synchronously by a core event listener (to be written as that was done in the EURPCF project) and which field is to be indexed asynchronously by the existing JMS topic listener.
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
