Revision as of 18:14, 4 August 2005 (view source) Marek (talk | contribs) m (Content - Pulling Out, Feeding In, Pooling moved to Content - Import, Pulling Out, Feeding In, Pooling, Syndication) ← Older edit		Revision as of 18:17, 4 August 2005 (view source) Marek (talk | contribs) (→‎Internal Content Pooling) Newer edit →
Line 9:		Line 9:
	== Internal Content Pooling ==		== Internal Content Pooling ==
	<aafaq id=1748> ~ToDo: 1748 How do feed items from one slice to another </aafaq>		<aafaq id=1748> ~ToDo: 1748 How do feed items from one slice to another </aafaq>
		+	=== Internal content pooling example ===
		+	<aafaq id=1761>I want to feed highlighted items from several slices to the front page</aafaq>
	== Cross Server Content Exchange ==		== Cross Server Content Exchange ==

---

Revision as of 18:17, 4 August 2005

Getting Data In

Importing data from static sources

CSV import

Writing your own import script

Offline client

How to set the off-line filling up?

The offline filling currently works only in IE with Java support (there are some problems with Netscape and file manipulation permissions).

All files used for off-line filling are stored in /mics/offline2slice directory. All of them should be copied to local computer, where you want to use offline filling. There are a few steps to do for sucessfull installation.

1. Create directory on your local computer (default is c:java).
2. Copy files from /mics/offline2slice directory of apc-aa installation to created directory.
3. Add row "set classpath=c:java" to your autoexec.bat file, in order java finds the class definitions.
4. Restart computer in order the changes in autoexec.bat tekes efect.
5. Open the delete_file.html file and change the location of main filling form
   row 11: document.location='c:\java\fillform.html';
   
6. Change the location of the file, where form data are stored
   row 19: <PARAM NAME="filename" VALUE="C:\offlinedata.txt">
7. Open the file fillform.html and modify it in order to have the same fields as your slice have. The fields are identified by its ids (like 'headline........'), known from AA.
8. Change the parameter to OffLine2Slice applet to point to the file, where the content of filled forms will be locally stored
   row 240 <PARAM NAME="filename" VALUE="C:\offlinedata.txt">
9. Change the URL in ACTION atribut of second form at fillform.html page to point to your server with ActionApps
   row 356: <FORM NAME="hidden_form" ACTION="http://aa.ecn.cz/aaa/offline.php3" METHOD="post">
10. Change slice_id in hidden form input to match your slice, where you want to store item
    row 358: <INPUT NAME="slice_id" TYPE="hidden" value="45636f6d6f6e69746f72427942455a4c">
11. Change the path to delete_file.html to point to your install directory, where the file is stored
    row 361: <INPUT NAME="del_url" TYPE="hidden" VALUE="C:/java/delete_file.html">

The offline filling is now installed on your computer and you can try it (open your local fillform.html file in your browser). There you can fill as many items as you want and after all send it to the server.

Before sending the filled forms to server make you sure, that the slice you want import to, permit this operation (see 'Admin' - 'Slice' - 'Allow off-line item filling').

After the sucesfull sneding the items to server, your browser should be redirected to the page, where you can delete the file (offlinedata.txt). In this file the filled data are locally stored. The deletion is not necessary - the offline filling script offline.php3 will recignize, if the data for each item is already stored in database or not (the CRC for each item is computed). However, the better practice is to delete the file. This saves the capacity of line, because the data will not be transfered to server for second time.

Other documentation

Email To ActionApps

RSS Import

Internal Content Pooling

How do feed items from one slice to another

There are two feeding methods - authomatical and manual. Automatical feeding works only for new/updated item. By manual feeding it is possible to feed any selected item to another slice (if you have permission to do so).

Manual feeding
In Item Manager select the items you want to send to another slice. Select "Export" on the toolbar just below the itemlist. After clicking on "GO" a new window is shown where you can select destination slices. (You must have a permission in the destination slice - at least Author. If you are Editor or more in the destination slice, you can set the "Active" checkbox, which means to copy the items in the destination slice into the Active Bin. If the checkbox stays unchecked, the item is copied to the Holding bin).

The feeding is error-safe, it is impossible to feed one item to the same destination slice more than once.

Automatical feeding

Each Feed needs to be configured in both the slice where the items are entered and which will export items, and for the slice where the items are imported.

Select the slice where the items are entered. Select Admin->Content Pooling -> Inner Node Feeding. If you are willing for items to go to any other slice on the same host then check "Enable export to any slice". Otherwise uncheck this box, and move slices that you want to receive items to the Export Enable box.

Select the slice where items will be received. Make sure the slice you want to recieve from is in the Import box. As a courtesy send an email to the administrator of the slices you want to receive from.

The import process can be fine tuned in two ways.

In Admin->Content Pooling->Filters you can select which of the exporting slice's categories items come from, and to which categories of the importing slice they are delivered. Select the Active box if you want items in this category to be made Active, otherwise they will go in the Holding Bin for manual approval. There is currently no way to control which items are fed, only which category they go to.

In Admin->Content Pooling->Mapping you can control which fields of the source slice end up in which fields of the destination slice.

If you want to export items already in the slice, then go to the Item Manager, check the items to export, and choose "Export" and Go. This will give a choice of destination slices, which you can check along with whether they should be Active, or go to the Holding Bin for manual approval.

Internal content pooling example

I want to feed highlighted items from several slices to the front page.

There is solution for 'Internal feeding':

It could be done using field 'Mapping' ('Slice Admin -> Mapping').
One of the possibilities there is to select '-- Value --' for a field. The 'Value' is not ony static text, but you can use any AA alias construct there (just like: <a href="{source_href.....}">{source..........}</a>).

The solution is to specify such expression for 'status_code' field (which controls, in which bin resulting items appear:
1 - Approved
2 - Holding bin
3 - Trash
4 - Item is not fed

So, if you specify something like:

{switch({highlight.......})1:1:4}

for status_code field, only highlighted fields are fed (into Approved).


There is no way to do it for external (Inter Node or RSS) feeds. The only solution there is to feed all the items into one slice
and then show only highlighted items in destination slice (the
highlighted flag will be copied too, so there is no need for manual setting "highlighted" in destination slice)

Cross Server Content Exchange