WriterBlocks

Transcript

1. EXCLUSIVE PREVIEW OF AN WriterBlocks writerblocks.me So many books, so little time.
2. Allow the user to easily find books and related information. About Writer Blocks The database is simple to use and will leave many users saying "Oh wow I did not know this author also wrote this book" Stats Commits: Issues: 53 Unit Tests: 17
3. Writers Julio Mendez Justin Smith Yipu Wang Billy Do Jake Miller Kevin Hwang Commits: 10 Issues: 14 Commits: 26 Issues: 9 Commits: 40 Issues: 4 Commits: 26 Issues: 1 Commits: 4 Issues: 2 Commits: 55 Issues: 6
4. Scraping Data "All right, I've been thinking. When life gives you lemons? Don't make lemonade. Make life take the lemons back! Get mad! 'I don't want your damn lemons! What am I supposed to do with these?'" ­Cave Johnson
5. Data models Book ID Title ISBN Image URL Description Amazon URL Author ID Publisher ID Series ID Author ID Name Date of Birth Occupation Nationality Homepage URL Image URL Publisher ID Name Founder Year Founded Country Status Image Association Table Book IDs Author IDs Many to many One to Many One to Many "All animals are equal, but some animals are more equal than others." — George Orwell (Animal Farm) Series ID Title Genre num_books status description notes Author ID Many to Many
6. Book
7. Publisher
8. Author
9. A P I /api/books{?id}{?title}{?isbn} Get a single book based on ID, Title or ISBN-13 /api/authors{?id}{?name} Get a single Author based on ID or Name /api/publishers{?id}{?name} Get a Single Publisher based on ID or Name
10. WriterBlocks Critique What did we do well? ­ Solid data model: our data model designed from first stage is consistent throughout the whole projects with only adding attributes for detailed information of each types. ­ Scraping data from NY Times: NY Times best seller list provided a finite number of books for our database. What did we learn? ­ A set of tools for building website. ­ Collaborating between frontend and backend design ­ Using other sites APIs and tools to get data (and the value of good documentation) ­ The fragility of infrastructure ­ Search bar for individual table: the search bar is capable of searching based on every attributes like ISBN, nationality or founder.
11. WriterBlocks Critique What can we do better? ­ Many entries have more than one attributes missing, due to the fact that there's not a single API that is capable of collecting all information needed. ­ Communicating between group members. ­ Researching the data model before loading data. ­Clearer delineation of responsibilities and methods for accountability What puzzles us? ­ Methodologies for tool selection and benchmarking (e.g. Why use Angular over Jinja?)
12. CuiBono Critique What did they do well? What did we learn from their website? ­ Data models are cohesive and provide intuitive understanding for the sites purpose ­ Consistent site design ­ Used other APIs well to gather data
13. CuiBono Critique What can they do better? What puzzles us about their website? ­ Display some data better (addresses and websites) ­ Reduce redundancy on individual pages ­ Pagination button is difficult to find
14. Thanks!