User stories
From ActiveArchives
User Stories are written by the (future) editors as things that the system needs to do for them. They are similar to usage scenarios, except that they are not limited to describing a user interface. They are in the format of about three sentences of text written by the editor in the editors terminology without techno-syntax.[1]
Contents |
Personal Wayback Machine
I need a simple tool to take a snapshot of webpages I'm interested in archiving/quoting/reusing, like a personal version of the wayback machine on archive.org. Ideally the snapshots would just be a folder (like a save as... web archive in Firefox), but could be bigger than just a single page (ie that links could work).
Smart(er) Playlists
I would like the ability to play media (sounds, images, videos) like from an iTunes/Rhythmbox type media player. For instance to say: Play music from archive.org while showing a slideshow of images from tapies.
AA Media Gallery
We want to provide a more media-savvy (saavy;) "gallery" view of the contents of the constant media lockers, namely:
http://video.constantvzw.org http://gallery.constantvzw.org
An AA Gallery would allow for tagging/annotation, provide faceted browsing of the media, allow for "qna" like tagged playback, flexible export options (like saving a BASH script to download selected materials). Ability to watch all media in "shuffle play" / random combination of vid + image + sound.
Containing pages / Back links
Often I want to include an image or video from a web page. The conventional approach to uncover and use the media URL has two problems:
- It takes some digging to get the underlying URL (particularly for embedded videos that sometimes obscure this).
- Having a link to the containing page is often more interesting than just the media itself if offering a link back to the original context of the media.
So, in adding a page - the archive would (automatically) add contained media allowing use of the this contained media, while still providing a "link back" to the original page using this media.
Are normal links stored in the triple store as well ?
Beyond just explicit RDF, Storing HTML structure in an RDF store
- Regular links
- Embedded media, ie img, embed (thus refs in Javascript)
- Headers (as values)
JQuery for the web
JQuery allows powerful means for selecting portions of pages and performing manipulation commands on them. How might AA be a kind of jquery across the multiple resources of an archive. Another way of saying this is providing:
Efficiently across an archive.
SPARQL results in either:
- RDF Graph structure (RDF nodes)
- Table structure (RDF nodes)
CSS & XPATH Selectors:
- Lists of HTML elements (DOM nodes)
Can imagine using: SPARQL | CSS
Where the SPARQL query would need to be reduced to a set of URLs, then for each URL, the CSS query would run.
PREFIX foaf: <http://xmlns.com/foaf/0.1/>
SELECT ?url
FROM <bloggers.rdf>
WHERE {
?contributor foaf:name "Jon Foobar" .
?contributor foaf:weblog ?url .
}
xpath://h1.text()
Internet quoting done right
Currently to paste a quotation from a website requires a double cut and paste, first for the text, second for the URL plus all the accompanying wiki markup to format the result + add a link back to the source. Semantically the source / position in page is all lost.
Clean writing space
The Current AA is very useful in allowing videos to be watched from various contexts (Vimeo for instance), in a sort of "clean room" where one can focus on taking notes while watching with little distraction. It would however be useful to have suggestions for links or the ability to temporarily watch (tag) linked videos to compare.
