Wolfgang Pichler wrote:
sorry to come up late - ready for fighting in community in oct, not aug
as i intended ...
( as i see david is _very_ active for the sake of all the project -
thank you a lot !!! )
Good to have you back in business =)
---
regarding barcodes i will have to use a bulk print system using
_kbarcode_ since ther will be no mature system in 1.2 alas ...
Is barcode type diversity still the main issue, or are you thinking of
something larger in terms of a "mature" barcode (printing) system?
SO
for BOOKS it would be nice to have added :
- table "books" : field "barcode_printed tynint unsigned NOT NULL
default '0' "
- some assurance that such a field won't interfere with the system
- field established in "deleted_books" accordingly
i do not think this will be a _too_big_ enhancement going into 1.2 :-)
No, it's not a big enhancement, but I'm not sure it fits within the
current barcode system. I.e. whether it is something useful for Emilda
in general or just a tweak for your case. When and how would you exactly
populate this field, what would you do with the data, and why do you
need it? I can imagine a scenario, but I would like to make sure we're
talking about the same thing.
---
[[ off topic :
for USERS we will have some sort of activation system with :
- preprinted user-cards showing up code39 -c "card_id"
- preprinted labels with am autogenerated unique activation-barcode
which links to external data which will be fed into
emilda's user/group tables every year
mechanism :
- users are deactivated at the end of each (school-) year
- at the beginning of the year all the data of all users (of all
classes) will be
- fed into some db-space with primary key "activation-id" for every
(potential) user
- labels are printed containing name, year,class,barcode /w activation-id
and deposited ready for use of the library-administrator
- if an "old" user wants to use the library
- he will pesent his "old" id-card and receive a "new" label affixed on
the card
- library-administrator will start some little gui, read activation-id
and card-id
this utility will tweak emilda's databases, voila, user is able to
use the library for 1 more year
- same for a new user which will receive his/her "new" id-card
if you want to share your thougts about such a system you are welcome.
Why do you need to replace the id and use an activation code? Wouldn't
it be easier just to disable/enable the user's account in Emilda (and
use the same id every year)? Do you mean that data will be erased every
year and just basic user information imported again when the user is
reactivated (user history will be lost)? If not, why do you want to
export/import data in the first place? I'm not sure I follow your
intentions here, but it's getting late in the evening and I'm tired =)
]]
---
greetings
w.pichler
_______________________________________________
Emilda mailing list
Emilda@xxxxxxxxxxxxxxxxxx
http://lists.realnode.com/mailman/listinfo/emilda
At least we'll get some discussion going... =)
Regards,
--
Erik Berglund
Partner, Marketing
Oy Realnode Ab
lastname@xxxxxxxxxxxx
www.realnode.com
|
