Am 29.06.2011 14:20, schrieb Jerome Caffaro:
Hi!
[...]
It will just miss the following bit of information (stored
in the DB):
1. The content-type used to serve the output format.
This is the one most cricital.
2. The visibility bit switching on/off the output format on the user
search interface (hidden does not mean that the output format is
not available: it is just not in the list).
3. Names and description (mostly useful when format is visible).
Han happily live without those.
(1) is the most annoying but can be worked around in some cases by
using the fact that some default content-type is used depending on the
first letter of the output format code:
- 'h': text/html
- 't': text/plain
- 'x': text/xml
This is the missing piece of information on my end. In
this case I can just name them accordingly and all is fine.
(And I'll add this as a first stanza to the upcoming doc ;)
(2) and (3) can be "worked around" thanks to the fact they
are more or less only here for information (this is mostly
true for (3)), and also because these values are not often
changed: if you keep the output format files in some repo
and periodically deploy the changes by copying the files
to your production environment, there are chances that
most of the time you want to keep (2) and (3) as they were
on the production server (don't change the values in the
DB).
I agree with this. The deployment here is a deployment on
several boxes on various locations spread over Germany,
that's why I'd like to come to some automatism. I do
something here, tell the gang "run make install" and it
should be fine as it's mostly backend stuff.
It is also not frequent that somebody wants to add new
output formats, compared to the need to update them (which
is in this case well covered with the current
implementation).
Of course one can imagine moving (1), (2) and (3) inside
the output format files. But do you see any use case for
which the above is not exactly suitable?
The above is sufficient, indeed. I missed the important
point with the naming convention for triggering the
content/type. For some connections I need text/plain
explicitly.
--
Kind regards,
Alexander Wagner
Subject Specialist
Central Library
52425 Juelich
mail : [email protected]
phone: +49 2461 61-1586
Fax : +49 2461 61-6103
http://www.fz-juelich.de/zb/mitarbeiter/fachinformation#wagner
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDirig Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Besuchen Sie uns auf unserem neuen Webauftritt unter www.fz-juelich.de
