Christoffer Landtman wrote:
Wolfgang Pichler wrote:
[snip]
Not really. I cannot quite remember your initial reasoning behind
using external printing and label management, but maybe this is not
the right time to discuss that. If you want to be entirely sure, I
would suggest that you use a separate table to gather your custom
data, and then only in your external program link it into the Emilda
tables. This is however only an idea!
reason ist that default fields give a pretty easy starting point for
external processing (i have initial values without to have to scan all
books and/or keep a "shadow" table)
i produce very complex labels (actually combined barcode/spine-labels
with rich info on them)
i generate via PDF::Reuse a pdf-file and the operator must commit the
batch after it is actually printed
for the user-activation-system which de-facto does the same as emilda's
ldap i use shadow-tables since the task is relatively complicated (you
can review it and put it on the net as goodie BUT as i am a
perl-programmer, it is perl, not php :-)
so, for the spine-labels i will just need one status-field in books to
indicate if label is produced/printed.
same for inventory because at will it will be needed to indicate if book
is still in shelf (and which one).
Please let us know how it went ;-)
i'll do it - i'll really do it - no matter *fg*
l.g.
wolfgang
|
