1. Rapid Prototyping of Single-Page Applications (SPAs)

2. Keeping Found Things FoundWilliam Jones2 Using… itemMirror* * http://keepingfoundthingsfound.github.io/itemMirror/classes/ItemMirror.html

3. Keeping Found Things FoundWilliam Jones3 itemMirror is… a JavaScript framework using XML in order to associate metadata with ordinary file folders in a way that is customizable, shareable among applications, and that works across OS-platforms via cloud storage services such as Dropbox.

4. Keeping Found Things Found The value for users 4 Use the familiar folder model for structuring information Take advantage of features for sharing and syncing as provided by any # of storing applications ( Dropbox, OneDrive, Google Drive, Box, REST…) Move between or mix & match among these storing applications. Mix & match among a growing # of applications for working with your information in new ways.

5. Keeping Found Things Found The value for developers 5 No need to work directly with APIs for storing applications ( Dropbox, OneDrive, Google Drive, Box, REST…) Work instead via drivers that support the itemMirror object model. Write your application once – have it work across storing applications ( Dropbox, OneDrive, Google Drive, Box, REST…) via drivers* *Drivers exist now for Dropbox. Drivers for Google Drive soon...

6. Keeping Found Things Found To illustrate: Spring quarter student projects (2013 & 2014)

7. Keeping Found Things Found Start with a folder structure in Dropbox

8. Keeping Found Things Found Model structure in itemMirror objects of JavaScript

9. Keeping Found Things Found Teams of MSIM students build SPAs (HTML5 apps) working exclusively with itemMirror objects

10. Keeping Found Things Found Objects persist their “mirrors” in synchronized XML fragments according to a “XooML” schema

11. Keeping Found Things Found SPAs by students have presented folders as... 11 an outline a mind map task/to-do lists an affinity diagram a tagging hierarchy for use in organizing Web information  see “Knitter” video (https://www.youtube.com/watch?v=0H9y5sjW8 zc&feature=youtu.be)https://www.youtube.com/watch?v=0H9y5sjW8 zc&feature=youtu.be

12. Keeping Found Things Found But there are many more possibilities… 12

13. Keeping Found Things FoundWilliam Jones13 Let the contents of a folder tell a story…

14. Keeping Found Things FoundWilliam Jones14 You can still see your folders in conventional views such as…

15. Keeping Found Things FoundWilliam Jones15 Or…

16. Keeping Found Things FoundWilliam Jones16 But also as a “my projects” collage…

17. Keeping Found Things FoundWilliam Jones17 Or a mind map…

18. Keeping Found Things FoundWilliam Jones18 Or a fantasy map…

19. Keeping Found Things FoundWilliam Jones19 The Sponsor: William Jones, williamj@uw.edu Research Associate Professor at the University of Washington Manages the Keeping Found Things Found project Wrote “Keeping Found Things Found: The Study and Practice of Personal Information Management” (2007). Edited (with Jaime Teevan) the book “Personal Information Management” and a special issue on PIM for the Communications of the ACM (2006). Wrote invited chapters on PIM for ARIST and for the Handbook of Applied Cognition. Has organized or co-organized numerous workshops, tutorials and courses on PIM including an invitational workshop sponsored by the National Science Foundation. Have 5 patents relating to search and PIM. Dr. Jones received a doctorate in Cognitive Psychology a long time ago from Carnegie-Mellon University for research in human memory

20. Keeping Found Things Found Thank you 20 (but read below for background)

21. Keeping Found Things Found The _real_ reason to use itemMirror?: So we can take back our information In better world, our information – content and structure – has an integrated, unified existence independent of any particular device or application. Just as we use a diversity of tools in the construction & maintenance of our houses, we need to apply a diversity of tools (“the right tool for the right job”) as we build our houses of digital information.

22. Keeping Found Things Found Export/import is “lossy” Image from http://chinesewhispersgame.blogspot.com/2010/06/so-whats- chinese-whisper.html

23. Keeping Found Things Found And we’re left to wonder: Why must I choose? “”I prefer zotero when I'm browsing the net and searching for papers, but I prefer a fully dedicated program like mendeley for later editing and browsing my own collection”. And, from another user on the same discussion board: “I don't want to be locked into using just Mendeley or Zotero” “The only reason I really use Evernote is for the OCR…”

24. Keeping Found Things Found And what does export/import mean now when our information is everywhere on the Web?

25. Keeping Found Things Found Take back our information! Our information can be ours again – with integrated, unified existence independent of any particular device or application.

26. Keeping Found Things Found Taking back our information in 4 steps. Step 1. Leave the information where it is (for now):

27. Keeping Found Things Found Taking back our information in 4 steps. Step 1. Leave the information where it is (for now): Step 2. Model the structure of this information using itemMirror objects.

28. Keeping Found Things Found Taking back our information in 4 steps. Step 1. Leave the information where it is (for now): Step 2. Model the structure of this information using itemMirror objects. a. itemMIrror objects all support the same methods on the front-end but, on the back-end, these methods work with drivers specific to a given “storing” application and its API. b. These drivers provide read/write access to information structures that are otherwise “siloed” in the application

29. Keeping Found Things Found Taking back our information in 4 steps. Step 1. Leave the information where it is (for now): Step 2. Model the structure of this information using itemMirror objects. Step 3. Now other applications working exclusively through these itemMirror objects might provide complementary ways of working with the information structures:

30. Keeping Found Things Found Taking back our information in 4 steps. Step 1. Leave the information where it is (for now): Step 2. Model the structure of this information using itemMirror objects. Step 3. Now other applications working exclusively through these itemMirror objects might provide complementary ways of working with the information structures. Step 4. itemMirror objects persist their “mirrors” of structure in synchronized XML fragments according to a “XooML” schema.

31. Keeping Found Things Found This means (in plain English ) that 31 Folders (and other “grouping items” such as Facebook “albums”)  Can now behave in many new, useful and fun ways As whiteboards with notes… to-do lists… ideas in a mind map… to represent people we care about or places we want to go… At another level, these folders are still folders  Behaving as we would expect them to.

32. Keeping Found Things Found itemMirror is…. 32 A simple way to associate metadata with folders  Customizable, extensible, shareable.

33. Keeping Found Things Found itemMirror is…. 33 A simple way to associate metadata with folders  Customizable, extensible, shareable. “Application neutral”  Many apps… One Information, i.e. our information is cohesively linked and integrated into a coherent whole. No more fragmentation!

34. Keeping Found Things Found itemMirror is…. 34 A simple way to associate metadata with folders  Customizable, extensible, shareable. “Application neutral”  Many apps… “One Information” A way to knit together all our information, no matter “where” (no matter which service, device, OS or storing application)

35. Keeping Found Things Found 1 2 3 4 Information “take back” in 4 steps!