Copy any number of documents (Microsoft Word, PDF, text, HTML, -etc.) to the file system of your database server. Create a data +etc.) to the filesystem 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:
word, Simple Story,sample-docs/simple.doc, Index: openacs-4/packages/acs-content-repository/www/doc/intermedia.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/intermedia.html,v diff -u -N -r1.2 -r1.2.2.1 --- openacs-4/packages/acs-content-repository/www/doc/intermedia.html 7 Aug 2017 23:47:47 -0000 1.2 +++ openacs-4/packages/acs-content-repository/www/doc/intermedia.html 5 Apr 2021 19:49:48 -0000 1.2.2.1 @@ -60,7 +60,7 @@ doc LOBFILE(ext_fname) TERMINATED BY EOF)
Copy any number of documents (Microsoft Word, PDF, text, HTML, -etc.) to the file system of your database server. Create a data file +etc.) to the filesystem 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:
Index: openacs-4/packages/acs-content-repository/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/requirements.adp,v diff -u -N -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-content-repository/www/doc/requirements.adp 30 Apr 2018 08:15:07 -0000 1.4 +++ openacs-4/packages/acs-content-repository/www/doc/requirements.adp 5 Apr 2021 19:49:48 -0000 1.4.2.1 @@ -133,14 +133,14 @@40.10. The data model must support the hierarchical organization of content items in a manner similar to a -file system.
+filesystem.
40.20. The URL of a content item should reflect its location in the hierarchy. For example, a press release with the URL /press-releases/products/new-widget is located at the third level down from the root of the hierarchy.
A folder is analogous to a folder or directory in a -file system. It represents a level in the content item hierarchy. +filesystem. It represents a level in the content item hierarchy. In the previous example, press-releases is a folder under the repository root, and products is folder within that. The description of a folder may include the following @@ -160,7 +160,7 @@
40.30.5 Content Symbolic Link.
40.30.5.10. A
@@ -315,7 +315,7 @@
100.50 Content Folders The repository should allow for hierarchical arrangement of
-content items in a manner similar to a file system. The API to meet
+content items in a manner similar to a filesystem. The API to meet
this general requirement focuses primarily on content folders:
Index: openacs-4/packages/acs-content-repository/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/requirements.html,v
diff -u -N -r1.3 -r1.3.2.1
--- openacs-4/packages/acs-content-repository/www/doc/requirements.html 7 Aug 2017 23:47:47 -0000 1.3
+++ openacs-4/packages/acs-content-repository/www/doc/requirements.html 5 Apr 2021 19:49:48 -0000 1.3.2.1
@@ -166,8 +166,7 @@
40.10. The data model must support the hierarchical
-organization of content items in a manner similar to a file
-system.
40.20. The URL of a content item should reflect its location in the hierarchy. For example, a press release with the URL @@ -176,8 +175,7 @@
-A folder is analogous to a folder or directory in a file -system. It represents a level in the content item hierarchy. In the +
A folder is analogous to a folder or directory in a filesystem. It represents a level in the content item hierarchy. In the previous example, press-releases is a folder under the repository root, and products is folder within that. The description of a folder may include the following information:
@@ -204,7 +202,7 @@40.30.5 Content Symbolic Link.
A symbolic link is analogous to a symlink, alias or -shortcut in a file system. The description of a symbolic link must include +shortcut in a filesystem. The description of a symbolic link must include the following information:
40.30.5.10. A URL-encoded name for the symbolic link. As @@ -394,7 +392,7 @@
100.50 Content Folders
The repository should allow for hierarchical arrangement of content -items in a manner similar to a file system. The API to meet this +items in a manner similar to a filesystem. The API to meet this general requirement focuses primarily on content folders:
Index: openacs-4/packages/acs-content-repository/www/doc/tutorial.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/tutorial.adp,v diff -u -N -r1.6.2.1 -r1.6.2.2 --- openacs-4/packages/acs-content-repository/www/doc/tutorial.adp 14 Aug 2019 07:34:35 -0000 1.6.2.1 +++ openacs-4/packages/acs-content-repository/www/doc/tutorial.adp 5 Apr 2021 19:49:48 -0000 1.6.2.2 @@ -537,7 +537,7 @@ The content repository also has a very useful facility for organizing your data into a hierarchy, very similar to a -file-system. Just like a file system, you can have folders to store +file-system. Just like a filesystem, you can have folders to store items inside of, and organize your information. The main difference is that every item can also contain other items. So in our case, we can have tasks that contain other tasks. This is a useful way for @@ -771,13 +771,12 @@ attributes.Using this structure is optional, but useful in many circumstances.
@@ -733,9 +733,9 @@
Determines if the item is a extlink
| Author: | Karl Goldstein | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Returns: | 't' if the item is a extlink, 'f' + | Returns: | 't' if the item is an extlink, 'f' otherwise | |||||||||||||||||||
| Parameters: | ||||||||||||||||||||||
| ||||||||||||||||||||||