skytreader / librarian Goto Github PK

Query functions must succeed regardless of the casing of the arguments passed. Right now, being that we assume them to be of the same case, using a different case makes the fields array crash (since we use them as indices).

Refreshing on the dashboard (at least at initial log-in) results to user going to "login/fail" page. This shouldn't be.

Add a translator field for adding books.

Check if the ISBN entered is, indeed, a valid ISBN number. Use checksums as discussed in http://en.wikipedia.org/wiki/International_Standard_Book_Number#Check_digits

The perennial issue.

Check JavaScript and CSS/layout.

This is of low-priority though, being that I will not be using this with IE.

Pressing the enter key while at the log-in form must submit the form for verification.

This provides for a UI enhancement but also because not doing so causes problems with how CodeIgniter creates links. Simply put, this seems to be the cheapest alternative.

Better formatting for form messages. Better error messages for saving app settings.

The error messages generated for app settings may come from the exceptions thrown by DAOModel update. It may be better if this exception message is more personalized for the specific record represented.

See: http://en.wikipedia.org/wiki/MARC_standards

(Check other resources too.)

Right now, we're only checking if all PK attributes of the DAO are set.

(Or, is this relevant given that the DB itself will complain if a PK attribute is missing in the DAO?)

When a user is not logged in and accesses dashboard.php, Librarian should automatically redirect to the log-in page, without any messages. However, when, in the log-in page, a user enters an invalid username-password combination, he should be redirected to the log-in page with a message informing about the invalid username-password combination.

Currently, when an invalid username-password combination is entered in the log-in page, there is no message.

(Recall that dashboard.php is the one that processes log-in verification.)

Add functionality to:

• Check if user is logged in or not, and then do the appropriate action afterwards.
• Read default scripts and stylesheets from a config file.

And, ideally:

• Make it so that it looks "native" to CodeIgniter.

The database already has a dedicated table for application-wide settings. Do we represent user settings in the same (possibly meta) manner?

But that will cut out a lot of functionality. See the most basic example, password changing. How will password changing (standard: ask for old password, ask for new password, enter again to confirm) work with that?

Also, given the DAOModel (cf. Active Record Pattern), it seems easy to accidentally issue an UPDATE and change a user's password. Should we do this using stored procedures?

A PHP Error was encountered

Severity: Notice

Message: Undefined index: username

Filename: controllers/dashboard.php

Line Number: 23

And also,

A PHP Error was encountered

Severity: Notice

Message: Undefined index: username

Filename: controllers/dashboard.php

Line Number: 23

Dashboard should have the following:

• Library statistics - For each criteria (Genre, Author, Illustrator, Editor, Translator, Publisher Printer, Year), display the entry with the most number of books. Then, beside this entry, display a link that will allow the user to view full statistics for that criteria (i.e., book breakdown by criteria).
• Newest book added. This entails a change in the database.