On Thu, 14 Nov 2013, [email protected] wrote: > somehow, although since the is really no interface for the user to set them > via the web interface it's kind of a bug that the bibtask relies on these > value to be set in the DB when there are already config files to describe > which jobs are needed.
BibExport configuration files can be thought of as examples. E.g. there is MARCXML job example that people probably don't want to run on production sites. Hence the sole presence of these configuration files is not enough to `activate' them... If we would like to change this and rely on the presence of configuration files, which I consider nice as well, then some of them should not be installed and/or defaults should be changed for some of them... Otherwise there is an easy risk that people forget to customise them. Best regards -- Tibor Simko
