Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Artology (Group 13) Presentation

Avatar for Dao Ton Dao Ton
April 15, 2024
110

Artology (Group 13) Presentation

Avatar for Dao Ton

Dao Ton

April 15, 2024
Tweet

Transcript

  1. Table of contents Navigation, search, and show visualization What did

    they do well? What did we learn from their website? What can they do beer? What puzzles us about their website? 03 Other Critique (Group 1) What did we do well? What did we learn? What can we do beer? What puzzles us? 01 02 Demonstration Self Critique
  2. Search • Global Search Results • Artwork Search • Artist

    Search • Exhibition Search (backup slides)
  3. What did we do well? Model linking ➢ Clear connections

    between dierent entities Intuitive and Responsive Interface ➢ Clear visual hierarchies; well-organized content ➢ Balanced aesthetics with performance
  4. What did we learn? ➢ Creating DB schemas and queries

    ➢ Combining it w/Flask and Python ➢ Interacting with external data sources ➢ Documenting our own API with Postman ➢ Using Flask on the backend and HTML href links for the frontend ➢ Filter/ordering data without reloading the page ➢ UI/UX ➢ Bootstrap framework ➢ Visual debugging with many data instances SQLAlchemy Searching & Sorting Implementing APIs HTML & CSS
  5. What can we do better? More improvements can be made

    to UI/UX Would help in organization of scripts/components Refining front-end React More Searchability Making arrays of alternative aributes searchable alongside main aributes
  6. What puzzled us? Challenges w/ GCP Deployment ➢ Adjusting seings

    to suit the deployment environment while ensuring compatibility between module versions Implementing Searching ➢ Initially confused about searching functionalities that handled multiple parameters Searching Array Aributes and other Aributes Simultaneously ➢ Could only do one or the other; trying to implement both at the same time failed
  7. What did they do well? ➢ Easy traveling back and

    forth between related models ➢ Artists could be discovered based on collaborations or similar genres Pagination Related Artists Inter-model Navigation ➢ Fast rendering of model instances
  8. What did we learn from their website? React can improve

    the performance of a website ➢ This was seen with the pagination, the model instances were loaded in immediately as you moved between the pages. Challenges w/ React ➢ React can be diicult to work with at first and the group faced challenges trying to deploy the website through GCP.
  9. ➢ Get the genre instance pages to render properly -

    resolve API issues ➢ Refining the design of the website by incorporating more color or animations ➢ Add in a global search option that can search a keyword from all models simultaneously ➢ Provide more sorting options / sortable variables What can they do better?
  10. What puzzles us about their website? Genres for an instance

    are found at the boom but would be beer placed near the top. Genre Placement Each page for the models only showed 4 instances at most. Having more instances shown would be beer from a UI/UX perspective Model Pages
  11. CREDITS: This presentation template was created by Slidesgo, and includes

    icons by Flaticon, and infographics & images by Freepik Please keep this slide for aribution