Purojekuto!!!
Group Proposal:
We are developing a system for quick, short-term storage of web elements. The velocity of modern living often precludes extended sessions online, and necessitates efficient, ad-hoc systems for storing and sharing simple data, e.g. websites to be read; links/images/notes for short-term projects; quotes or links to share with unavailable friends. Some systems exist that accommodate these goals, but only incidentally to their intended tasks: del.icio.us is intended for longer-term recording of links, and uses folksonomic organization to find related and popular sites; Backpack is a multi-modal system for recording data elements, with an emphasis towards time management and collaborative organization. Our system will use Javascript bookmarklets to trivialize recording in situ, and define records as draggable AJAX elements to make loose, hiearchical (or associative), on-site organization natural and adaptable.
This project can be divided into three relatively parallel tasks:
1) Contextual bookmarklets to parse plain text, hyperlinks, and/or image links from the wild to our system.
2) AJAX-driven interface for presentation of user-stored data. Simple, high-level model-world systems for sorting and modification of data elements.
3) Database for userdata storage.
And meta-bullets:
1) Defining public/private, individual/collaborative spaces user spaces, and systems for transitioning resources between spaces.
2) A strong, cohesive visual and philosophical identity.
3) Uniformity and generalizability of backend coding; development of a public API and simple extensions for outward presentation models (badges, RSS feed).
4) Metadata synthesis.
My Take:
One issue we have to deal with is how to make this system manageable, such that one can find a specific item in a field of other links. This is why I argue against a hierarchical organization; it would be cumbersome to go through multiple 'levels' just to find or classify a bookmarklet. An associative approach is much more suited to our project's goal, although it is harder to visualize this information.
I'm excited to work on this project. I've always felt insecure because I don't have any back-end web experience, and I'm reluctant to learn it because I don't know where to start. Since Pam, my wonderful group-mate, has the know-how to get this project off the ground, I'm hoping to learn from her. My other group-mate, Brian, is a design-y person like myself, but he's more of a nerd than I am so he's played around with many many web apps and such, so he has a lot of practical experience with the kinds of things we're building our project upon, and he doesn't use run-on sentences like this one. I suppose my main part will be in designing the user interface. Fun!
We are developing a system for quick, short-term storage of web elements. The velocity of modern living often precludes extended sessions online, and necessitates efficient, ad-hoc systems for storing and sharing simple data, e.g. websites to be read; links/images/notes for short-term projects; quotes or links to share with unavailable friends. Some systems exist that accommodate these goals, but only incidentally to their intended tasks: del.icio.us is intended for longer-term recording of links, and uses folksonomic organization to find related and popular sites; Backpack is a multi-modal system for recording data elements, with an emphasis towards time management and collaborative organization. Our system will use Javascript bookmarklets to trivialize recording in situ, and define records as draggable AJAX elements to make loose, hiearchical (or associative), on-site organization natural and adaptable.
This project can be divided into three relatively parallel tasks:
1) Contextual bookmarklets to parse plain text, hyperlinks, and/or image links from the wild to our system.
2) AJAX-driven interface for presentation of user-stored data. Simple, high-level model-world systems for sorting and modification of data elements.
3) Database for userdata storage.
And meta-bullets:
1) Defining public/private, individual/collaborative spaces user spaces, and systems for transitioning resources between spaces.
2) A strong, cohesive visual and philosophical identity.
3) Uniformity and generalizability of backend coding; development of a public API and simple extensions for outward presentation models (badges, RSS feed).
4) Metadata synthesis.
My Take:
One issue we have to deal with is how to make this system manageable, such that one can find a specific item in a field of other links. This is why I argue against a hierarchical organization; it would be cumbersome to go through multiple 'levels' just to find or classify a bookmarklet. An associative approach is much more suited to our project's goal, although it is harder to visualize this information.
I'm excited to work on this project. I've always felt insecure because I don't have any back-end web experience, and I'm reluctant to learn it because I don't know where to start. Since Pam, my wonderful group-mate, has the know-how to get this project off the ground, I'm hoping to learn from her. My other group-mate, Brian, is a design-y person like myself, but he's more of a nerd than I am so he's played around with many many web apps and such, so he has a lot of practical experience with the kinds of things we're building our project upon, and he doesn't use run-on sentences like this one. I suppose my main part will be in designing the user interface. Fun!
posted by Moni at 12:48 AM
0 Comments:
Post a Comment
<< Home