1. The Collections Keeper A collections management system Brian J. Mullen

2. 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

3. Design: Event based design lends naturally to a web interface Primary object, Table, inherent in a database Each script represents an action

4. Design: View Data Create Data Modify/Delete Data Create Table Modify Table Delete Table User Management Settings Management Event scripts:

5. Design: Script Execution: Grab user privilege Grab user id Grab settings Verify permissions Perform action Header Scripted Page Start page layout Footer Finish page layout

6. Final Product

7. Foreign Key Support: Uses MySQL key naming feature:

8. Using Key Naming For Viewing Data: Recognizes a foreign key and creates a link to the entry

9. Using Key Naming For Entering Data: Recognizes a foreign key and creates a drop down box

10. Creating Tables:

11. Modifying Tables: Changing Foreign Keys

12. Modifying Tables: Changing Existing Columns

13. Modifying Tables: Adding Columns

14. Image Support: Generates Thumbnails And Links To Image

15. Excel File Creation: Create excel files from the tables in the database

16. Referential Integrity: When removing users can remove all of user’s entries

17. Referential Integrity: When changing table names can update name in all tables

18. Referential Integrity: When removing a table can automatically remove for any tables that contain as a foreign key

19. 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.

20. SQL Bookmarks: Create a bookmark from the “View Collection” page

21. SQL Bookmarks: Manage SQL Bookmarks

22. Batch Entry: Essential when adding a lot of entries at one time

23. Batch Entry: Fill in common data on first form and set all forms to that data

24. 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