19
edits
Synthesizing Social Media/First Breakout Session: Difference between revisions
Synthesizing Social Media/First Breakout Session (view source)
Revision as of 17:35, 12 November 2022
, 17:35, 12 November 2022→Sharing attention data on ActivityPub through Zotero (?) extension
| (6 intermediate revisions by 2 users not shown) | |||
| Line 45: | Line 45: | ||
=== Mastodon/Twitter Paper announcement use case === | === Mastodon/Twitter Paper announcement use case === | ||
* One of the common norms that have developed on academic social media (Twitter/Mastodon) is announcement/summary threads of one’s paper. e.g.: | * One of the common norms that have developed on academic social media (Twitter/Mastodon) is announcement/summary threads of one’s paper. e.g.: https://hci.social/web/@Mor/109309396530932422 (others of interest: job market announcements, taking PhD announcements) | ||
* Imagine if you could create for yourself a unique, short, readable identifier for a paper, and add that in your post thread about your paper announcement. | * Imagine if you could create for yourself a unique, short, readable identifier for a paper, and add that in your post thread about your paper announcement. | ||
** Possible syntax: | ** Possible syntax: | ||
*** @mor:crisis-informatics / | *** <code>@mor:crisis-informatics</code> user namespace | ||
**** downsides: there are multiple authors, so an author may feel left out if another author's id gets used more often | **** downsides: there are multiple authors, so an author may feel left out if another author's id gets used more often or authors could coalesce around one author (ie, 1st author) | ||
*** <nowiki>#</nowiki>cscw22:crisis-informatics / | *** <code><nowiki>#</nowiki>cscw22:crisis-informatics</code> conference namespace | ||
**** downsides: possibility for name conflicts, you could use the conference ID but it's not very readable | **** downsides: possibility for name conflicts, you could use the conference ID but it's not very readable | ||
* Things you could do as a result: | * Things you could do as a result: | ||
** Presentation: put all your different paper threads on your academic webpage and associated with each paper | ** Presentation: put all your different paper threads on your academic webpage and associated with each paper, for example | ||
** Synthesis: collect all the paper announcements for a conference and organize/synthesize it using other tools | ** Synthesis: collect all the paper announcements for a conference/topic and organize/synthesize it using other tools | ||
** Discussion: people could reference your identifier in their conversations, and a bot could post the paper announcement thread as a reply ( | ** Discussion: people could reference your identifier in their conversations, and a bot could post the paper announcement thread as a reply (https://hci.social/web/@lewischuang/109331737391363720) | ||
** Discussion: you could collect all discussion around your paper in a separate place, or a bot could post pingbacks on the original paper announcement thread | ** Discussion: you could collect all discussion around your paper in a separate place, or a bot could post pingbacks on the original paper announcement thread | ||
=== Sharing attention data on ActivityPub through Zotero (?) extension === | |||
* Attention data (~digital pheromone trails) is an important step in the knowledge synthesis pipeline- what am I looking at and my assessment of it | * Attention data (~digital pheromone trails) is an important step in the knowledge synthesis pipeline- what am I looking at and my assessment of it | ||
* | * Sharing attention data using linked data over ActivityPub- | ||
** Pros- catching Mastodon wave, good expressivity but | |||
** Cons- writing it manually creates friction and so reduces usage by researchers | |||
* An extension can create automatic linked data posts based on existing user activity in Zotero | * An extension can create automatic linked data posts based on existing user activity in Zotero | ||
** Adding a paper to a reading list | ** Adding a paper to a reading list | ||
| Line 67: | Line 68: | ||
** Annotating inline, connecting pieces to other papers | ** Annotating inline, connecting pieces to other papers | ||
** Reviewing/assessing/endorsing content | ** Reviewing/assessing/endorsing content | ||
* Question - what are interesting downstream applications for attention data? | |||
** Content recommendation | |||
** Layering paper viewers with endorsements/reviews, popular tags & annotations | |||
*References | |||
**[https://dl.acm.org/doi/10.1145/2818048.2819949 Opportunities and Challenges Around a Tool for Social and Public Web Activity Tracking] | |||
**[https://dl.acm.org/doi/abs/10.1145/3511095.3536361 From Users to (Sense)Makers: On the Pivotal Role of Stigmergic Social Annotation in the Quest for Collective Sensemaking] | |||
[[Category:Conversation]] | [[Category:Conversation]] | ||