JCollection Homepage

Hi,
and thanks for continously testing and giving feedback, I appreciate that!
Let me shed some light on the two things you observe, and they are indeed somewhat wanted. The first observation is that there are description fields for an item, and also for an info set. In a normal setup, the info set will overwrite the item description, hence only the info set description would be needed. This leads to the problem that if the item description is given and also the info set description, this information would be displayed twice - once for the item, and once for the info set. To avoid that, there is a parameter "show item" which can be switched off, such that only the info set information are displayed.
The second problem you mention is that Amazon editorial reviews might be doubled as well. This is a different matter. JCollection has two ways of displaying Amazon editorial reviews: they are used for description overwrites, meaning they appear in the webservice type and are fetched according to the entry there (which is called description XPath). The advantage of this approach is that it fills the description field. The disadvantage is that it might not look so goot when parts of information are missing (source of the review or date, that might lead to "()", which does not look very nice). The second way of displaying editorial reviews is completely separate and triggered via the "show editorial reviews" parameter (advantage: displays nicely, disadvantage: does not fill the description field). So, if this parameter is set and the webservice types are set up like they are after installation, then the editorial reviews are doubled.
To justify this rather complicated setup: when I introduced the old Collection Manager, there were many people asking if the component could do this or that, and in most cases it couldn't. So this time with JCollection I wanted to produce something very, very flexible to suit almost everybody's need - but with sensible default settings, of course. The cost is that the complexity needs some very good - yet to be written - manual.
Thorsten.

Ahh,

thanks for the detailed explanation. I understand.

Certainly it is a problem to find the right balance between functions and complexity.

So two questions still remains.

1.)
How can i force JCollection to show the saved "info set description" instead of the "Amazon description overwrite" ? I thought the Option "Description overwrite" where responsible for this, but it seems that this option didn´t work .

2.)
You said : "In a normal setup, the info set will overwrite the item description, hence only the info set description would be needed"
Then why the "Permanent Overwrite" function fills both fields ?

Hi,
to your questions:
1. The "description overwrite" parameter for info sets is indeed responsible. If you leave it empty, the global standard value for this parameter is used, and if this is also empty, then all webservices are probed (in a given order). So, to switch overwrite off for a specific info set, set the description overwrite parameter to "none". To switch it off globally, set the global parameter to "none". Then you'd have to activate it in each info set where you want to use it, for example "amazon,isbndb" would first query Amazon and then, if no description was found, ISBNdb (if the parameters for these two webservices are set, of course).
2. The "permanent overwrite" takes exactly the same steps as the display function, hence if the item description is overwritten by info set description, then it will be stored like that. In other words, the final result is stored, after all overwrites are done. Of course there are item parameters that control how info set information overwrites item information, and the permanent overwrite also obeys these settings. So, you can switch that off if it is not desired.
Thorsten.

Hi,

ok it seems i have to play a little bit with all kinds of options.

But, for one item i changed the option "Title overwrite" under the "Parameters - Overwrites" area to "No" and set "Webservice overwrites" under "Parameters - Item" to "none".

The Global Parameter "No overwrite in category or list view" is set on "Yes"

It is not a worse problem. But when i watched the detailview for this item in the frontend, the titel is not hyperlinked to the original Amazon-Titel unlike other items. So it seems JCollection still takes the titel for this item from the infoset. Do in understand the option "Title overwrite" wrong or is it a little bug ?

Hi,
the hyperlink is more related to the "overwrite url" setting, since it links to this url. BTW, the "webservice overwrite" item-parameter acts as a default value for all webservice overwrite info set-parameters (and default for this is the global value).
HTH,
Thorsten.