(WIP) => { The Controversies of Science App. Currently includes controversy search and a swiping interface for structuring the crowdsourcing of information on controversies. }
The quote could be automatically mined from the quote's body by identifying the first non-stop-word label not already reserved as an id for that page. For instance, if the quote was ...
"'Space' was invented on Earth before we knew what was out there"
... the keyword would be space and the url would look like:
What would be ideal is even if the quote is broken up by paragraphs, there exists a span which can be used to identify the end of each quote, so that it can be selected, annotated and shared as a distinct unit.
And if there are other versions of the quote which might be better for sharing -- like with some words or content left out -- that they are also available:
What would be nice is to spawn a dynamic hash link handler in the event that a hash link is not found on the page.
User-Generated Zoom Hash Links
Another really nice feature would be to permit users to create their own zoom frame id's for a particular graphic which would not only take the site visitor to the controversy card image, but also zoom them into the frame that has been associated with that id. A user could create that frame and id by clicking a button while they are at some particular zoom level. If specified as "public", these frame snapshots could subsequently be invoked by other users because they would then list on the page under ...
The thing about this is that the page cannot possibly contain all of these images (or even thumbnails) from former shares, so the way to do this would be to store them in an S3 bucket when they are generated, and then if a person goes to them, only then fetch them from the bucket.
An interesting question is where #annotations takes a person, since they are distributed across the page. And should there be an option to turn the annotations off?
Ideally, this would scroll to that first of that particular user's comments, while graying out all others. And perhaps once it gets there, change the URL to ...
All of this could be tricky to do since the person can of course have more than one comment, and yet we should only assign one single id on a page. It might be better to implement the content tagging as classnames, and see if I can interpret the hash link using React Router.
worldviewer
commented
7 years ago
Some of the things that I'd really like to be able to do with these hash links are completely experimental ...
Hash Links
For going to specific parts of the page:
The quote could be automatically mined from the quote's body by identifying the first non-stop-word label not already reserved as an id for that page. For instance, if the quote was ...
... the keyword would be
spaceand the url would look like:What would be ideal is even if the quote is broken up by paragraphs, there exists a span which can be used to identify the end of each quote, so that it can be selected, annotated and shared as a distinct unit.
And if there are other versions of the quote which might be better for sharing -- like with some words or content left out -- that they are also available:
With relevant image:
Or adding in a reference too:
Or use to go straight to best comments:
One question is: On the
/cardroute, if this should aggregate from all feeds and cards (probably).Or best questions for a controversy card:
It might (?) make sense, in such cases, to redirect, so that content is not being duplicated across pages:
There is a discussion of how to handle hashes with React Router at:
What would be nice is to spawn a dynamic hash link handler in the event that a hash link is not found on the page.
User-Generated Zoom Hash Links
Another really nice feature would be to permit users to create their own zoom frame id's for a particular graphic which would not only take the site visitor to the controversy card image, but also zoom them into the frame that has been associated with that id. A user could create that frame and id by clicking a button while they are at some particular zoom level. If specified as "public", these frame snapshots could subsequently be invoked by other users because they would then list on the page under ...
I don't know how hard it would be to do that, but if it proves impossible, it is probably still an option to use a route:
The thing about this is that the page cannot possibly contain all of these images (or even thumbnails) from former shares, so the way to do this would be to store them in an S3 bucket when they are generated, and then if a person goes to them, only then fetch them from the bucket.
Content-Based Shares
Possible?
Annotation Hash Links
An interesting question is where
#annotationstakes a person, since they are distributed across the page. And should there be an option to turn the annotations off?That could be useful in some situations.
Username Hash Links
Ideally, this would scroll to that first of that particular user's comments, while graying out all others. And perhaps once it gets there, change the URL to ...
All of this could be tricky to do since the person can of course have more than one comment, and yet we should only assign one single id on a page. It might be better to implement the content tagging as classnames, and see if I can interpret the hash link using React Router.
Rebuttal Hash Links