1. information architecture (basics for app building)

2. what we’re after: articulate the impact that information architecture can have on knowledge Awareness of media imposed constraints on information architecture select an appropriate architecture for your project articulate the impact that information architecture can have on knowledge Awareness of media imposed constraints on information architecture select an appropriate architecture for your project

3. Physical Organization

5. What happens when we get too much stuff for piles? paper lists & catalogs digital databases

7. ontology & hierarchy hierarchy + links web-scale organization only links, no authority

9. IT DOES SOMETHING FOR SOMEONE. IT'S PURPOSE BUILT. IT'S NOT USEFUL BEYOND THIS PURPOSE. an app = small program or utility running on a mobile device.

11. Ontology Works When: Domain to be Organized Small corpus Formal categories Stable entities Restricted entities Clear edges Domain to be Organized Small corpus Formal categories Stable entities Restricted entities Clear edges

12. Ontology Works When: Participants Expert Catalogers Authoritative Source of Judgement Coordinated Users Expert Users Participants Expert Catalogers Authoritative Source of Judgement Coordinated Users Expert Users

13. Practically Speaking, what does all this mean? We are not constrained by our media to use an ontological organization. A. However, it is one reasonable choice, among many B. It is a damn good fit for early projects. We are not constrained by our media to use an ontological organization. A. However, it is one reasonable choice, among many B. It is a damn good fit for early projects.

15. Next: usability & wireframe