240 likes | 255 Views
Collections Keeper blends the functionality of a collections management system with a database management system through a user-friendly web application interface. It provides a seamless solution for managing collections and data, with features like event-based design, foreign key support, image support, Excel file creation, referential integrity, SQL bookmarks, and batch entry processing.
E N D
The Collections KeeperA collections management system Brian J. Mullen
System Overview • Goal • Blend the functionality of a collections management system with a database management system • Do this through a web application interface • Why • Existing collections management systems provide poor support for web pages • Existing database management systems can be overly complex and intimidating
Design: Event based design lends naturally to a web interface Primary object, Table, inherent in a database Each script represents an action
Design: Event scripts: • View Data • Create Data • Modify/Delete Data • Create Table • Modify Table • Delete Table • User Management • Settings Management
Design: Script Execution: Header Start page layout Grab user privilege Grab user id Grab settings Scripted Page Verify permissions Perform action Footer Finish page layout
Foreign Key Support: Uses MySQL key naming feature:
Using Key Naming For Viewing Data: Recognizes a foreign key and creates a link to the entry
Using Key Naming For Entering Data: Recognizes a foreign key and creates a drop down box
Modifying Tables: Changing Foreign Keys
Modifying Tables: Changing Existing Columns
Modifying Tables: Adding Columns
Image Support: Generates Thumbnails And Links To Image
Excel File Creation: Create excel files from the tables in the database
Referential Integrity: When removing users can remove all of user’s entries
Referential Integrity: When changing table names can update name in all tables
Referential Integrity: When removing a table can automatically remove for any tables that contain as a foreign key
SQL Bookmarks: Given the broad scope of Collections Keeper it is inevitable that all cases will be covered. SQL Bookmarks are there when Collections Keeper can’t do what you want.
SQL Bookmarks: Create a bookmark from the “View Collection” page
SQL Bookmarks: Manage SQL Bookmarks
Batch Entry: Essential when adding a lot of entries at one time
Batch Entry: Fill in common data on first form and set all forms to that data
Conclusion • Merged the features of a collections management system with a database management system • I learned: • More about programming in PHP and MySQL • Better coding practices due to large breaks in the creation of Collections Keeper