On Thu, 13 Jan 2022 15:22:50 -0500, Dennis Lee Bieber
<wlfr...@ix.netcom.com> declaimed the following:
Talking to myself in public again... Bad habit...
> As you've described this system, the only thing your application will
>do is record "check-outs" by tracking available copies of books, and the
>name (and dates?) of the person doing the check-out. There is no reporting
>function -- not even a print-out for the user of which books they've just
>reserved, so how does anyone actually verify they are to receive a physical
>book after reserving it. Is there any logic to prevent someone from
>reserving multiple copies of a book... You'll also need logic to ensure
>that multiple borrowers connecting to the application at the same time
>can't both reserve the same copy of any book, or that one borrower doesn't
>block others from reserving other books at the same time. Spreadsheets are
>not "multiple user" files, and if each session (borrower connecting to the
>application) results in the application trying to open the spreadsheet
>you'll have conflicts.
>
Perhaps
https://data-flair.training/blogs/library-management-system-python-project/
can provide some clues -- though it is tkinter based, not a web
application... (Though they don't seem to be tracking issue/due dates <G>).
Or, for a web application (using Django, not Flask) see
https://techvidvan.com/tutorials/python-library-management-system/
If you need more examples to purloin, rather than developing your own
implementation, just hit Google...
https://www.google.com/search?q=python+library+reservation+system which is
how I found the above two examples.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfr...@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/
--
https://mail.python.org/mailman/listinfo/python-list
