Cs373 Project

project

Transcript

1. DCDATABASE Darya Mylius, Andrew Turner, Kevin Du, Brendon Rhodes, Shuoyi Yang, Kiankris Villagonzalo, Jonathan Puentes
3. What we should have done • The security of server needed improvement, in need of ssh keys • Start earlier to prevent the inevitable “this is due in the next 2 hours and literally nothing works” • Spent more time learning about the tools that we used to work more efficiently and be more well rounded • Make a (working) backup server • We should have relied less on the amateur DCwiki site • Locked our phones away Self critiques:
4. What we learned • A greater appreciation for web development • The importance of communication and expanding character roles so that one person isn’t the only authority on a particular aspect • How to work with a database, APIs, postGres, SQLalchemy, Flask, and many more Self critiques:
5. What we did well And what puzzled us • The database is very expansive • Scheduled well • Implementing search • Sometimes our code broke the website • Sometimes the server just failed Self critiques:
6. What they should have done • Their color scheme could have been brighter and more friendly ◦ black , red, and dark red poor combo • Fixed the tables, number of issue • Made the visualization easier to use Komixx Critiques
7. What we learned • The importance of graphic design • A small amount of publishers control a large amount of characters and comic issues Komixx Critiques
8. What they did well • The have an internal search for tables and a global search • You can interactively sort their search results? • Wonderful API (except for real_name) • Images are clickable Komixx Critiques
9. What puzzles us 1. Your carousel 2. The UI 3. Is the website called downing.rocks or Komixx 4. The data seems to be inconsistent’ 5. How do we use your website? Komixx Critiques