Skip to content

A
acs-content-repository
Commit 8e2ff12b authored by Frank Bergmann's avatar Frank Bergmann
Browse files
Options

- OpenACS 5.9 Import

parent 8061ff9d
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 2580 additions and 0 deletions
tcl/content-procs-postgresql.xql 0 → 100644
View file @ 8e2ff12b
<?xml version="1.0"?>
<queryset>
<rdbms><type>postgresql</type><version>7.1</version></rdbms>
<fullquery name="cr_count_file_entries.count_entries">
<querytext>
SELECT count(*) FROM cr_revisions WHERE substring(content, 1, 100) = substring(:name, 1, 100);
</querytext>
</fullquery>
</queryset>
www/doc/api/content.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Package: content}</property>
<property name="doc(title)">Package: content</property>
<master>
<body>
<h2>content</h2><p>
<a href="../index.html">Content Repository</a> : content</p><hr><ul><li>Function content.blob_to_string</li></ul><table cellpadding="3" cellspacing="0" border="0">
<tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><i>Not yet documented</i></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
function blob_to_string(
blob_loc blob) return varchar2
as language
java
name
'com.arsdigita.content.Util.blobToString(
oracle.sql.BLOB
) return java.lang.String';
</tt></pre></td></tr>
</table><ul><li>Procedure content.blob_to_file</li></ul><table cellpadding="3" cellspacing="0" border="0">
<tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><i>Not yet documented</i></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
procedure blob_to_file(
s varchar2, blob_loc blob)
as language
java
name
'com.arsdigita.content.Util.blobToFile(
java.lang.String, oracle.sql.BLOB
)';
</tt></pre></td></tr>
</table><ul><li>Procedure content.string_to_blob</li></ul><table cellpadding="3" cellspacing="0" border="0">
<tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><i>Not yet documented</i></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
procedure string_to_blob(
s varchar2, blob_loc blob)
as language
java
name
'com.arsdigita.content.Util.stringToBlob(
java.lang.String, oracle.sql.BLOB
)';
</tt></pre></td></tr>
</table><ul><li>Procedure content.string_to_blob_size</li></ul><table cellpadding="3" cellspacing="0" border="0">
<tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><i>Not yet documented</i></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
procedure string_to_blob_size(
s varchar2, blob_loc blob, blob_size number)
as language
java
name
'com.arsdigita.content.Util.stringToBlob(
java.lang.String, oracle.sql.BLOB, int
)';
</tt></pre></td></tr>
</table><p>Last Modified: $Id: content.html,v 1.1.1.1 2001/03/13 22:59:26
ben Exp $</p>
</body>
www/doc/api/folder.adp 0 → 100644
View file @ 8e2ff12b
This diff is collapsed.
www/doc/api/keyword.adp 0 → 100644
View file @ 8e2ff12b
This diff is collapsed.
www/doc/api/symlink.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Package: content_symlink}</property>
<property name="doc(title)">Package: content_symlink</property>
<master>
<body>
<h2>content_symlink</h2><p>
<a href="../index.html">Content Repository</a> :
content_symlink</p><hr><ul>
<li><a href="#overview">Overview</a></li><li><a href="#related">Related Objects</a></li><li><a href="#api">API</a></li>
</ul><p> </p><h3><a name="overview">Overview</a></h3><p>Symlinks are pointers to items within the content repository.
They are simply used to create links between content items.</p><p> </p><h3><a name="related">Related Objects</a></h3>
See also: content_item, content_folder
<p> </p><h3><a name="api">API</a></h3><ul><li>
<font size="+1">Function:</font>
content_symlink.is_symlink</li></ul><p>Determines if the item is a symlink</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Karl Goldstein</td>
</tr><tr>
<th align="left">Returns:</th><td align="left">'t' if the item is a symlink, 'f' otherwise</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1"><tr>
<th align="right" valign="top">item_id:</th><td>  </td><td>The item id</td>
</tr></table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
function is_symlink (
item_id in cr_items.item_id%TYPE
) return char;
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>content_symlink.new, content_symlink.resolve</td>
</tr>
</table><p> </p><ul><li>
<font size="+1">Function:</font> content_symlink.new</li></ul><p>Create a new symlink, linking two items</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Karl Goldstein</td>
</tr><tr>
<th align="left">Returns:</th><td align="left">The id of the newly created symlink</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1">
<tr>
<th align="right" valign="top">name:</th><td>  </td><td>The name for the new symlink, defaults to the name of the
target item</td>
</tr><tr>
<th align="right" valign="top">label :</th><td>  </td><td>The label of the symlink, defaults to 'Symlink to
&lt;target_item_name&gt;'</td>
</tr><tr>
<th align="right" valign="top">target_id:</th><td>  </td><td>The item which the symlink will point to</td>
</tr><tr>
<th align="right" valign="top">parent_id:</th><td>  </td><td>The parent folder for the symlink. This must actually be a
folder and not a generic content item.</td>
</tr><tr>
<th align="right" valign="top">symlink_id:</th><td>  </td><td>The id of the new symlink. A new id will be allocated by
default</td>
</tr><tr>
<th align="right" valign="top">creation_date:</th><td>  </td><td>As in <tt>acs_object.new</tt>
</td>
</tr><tr>
<th align="right" valign="top">creation_ip:</th><td>  </td><td>As in <tt>acs_object.new</tt>
</td>
</tr><tr>
<th align="right" valign="top">creation_user:</th><td>  </td><td>As in <tt>acs_object.new</tt>
</td>
</tr>
</table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
function new (
name in cr_items.name%TYPE default null,
label in cr_symlinks.label%TYPE default null,
target_id in cr_items.item_id%TYPE,
parent_id in acs_objects.context_id%TYPE,
symlink_id in cr_symlinks.symlink_id%TYPE default null,
creation_date in acs_objects.creation_date%TYPE
default sysdate,
creation_user in acs_objects.creation_user%TYPE
default null,
creation_ip in acs_objects.creation_ip%TYPE default null
) return cr_symlinks.symlink_id%TYPE;
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>acs_object.new, content_item.new, content_symlink.resolve</td>
</tr>
</table><p> </p><ul><li>
<font size="+1">Function:</font> content_symlink.resolve</li></ul><p>Resolves the symlink and returns the target item id.</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Karl Goldstein</td>
</tr><tr>
<th align="left">Returns:</th><td align="left">The target item of the symlink, or the original
item id if the item is not in fact a symlink</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1"><tr>
<th align="right" valign="top">item_id:</th><td>  </td><td>The item id to be resolved</td>
</tr></table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
function resolve (
item_id in cr_items.item_id%TYPE
) return cr_items.item_id%TYPE;
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>content_symlink.new, content_symlink.is_symlink</td>
</tr>
</table><p> </p><ul><li>
<font size="+1">Function:</font>
content_symlink.resolve_content_type</li></ul><p>Gets the content type of the target item.</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Michael Pih</td>
</tr><tr>
<th align="left">Returns:</th><td align="left">The content type of the symlink target, otherwise
null. the item is not in fact a symlink</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1"><tr>
<th align="right" valign="top">item_id:</th><td>  </td><td>The item id to be resolved</td>
</tr></table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
function resolve_content_type (
item_id in cr_items.item_id%TYPE
) return cr_items.content_type%TYPE;
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>content_symlink.resolve</td>
</tr>
</table><p> </p><ul><li>
<font size="+1">Procedure:</font> content_symlink.copy</li></ul><p>Copies the symlink itself to another folder, without resolving
the symlink</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Karl Goldstein</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1">
<tr>
<th align="right" valign="top">symlink_id:</th><td>  </td><td>The id of the symlink to copy</td>
</tr><tr>
<th align="right" valign="top">target_folder_id:</th><td>  </td><td>The id of the folder where the symlink is to be copied</td>
</tr>
</table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
procedure copy (
symlink_id in cr_symlinks.symlink_id%TYPE,
target_folder_id in cr_folders.folder_id%TYPE
);
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>content_symlink.new, content_item.copy</td>
</tr>
</table><p> </p><ul><li>
<font size="+1">Procedure:</font> content_symlink.delete</li></ul><p>Deletes the symlink</p><table cellpadding="3" cellspacing="0" border="0">
<tr>
<th align="left">Author:</th><td align="left">Karl Goldstein</td>
</tr><tr><th align="left" colspan="2">Parameters:</th></tr><tr><td></td></tr><tr><td align="left" colspan="2"><blockquote><table border="0" cellpadding="0" cellspacing="1"><tr>
<th align="right" valign="top">symlink_id:</th><td>  </td><td>The id of the symlink to delete</td>
</tr></table></blockquote></td></tr><tr><th align="left" colspan="2">Declaration:</th></tr><tr align="left"><td colspan="2" align="left"><pre><tt>
procedure delete (
symlink_id in cr_symlinks.symlink_id%TYPE
);
</tt></pre></td></tr><tr>
<th align="left" valign="top">See Also:</th><td>content_symlink.new, acs_object.delete</td>
</tr>
</table><p> </p>
Last Modified: $Id: symlink.html,v 1.1.1.1.28.1 2014/09/16 20:43:09
gustafn Exp $
</body>
www/doc/api/type.adp 0 → 100644
View file @ 8e2ff12b
This diff is collapsed.
www/doc/guide/convert.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Content Repository Developer Guide: HTML Conversion}</property>
<property name="doc(title)">Content Repository Developer Guide: HTML Conversion</property>
<master>
<body>
<h2>Converting Binary Documents to HTML</h2><p>The content repository uses the INSO libraries included with
Intermedia to support conversion of binary files such as Microsoft
Word documents to HTML. This document describes how to make this
conversion be part of the item creation or editing process, such
that the content is always stored in the repository as HTML.</p><p>
<b>Note:</b> Because temporary tables and LOB storage are used
during the conversion process, the entire process described here
must be performed within the context of a single transaction.</p><h3>Create the Revision</h3><p>The first step is to create the revision that will be associated
with the converted document, and obtain the corresponding ID. The
<tt>content</tt> column for the revision must be initialized with
an empty blob object:</p><pre>
revision_id := content_revision.new(item_id =&gt; :item_id,
revision_id =&gt; :revision_id,
data =&gt; empty_blob(),
title =&gt; 'My Word Document',
...);
</pre><h3>Uploading Binary Files</h3><p>The next step in the process is to upload the binary file into
the temporary table <tt>cr_doc_filter</tt>. This may be done using
any standard technique for uploading a binary file, such as an
image. The temporary table has only two columns; one is a BLOB to
store the document itself, and one is the revision ID.</p><h3>Converting the Document</h3><p>Once the revision has been created and the file has been
uploaded, the file may be converted to HTML and written into the
empty blob associated with the revision. This is done with the
<tt>to_html</tt> procedure in the <tt>content_revision</tt>
package:</p><pre>
begin
content_revision.to_html(:revision_id);
end;
/
</pre><p>Once the transaction is committed, the uploaded document is
automatically deleted from the <tt>cr_doc_filter</tt> table.</p><hr><a href="mailto:karlg@arsdigita.com">karlg@arsdigita.com</a><br>
Last Modified: $Id: convert.html,v 1.1.1.1 2001/03/13 22:59:26 ben
Exp $
</body>
www/doc/guide/items.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Content Repository Developer Guide: Creating Content
Items}</property>
<property name="doc(title)">Content Repository Developer Guide: Creating Content
Items</property>
<master>
<body>
<h2>Creating Content Items</h2><h3>Use the Content Item API to create the item</h3><p>Content items are initialized using the
<tt>content_item.new</tt> function. A name is the only parameter
required to create an item:</p><pre>
item_id := content_item.new( name =&gt; 'my_item' );
</pre><p>The name represents the tail of the URL for that content item.
In most cases you will want to create items in a particular context
with the repository hierarchy:</p><pre>
item_id := content_item.new(
name =&gt; 'my_item',
parent_id =&gt; :parent_id
);
</pre><p>The parent ID must be another content item, or a subclass of
content item such as a folder.</p><p>The <tt>content_item.new</tt> function accepts a number of other
optional parameters. The standard <tt>creation_date</tt>,
<tt>creation_user</tt> and <tt>creation_ip</tt> should be specified
for auditing purposes. You can also create the initial revision and
publish text items in a single step:</p><pre>
item_id := content_item.new(
name =&gt; 'my_item',
parent_id =&gt; :parent_id,
title =&gt; 'My Item',
text =&gt; 'Once upon a time Goldilocks crossed the street.
Here comes a car...uh oh! The End',
is_live =&gt; 't'
);
</pre><p>If either the title or text are not null, the function will
create the first revision of the item. It will also mark the item
as live if the <tt>is_live</tt> parameter is true. The alternative
to this one step method is to create a content item and then add a
revision using the Content Revision API.</p><h3>Publishing a content item</h3><p>If a content item has at least one revision, then it can be
published by calling the <tt>content_item.set_live_revision</tt>
procedure, which takes as input a <tt>revision_id</tt>:</p><pre>
content_item.set_live_revision( revision_id =&gt; :revision_id );
</pre><hr><a href="mailto:karlg@arsdigita.com">karlg@arsdigita.com</a><p>Last Modified: $Id: items.html,v 1.1.1.1 2001/03/13 22:59:26 ben
Exp $</p>
</body>
www/doc/guide/types.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Content Repository Developer Guide: Defining Content
Types}</property>
<property name="doc(title)">Content Repository Developer Guide: Defining Content
Types</property>
<master>
<body>
<h2>Defining Content Types</h2><p>The content repository requires you to define each type of
content supported by your supplication. Content types are defined
as <a href="?">ACS Object Types</a>, and may be created in the same
fashion as any other object type. This page provides some specific
examples and details related to defining ACS object types in the
context of the content repository.</p><h3>Determine content attributes</h3><p>A content item typically consists of two components:</p><ol>
<li>Text or binary data stored as a single object</li><li>Structured attributes stored as distinct values</li>
</ol><p>Note that a content type does <em>not</em> have to store its
primary content in the <tt>BLOB</tt> column of the
<tt>cr_revisions</tt> table. There is some additional overhead
associated with retrieving small passages of text from the BLOB
column compared to an attribute column. In most cases the
difference is trivial (fewer than about 10 microseconds), but if
many items must be queried at the same time the difference may
become significant. If the primary content will always be small, it
is perfectly acceptable to store the content in an attribute column
instead.</p><p>Basic attributes for all content types are stored in the
<tt>cr_revisions</tt> (note that they are stored in the revisions
table so that attributes may be updated for each new revision of
the actual data). Most types of content require more than the basic
attributes. For example, when storing images you will usually want
to store the pixel height and width so that images can be selected
and sorted by size, as well as displayed efficiently.</p><h3>Create an attribute table</h3><p>Extended attributes associated with ACS object types may be
stored as key-value pairs in a central table (generic storage), or
in a custom table whose primary key references the associated ACS
object ID (specific storage). To ensure efficient access to
attributes, the content repository API requires you to use specific
storage. Your table should have the form:</p><pre>
create table cr_<em>content_type</em> (
<em>content_type</em>_id integer
constraint cr_<em>content_type</em>_id_fk
references cr_revisions
constraint cr_<em>content_type</em>_pk
primary key,
<em>attributes</em>...
);
</pre><p>Note that your extended attribute table must reference the
<tt>cr_revisions</tt> table, <em>not</em><tt>cr_items</tt>. As
mentioned above, this allows you to maintain multiple revisions of
the attribute data in tandem with revisions of the content object
itself.</p><h3>Use the Content Type API to create the content type</h3><p>To define a content type, you should write an SQL script to
create the content type and then add attributes to it:</p><pre>
declare
attr_id acs_attributes.attribute_id%TYPE;
begin
-- create the content type
content_type.create_type (
content_type =&gt; 'cr_press_release',
pretty_name =&gt; 'Press Release',
pretty_plural =&gt; 'Press Releases',
table_name =&gt; 'cr_press_releases',
id_column =&gt; 'release_id'
);
-- create content type attributes
attr_id := content_type.create_attribute (
content_type =&gt; 'cr_press_release',
attribute_name =&gt; 'location',
datatype =&gt; 'text',
pretty_name =&gt; 'Location',
pretty_plural =&gt; 'Location',
column_spec =&gt; 'varchar2(1000)'
);
...
</pre><p>The <tt>content_type</tt> methods use the core ACS Object Type
API to create an object type for each content type, and to add
attributes to the object type. In addition,
<tt>content_type.create_type</tt> will create the extended
attribute table with an appropriately defined primary key column
(referencing its supertype) if the table does not already exist.
Likewise, <tt>content_type.create_attribute</tt> will add a column
to the table if the column does not already exist.</p><p>Most importantly, the <tt>content_type</tt> methods call
<tt>content_type.refresh_view</tt> after each change to the content
type definition. Each content type must have an associated
attribute view named <tt>
<em>table_name</em>x</tt>, where
<em><tt>table_name</tt></em> is the name of the extended attribute
table for a particular content type. The view joins the
<tt>acs_objects</tt>, <tt>cr_revisions</tt>, and all extended
attribute tables in the class hierarchy of a particular content
type. This view may be used to query attributes when serving
content.</p><h3>Creating compund items</h3><p>In many cases your content items will serve as containers for
other items. You can include the set of allowable components as
part of a content type definition. See <a href="object-relationships">Object Relationships</a> for
details.</p><hr><a href="mailto:templating@arsdigita.com">templating@arsdigita.com</a><p>Last Modified: $Id: types.html,v 1.1.1.1 2001/03/13 22:59:26 ben
Exp $</p>
</body>
www/doc/index.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {ACS Content Repository}</property>
<property name="doc(title)">ACS Content Repository</property>
<master>
<body>
<h2>ACS Content Repository</h2><ul>
<li><a href="design">Introduction</a></li><li><a href="install">Installation</a></li><li><a href="tutorial">Tutorial</a></li><li><a href="object-model">Object Model</a></li><li>
<p>Developer Guide</p><ul>
<li><a href="guide/types">Designing content types</a></li><li><a href="guide/items">Creating content items</a></li><li><a href="guide/revisions">Adding revisions to content
items</a></li><li><a href="guide/file-system">Organizing items in the
repository.</a></li><li><a href="guide/object-relationships">Relating content to
other objects.</a></li><li><a href="guide/template">Associating templates with
content items</a></li><li><a href="guide/publish">Publishing content</a></li><li><a href="guide/keywords">Categorizing content based on
keywords</a></li><li><a href="guide/search">Searching for content</a></li><li><a href="guide/convert">Converting binary documents to
HTML</a></li><li><a href="guide/access-control">Applying access
control</a></li><li><a href="guide/workflow">Applying workflow to content
items</a></li>
</ul>
</li><li>
<p>Object Reference</p><ul>
<li>Unpackaged: <a href="api/content">Content</a>
</li><li>Packages
<ul>
<li><a href="api/type">Type</a></li><li>
<a href="api/item">Item</a><ul>
<li><a href="api/folder">Folder</a></li><li><a href="api/symlink">Symbolic Link</a></li><li><a href="api/extlink">External Link</a></li>
</ul>
</li><li><a href="api/template">Template</a></li><li><a href="api/keyword">Keyword</a></li><li><a href="api/permission">Permission</a></li><li><a href="api/revision">Revision</a></li>
</ul>
</li>
</ul>
</li><li><a href="uninstall">Uninstalling the content
repository</a></li>
</ul><hr><a href="mailto:karlg@arsdigita.com">karlg@arsdigita.com</a><br>
Last Revised: $Id$
</body>
www/doc/intermedia.adp 0 → 100644
View file @ 8e2ff12b
<property name="context">{/doc/acs-content-repository {Content Repository}} {Content Repository: Testing Intermedia}</property>
<property name="doc(title)">Content Repository: Testing Intermedia</property>
<master>
<body>
<h2>Testing Intermedia</h2><p>Even if you follow the instructions in the <a href="install">installation notes</a>, content searches may
inexplicably fail to work. This document describes how to create a
simple test case independent of the content repository to verify
that Intermedia is indeed functioning properly.</p><h3>Create a document table</h3><p>Create a simple table to hold some test documents:</p><pre>
create table cr_test_documents (
doc_id integer primary key,
author varchar2(30),
format varchar2(30),
title varchar2(256),
doc blob
);
</pre><p>Create an Intermedia preference to specify INSO filtering:</p><pre>
begin
ctx_ddl.create_preference
(
preference_name =&gt; 'CONTENT_FILTER_PREF',
object_name =&gt; 'INSO_FILTER'
);
</pre><p>If this preference has already been created, this step will
cause an error that you can ignore.</p><p>Create an Intermedia index on the test table with INSO
filtering:</p><pre>
create index cr_test_documents_idx on cr_test_documents ( doc )
indextype is ctxsys.context
parameters ('FILTER content_filter_pref' );
</pre><h3>Load test documents</h3><p>You can use SQL*Loader to load some documents into the test
table. First create a control file named
<tt>cr-test-docs.ctl</tt>:</p><pre>
load data
INFILE 'cr-test-docs.data'
INTO TABLE cr_test_documents
APPEND
FIELDS TERMINATED BY ','
(doc_id SEQUENCE (MAX,1),
format,
title,
ext_fname FILLER CHAR(80),
doc LOBFILE(ext_fname) TERMINATED BY EOF)
</pre><p>Copy any number of documents (Microsoft Word, PDF, text, HTML,
etc.) to the file system of your database server. Create a data
file with an entry for each document you would like to load. This
is simply a comma-separated text file:</p><pre>
word, Simple Story,sample-docs/simple.doc,
excel, Simple Spreadsheet,sample-docs/simple.xls
</pre><p>Load the documents from the command line:</p><pre>
$ sqlldr userid=cms/cms control=cr-test-docs.ctl log=cr-test-docs.log
SQL*Loader: Release 8.1.6.2.0 - Production on Thu Nov 9 13:36:56 2000
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Commit point reached - logical record count 2
</pre><h3>Test search</h3><p>Once the documents have been loaded, rebuild the index and run
some test queries:</p><pre>
SQL&gt; alter index cr_test_documents_index rebuild online parameters ('sync');
SQL&gt; select score(1), doc_id from cr_test_documents
where contains(doc, 'cars', 1) &gt; 0;
SCORE(1) DOC_ID
---------- ----------
4 1
</pre><hr><a href="mailto:karlg@arsdigita.com">karlg@arsdigita.com</a><br>
Last revised: $Id: intermedia.html,v 1.1.1.1 2001/03/13 22:59:26
ben Exp $
</body>
www/doc/requirements.adp 0 → 100644
View file @ 8e2ff12b
This diff is collapsed.
www/doc/tutorial.adp 0 → 100644
View file @ 8e2ff12b
This diff is collapsed.
www/index.adp 0 → 100644
View file @ 8e2ff12b
<master>
<property name="doc(title)">Content Item Not Found</property>
<h1>Content Item Not Found</h1>
The requested item is not available for viewing.
The item is either not available on this server or it is not in a publishable state.<br>
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment