OpenACS Content Rep Tables

The content repository is used to store different kinds of content objects. It is not very much used by ]po[. For more information please see the OpenACS documentation.

 


Table

Cols

Rows

Description

[cr_child_rels]

5

57

Provides for richer parent-child relationships than the simple link encapsulated in the primary table. May be subclassed to provide additional attributes.

[cr_content_mime_type_map]

2

7

A mapping table that restricts the MIME types associated with a content type.

[cr_content_text]

2

0

A temporary table for holding text extracted from the content blob. Provides a workaround for the fact that blob_to_string(content) has 4000 character limit.

[cr_doc_filter]

2

0

A temporary table for holding binary documents that are to be converted into HTML (or plain text) prior to insertion into the repository.

[cr_dummy]

1

0

Not used anymore

[cr_extension_mime_type_map]

2

261

a mapping table for extension to mime_type in db version of ns_guesstype data

[cr_extlinks]

4

0

Extlinks are pointers to items anywhere on the web which the publisher wishes to categorize, index and relate to items in the content repository.

[cr_files_to_delete]

2

0

Table to store files to be deleted by a scheduled sweep. Since binaries are stored in filesystem and attributes in database, need a way to delete both atomically. So any process to delete file-system cr_revisions, copies the file path to this table as part of the delete transaction. Sweep run later to remove the files from filesystem once database info is successfully deleted.

[cr_folder_type_map]

2

16

A one-to-many mapping table of content folders to content types. Basically, this table restricts the content types a folder may contain. Future releases will add numeric and tagged constraints similar to thos available for content types.

[cr_folders]

6

5

Folders are used to support a virtual file system within the content repository.

[cr_item_keyword_map]

2

102

 

[cr_item_publish_audit]

6

28

An audit table (populated by a trigger on cr_items.live_revision) that is used to keep track of the publication history of an item.

[cr_item_rels]

5

27

Describes all relations from one item to any number of other objects.

[cr_item_template_map]

3

0

Allows a template to be assigned to a specific item.

[cr_items]

11

593

Each content item has a row in this table, as well as a row in the acs_objects table. The parent_id is used to place an item in a directory or place it within another container item.

[cr_keywords]

6

13

Stores a subject taxonomy for classifying content items, analogous to the system used by a library.

[cr_locales]

5

1

Locale definitions in Oracle consist of a language, and optionally territory and character set. (Languages are associated with default territories and character sets when not defined). The formats for numbers, currency, dates, etc. are determined by the territory.

[cr_mime_types]

3

165

file_extension is not used to recognize MIME types, but to associate a file extension to the file after its MIME type is specified.

[cr_release_periods]

3

0

 

[cr_revision_attributes]

2

0

 

[cr_revisions]

10

628

Each content item may be associated with any number of revisions. The item_id is used to associate revisions with an item.

[cr_scheduled_release_job]

2

0

One-row table to track job ID of scheduled release update.

[cr_scheduled_release_log]

5

0

Maintains a record, including any exceptions that may
have aborted processing, for each scheduled update of live content.

[cr_symlinks]

3

0

Symlinks are pointers to items within the content repository.

[cr_template_use_contexts]

1

2

A simple table (for now) for constraining template use contexts.

[cr_templates]

1

1

Templates are a special class of text objects that are used for specifying the layout of a content item. They may be mapped to content types for defaults, or may be mapped to individual content items.

[cr_text]

1

0

A simple placeholder table for generating input views, so that a complete revision may be added with a single INSERT statement.

[cr_type_children]

5

0

Constrains the allowable content types which a content type may contain.

[cr_type_relations]

5

1

Constrains the allowable object types to which a content type may relate (see above).

[cr_xml_docs]

2

0

A temporary table for holding uploaded XML documents for the duration of a transaction, until they can be inserted into the content repository.

[cr_type_template_map]

4

3

A simple mapping template among content types and templates. Used to determine the default template to use in any particular context, as well as for building any UI that allows publishers to choose from a palette of templates.

[lob_data]

4

44

 

[lobs]

2

22

 

[user_portraits]

1

0

"Portrait" content type to store users's images.

  Contact Us
  Project Open Business Solutions S.L.

Calle Aprestadora 19, 12o-2a

E-08907 Hospitalet de Llobregat (Barcelona)

 Tel Europe: +34 932 202 088
 Tel US: +1 415 429 5995
 Mail: info@project-open.com