Another thing that differentiates you from other small libraries
attempting this sort of thing is your contacting of this list. Most of
the readers here are used to big-data problems, where they're trying
to make sense of the storage, maintenance, and display of millions of
records, so it's
Interesting point about the checkout history. Not displaying it
automatically is probably a good idea. I wouldn't drop that info though, or
obscure it in the DB.
@brice: good point, its on the list now
University of Texas is switching to django for all of their internal DB
stuff like accounting and payroll for reasons that are obvious to anyone
has used django.
Huh? Django may be great, but this seems highly unlikely.
I may very well
It was at the end of last year that I came here saying I was writing an open
source ILS for a distributed (book sharing) library. While I had lots of
enthusiasm and time for it at the time, our development computer didn't have
the capacity to run a solr based discovery front end. Even
What's wrong with the library world developing its own domain language?
We're already in a world of pain because we have our own data formats and
ways of dealing with them, all of which have basically stood idle while 30
years of advances computer science and information
Congratulations on discovering python. It will serve you much better
than php, or any other scripting language.
Skipping to the punch-line, you should dive into python before you
dive in django:
You will have a very much more easy time if you learn how to debug a
my first project in python involved capturing keyboard input before
windows heard about it. Then I kept discovering amazing things python
can do that php cant.
For instance, PHP can do this fine. Was there something in particular
you're thinking of that PHP can't do?
a set of
tools that go well beyond what I need from them.
The code is available for anyone:
I'll gladly explain/document more if anyone cares to hear
PS: I am now using a more clean email address. Previously I was using