Dear Alexander, On 05/02/2012 1:41 PM, Alexander Wagner wrote: > If I set CFG_WEBSEARCH_INSTANT_BROWSE, I get a list of all recent > addtions to a given collection. This works fine here. However, I do not > undertand where I can adopt it's output format. It seems that certain > records get a HB-like format applied. It also seems that this is a > static format. Probably I should recreate it? But it can't be HB as I > don't run bibreformat by default on our test system.
In principle CFG_WEBSEARCH_INSTANT_BROWSE should have no effect on the display of the records, but would only alter the number of records featured in the "Latest additions" box on collection (splash) pages, unless there is some sort of unexpected behaviour. So I am assuming this is unrelated. The records in the "Latest additions" box are displayed using the HB format (cached, or not). If you click on the "Search" button of the collection splash page, you should in principle see the same formatting of the records. If the displays are not synchronized, it could be that the format of the records has been updated AFTER the collection splash page was refreshed by WebColl. You can refresh the collection splash page with the WebColl '--force' option: $ webcoll --force -c "Meine Sammlungen" -p2 $ bibsched # check that task has run You can also get more info about the status of the formatting of the records if you click on "Search" in the given collection, and add "&verbose=9" as parameter to the URL. Note that when no corresponding format can be found for a record (erroneous config or unrecoverable failure somewhere in the formatting chain) a "basic" fail-safe formatting of the record is applied using a Pythonic template, which can be found in websearch_templates.tmpl_print_record_brief(..). A similar function exists for HD in websearch_templates.tmpl_print_record_detailed(..). If this format seem to be used the case should be investigated in more details (you could customize the above function to add some debug message and check if it is indeed used). The context in which the records are displayed might also affect their look: records are encapsulated in different HTML markups in search results and splash pages, maybe with different CSS depending on some possibly fancy Pythonic template customization/overriding. This could explain minor variations of the display (small/bigger fonts, etc.) Check the HTML to spot differences, if any. I hope the above provides a good start to investigate further. Best regards -- Jerome Caffaro ** CERN Document Server ** <http://cds.cern.ch/>
