Index: openacs-4/packages/acs-content-repository/www/doc/guide/search.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/search.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/acs-content-repository/www/doc/guide/search.html 13 Mar 2001 22:59:26 -0000 1.1 +++ openacs-4/packages/acs-content-repository/www/doc/guide/search.html 7 Aug 2017 23:47:47 -0000 1.2 @@ -4,18 +4,18 @@

Search

- Content Repository : Developer Guide + Content Repository : Developer Guide

The content repository provides a consistent sitewide interface for -searching content. It uses Intermedia to index the content -column of cr_revisions) as well as all the attribute columns +searching content. It uses Intermedia to index the content +column of cr_revisions) as well as all the attribute columns for each content type.

Searching Content

The content column in cr_revisions may contain -data in any text or binary format. To accomodate searches across +

The content column in cr_revisions may contain +data in any text or binary format. To accommodate searches across multiple file types, the content repository uses an Intermedia index with the INSO filtering option. The INSO filter automatically detects the the file type of a binary object, and extracts text from it for @@ -61,15 +61,15 @@

Multilingual searches are not enabled by default. You may enable them for one more languages by setting the appropriate - Intermedia preferences when creating cr_rev_content_index. + Intermedia preferences when creating cr_rev_content_index.
Some items are not appropriate to display "stand-alone", but rather need to appear only in the context of a container document (typically their parent in the content repository). - This is probably a limitation of content_item.get_path: + This is probably a limitation of content_item.get_path: it should be possible to specify an arbitrary function to return the path for items of a particular content type, with - content_item.get_path as the default. + content_item.get_path as the default.

Searching Attributes

@@ -84,13 +84,13 @@

After creating a new revision and inserting attributes into the storage table for the content type and all its ancestors, you must -execute the content_revision.index_attributes procedure. +execute the content_revision.index_attributes procedure. (Note that this cannot be called automatically by -content_revision.new, since the attributes in all extended +content_revision.new, since the attributes in all extended storage tables must be inserted first).
This procedure creates a row in the -cr_revision_attributes table, and writes an XML document +cr_revision_attributes table, and writes an XML document including all attributes into this row. A Java stored procedure using the Oracle XML Parser for Java v2 is used to actually generate the XML document. @@ -113,17 +113,17 @@
Some limitations of the current implementation include:
1. A USER_DATASTORE associated with each row of the - cr_items table, which feeds Intermedia the contents - of the content column (a BLOB) for the live +
2. A USER_DATASTORE associated with each row of the + cr_items table, which feeds Intermedia the contents + of the content column (a BLOB) for the live revision of an item. This should theoretically be more efficient for searching live content, especially in production environments where content is revised often. -
3. A second USER_DATASTORE associated with each row of the - cr_items table, which feeds Intermedia the XML +
4. A second USER_DATASTORE associated with each row of the + cr_items table, which feeds Intermedia the XML document representing all attributes for the live - revision of an item (from cr_revision_attributes). + revision of an item (from cr_revision_attributes).
5. The default XML document handler for the content repository simply provides a flat file of all attributes. Content types