Information Architecture

Information architecture for our project (schema and site navigation).

Schema

Project data model outline. All models have created and modified properties as well as an AppEngine created id (primary key). Standard REST-ful data access

applies:

http://streetcode-sw.appspot.com/data/<model> - collection (GET, POST)
http://streetcode-sw.appspot.com/data/<model>?prop=value - filtered collection (GET)
http://streetcode-sw.appspot.com/data/<model>?prop=value* - filtered prefix (GET)
http://streetcode-sw.appspot.com/data/<model>/id - item (GET, PUT, DELETE)

Clients

• displayName
• fullName
• story (long text)
• sponsor
• imageURL
• shortCode

Sponsors

• name
• url
• address
• phone

Donors

• name
• email
• phone

Users (user accounts)

• isAdmin
• sponsor
• user (app engine credentials)

Scans

• client
• donor
• ledger
• transaction

Transactions (ledger)

• fromAccount (e.g., 'stripe')
• toAccount (e.g. 'sponsor_id/client_id' like 'sponsor_64/client_12')
• amount
• type
• note
• confirm

SKUs

• name
• price
• description

Site Navigation

This web application serves several different constituents, with access to different functions:

• Donors: Mobile web interface displayed after scanning a Clients's QR-Code. The site home page is also primarily targeted at Donors.
• Sponsors: Partner organizations access to client administration pages.
• Administrators: Site administration, setting up Sponsors and User accounts.

URL

• /: Home pages, marketing, positioning
• /client/id: QR-Code landing page for a Client