Please enable JavaScript.
Coggle requires JavaScript to display documents.
Books Project - Coggle Diagram
Books Project
Research Investigation
API
Google Books
Search & browse list of books with a query
View metadata, availability, price and links to the preview page
Manage personal bookshelves
Uses OAuth 2.0 requests (Google Sign-On)
API Key required to access licenced data
Google Maps API
API Key (Access Map Data)
Map Type = Place
Puts a pin on the designated place
Uses both names/query or coordinates
Data Format
JSON (JavaScript Object Notation) lightweight data interchange language
Datasets
Google Books Dataset
Volume, Bookshelf and User ID's
Not intended as a replacement for commercial services
Title, Author, Image, Description and Publisher
Library Locations Dataset
CSV
Venue, Coordinates, Website, Address, Opening Hours/Days, Phone, Summary, Facilities, Meeting Rooms
Existing Solutions
Hathi Trust Digital Library
Development
Languages
CSS
User Interface
PHP
Displaying Data
JavaScript
HTML 5
Bootstrap/Format
Google Maps
MySQL
Data Exchange
User Interface
Bootstrap 5
Transforms Webpage for multiple devices and Aspect Ratios
Simple Navigation Header & Footer
Data
Accessing Object Values
e.g totalBooks->[bookTitle]
MySQL Queries
e.g. GET * FROM PublicLibraryDirectory WHERE Suburb = Greenslopes
Client (Brisbane City Council)
Requirements
Blue, White, Yellow, Grey Colour Scheme Palette
Brisbane City Council Logo
Dedicated to Brisbane
Follows Brisbane City Council Website Standards
Copyright Reference
Two Systems, Application and Data Store
User
Potential Users
Mary
Age: 62
Device: Mobile & Laptop
Retired
Impaired Hearing
Requirements: Find Local Library, Know Parking and Access limitations
Leader of a reading club
Pater
Age: 75
Device: Laptop
Retiree living at retirement village
Impaired vision
Requirements: Review Books, Local Library Location
Alan
Age 70
Device: Mobile
Retired
Requirements: Review Books, Search books by author or title
Part of a reading club
Elderly Target Userbase
Limited Symbol Use
Older users aren't familiar with recent common symbols. Home, Question Mark, Profile etc. Therefore A simple title for each button will suffice for this application
Informative via text
Interactive features can be confusing for older users. Therefore informative text segments should be used rather than videos, audio or animations.
Simple Navigation
Common navigation features aren't familiar for older users, therefore implementing a simple header and footer navigation system will prevent confusion.