Hi Jérôme, first of all, thank you for your patience so far...
[...] > (We use the convention to start output formats that produce HTML with > the letter 'H' AB -> HAB or HBA...) [Good advices that I appreciate and I have to evaluate further...] >> Summing up, we have something that works *except* the first cached >> page. So I may have to change the hardcoded 'hb' in line 397 according >> to the self.name collection name (out of the loop, that is). > > But if I understand well, AB is not chosen by default when you hit the > search button, is that true? Au contraire! If I hit the search button, I get my own nice authority format, either brief or full according to the context, whether it is a list of records or a particular one. The *only*, single case where it does not work is the first, cached page. > (In general it would be interesting to be able to define a default > output format for a given collection) That's what I was thinking myself. (More about it below.) >> [..] we like a presentation more gallery-like, such as this: >> http://pares.mcu.es/cartelesGC/AdminControlServlet?COP=6 >> >> [..] Are we dreaming too much? Do you have any suggestion or future plans? > > It shouldn't be too difficult. There is already the "portfolio" format > to achieve a similar effect: > <http://invenio-demo.cern.ch/search?cc=Pictures&of=hp> > <http://cdsweb.cern.ch/search?cc=Photos&rg=50&of=hp> Great! That's exactly what we want. But again, we hit the same problem: how to define this «portfolio» format as the default one when you visit the collection page? With so many options in the Edit collection admin pages, don't you think it would be useful and easier to administer? As much as I appreciate (and I really do!) to edit the *.btf (format templates) and bfe_*.py (bibformat_elements) files from an editor, and having all kinds of fancy version control tools at my disposal, I don't really understand the role of those *.bfo (output format) files, and why they cannot live in the database and be selected like the search fields or sort options by a librarian, with a default one and (optionally) a special choice. I'm unable to see why living in the filesystem is better in that case. My two cents, Ferran
