Property:Contains text
- Text
- schema:text (schema | Schema.org, V 14.0)
D
super glad to hear that the endpoint worked btw, i've never used SPARQL and am more used to just making my own data models that generate API queries & parse etc. so I would love to see what you've been doing and how you've been using it - I'll make a [[SPARQL]] page linked off the wiki page that gives the URL and maybe we can embed sample queries and etc. there +
I am definitely on team "scruffy" per Lindsay Poirier's typology (BTW "[[A Turn for the Scruffy]]" should be on the collective [[Reading List]] for anyone who hasn't come across it) and so yes definitely "Own-terminology" iterating into something shared, part of why i love the semwiki model of building them. On the other end of things for tomorrow - Is there any particular existing ontology/schema/etc. anyone in this group would like to have imported into the wiki for discourse modeling? +
[[A System for Interleaving Discussion and Summarization in Online Collaboration#Evidence]] This section of the document references some [[Other Work]] +
Info on using [[Page Schemas]]:
So you could only need to make schemas for the different types of nodes that you'd want, so if i'm reading right then yes you would have several hundred pages but only 4-5 schemas.
A schema is defined (using page schemas) from a Category Page
A page is only ever loosely connected to a schema (rather than strictly, ie. can only have/requires the schema's fields) through its categ +
Info on using [[Page Schemas]]:
So you could only need to make schemas for the different types of nodes that you'd want, so if i'm reading right then yes you would have several hundred pages but only 4-5 schemas.
A schema is defined (using page schemas) from a Category Page
A page is only ever loosely connected to a schema (rather than strictly, ie. can only have/requires the schema's fields) through its category. Page schemas then generates a template for the category. Typically templates will add a page to a category anyway ([ [Category:CategoryName] ]). So a page can have multiple schemas - that would just look like using multiple templates on the same page. +
[[Semantic MediaWiki]] vs [[WikiBase]]: you're right! Semantic mediawiki is more for being an interface that can support unstructured and structured information in the same place, it's a lot more freeform and gestural, but at the cost of predictability/strictness/performance as a database. Definitely different tools with different applications, albeit with a decent amount of overlap in philosophy and etc. +
[[Page Schemas#Creating a new Schema]]
Page schemas is mostly a handy way to generate boilerplate templates and link them to semantic properties. A Form (using [[Page Forms]] is something that is an interface for filling in values for a template.
For an example of how this shakes out, see
[[:Category:Participant]]
[[Template:Participant]]
[[Form:Participant]]
* go to a `Category:CategoryName` page, creating it if it doesn't already exist.
* Click "Create schema" in top right
* If you want a form, check the "Form" box. it is possible to make a schema without a form. The schema just defines what pages will be generated, and the generated pages can be further edited afterwards (note that this might make them inconsistent with the schema)
* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.
* Add fields! Each field can have a corresponding form input (with a type, eg. a textbox, token input, date selector, etc.) and a semantic property.
* Once you're finished, save the schema
* Click "Generate pages" on the category page. Typically you want to uncheck any pages that are already bluelinks so you don't overwrite them. You might have to do the 'generate pages' step a few times, and it can take a few minutes, bc it's pretty buggy. +
OK we have a testing [[Mastodon#Test Instance]] server up and running at https://masto.synthesis-infrastructures.wiki
- since I am not going to bother setting up sending emails from the test instance, I need to manually bypass the email verification step for any accounts that are registered. If you want to make an account just for funzies, send me a DM here with the email you used to sign up with and i'll bypass it for you.
- this is not secure! at all! I did nothing to secure it! seriously this is just used for testing purposes! When the workshop ends I'll shut it down and archive the toots as static pages! +
<@771783584105234462> [[WikiBot#Bugfixes]] just pushed an update to the wikibot that might fix the red X's you're getting - likely an error from when there isn't an avatar set, but the logs aren't being kept long enough back for me to see for sure. +
I've got a question that seems appropriate for this group, if anyone is interested in sticking around in this discord :).
So I spend a decent amount of time talking to [[Librarians]] [[Libraries]], and it always strikes me that they are a group of people with a ton of training and experience specifically in synthesis-like work but seem often stymied by their tools, often for lack of resources. I should have asked earlier, are there any other libraries-adjacent people in this chat?
Here's a question for whoever is interested: what would you do (what tools, what would your workflow look like) for [[Manual Curation]] of thousands of papers from structured queries across multiple databases, with curation criteria that include
a) reasonably specific/computable **minimum standards** (peer-reviewed, word count, etc.) and
b) **topic standards** that are a series of keywords, but rely on someone doing manual curation to be able to recognize an intuitive n-depth similarity to the specific keywords +
encouraging the use of the thread for the sake of people's notifications as we enter slow-mode.
sidebar: this to me is one of the more interesting uses of this kind of wiki-bot, in a more long-lived chat and communication medium (glad 2 have <@708787219992805407> here for the long-timescales perspective btw). in both this and any future workshops, being able to plug in something like a wikibot that can let different threads get tagged to common concepts through time to different/overlapping discord servers and output to potentially multiple overlapping wikis is v interesting to me.
I'm gonna continue to make it easier to deploy because i feel like the [[Garden and Stream]] metaphor is one that can unfold on multiple timescales, and it would be cool to build out the ability to make that easier: how cool would it be if you didn't have to decide on a chat/document medium or have to make a new set at the start of an organizing project since it was arbitrary anyway and your infra supported use and crossposting across many media.
Eg. the very understanding surfacing of [[The Google Docs Problem]] because of [[Mediawiki]]'s lack of [[Synchronous Editing]] [[Live Editing]] and the need to remember to link out to external services rather than that being a natural expectation of a multimodal group and having systems that explicitly support that is illustrative to me. Maybe one description is being able to deploy a [[Context of Interoperability]] [[Interoperability]]: during this time period I am intending these documents/discord servers/hashtags/social media accounts/etc. to be able to crosspost between each other so that everyone needs to to as little as possible to make their workflows align +
Also I am doing another [[Sorry Anagora]] (https://anagora.org/sorry-anagora) by speculating about the overlay syntax in-medium, but the need for repeated wikilinks above there revives my interest in recursive wikilinks that can be used in overlapping terms +
in thinking about some of the problems from this weekend like the (affectionately titled) [[The Google Docs Problem]] and various other interface problems with the wiki, where it'll always be easier for people to interact with a system from something they're more used to using, I've been thinking about a more generalized kind of bridging where one can set a [[Context of Interoperability]] where for a given workshop, time period, project, etc. people can plug their tools together and work in a shared space without needing to make all of them anew - so for the simple example of this discord and this wiki, it should be possible to reuse this space to eg. connect to a different (or multiple) wikis, and vice versa to have a different discord connect to it. Along those lines, being able to have a synchronizing eg. git repository of the pages on the wiki so that people could edit them in obsidian or logseq or whatever their tool of choice is... this feels like an incredibly generic idea, so I feel like there must already be a ton of work on it, but it feels like it starts by just making a framework for bridging where the n-to-n problem is simplified by having a set of tools for auth and format translation and modeling documents and messages... I'm going to start sketching one piece of that with the [[Mediawiki-Git Bridge]], but I'm curious to hear if anyone either has any ideas, prior experience, or unmet needs that I might be orbiting around here +
This project, [[Git-Mediawiki]] looks pretty good: https://github.com/Git-Mediawiki/Git-Mediawiki
I'm gonna see if i can get a further translating layer between wiki markup and markdown going, thank god for [[Pandoc]] +
<@743886679554654299> brilliant idea for a [[Local Algorithm]] [[Parametrization]] along the lines of using the [[Medium as Storage]] and parametrization from a conversation I was having just now +
check this out. [[DIY Algorithms]]. instead of adding accounts to lists and autopopulating, you can directly add posts themselves. so then you can rig up whatever the frick algorithm you want to masto:
https://social.coop/@jonny/109545449455062668
https://github.com/sneakers-the-rat/mastodon/tree/feature/postlists +
I would suggest turning [[Discord#Notifications]] off for this channel. on mobile click the person looking icon in the top right and then the notification options are near the top. on desktop there should be a bell-looking icon along the top row of icons +
Just added a "proposal" tag to our discussion. In scientific discourse, that would be a category used in opinion papers etc. Is this already part of the [[Discourse Graph]] repertory? +
we think the problem now is user-friendly tools and workfows that can create discourse graph structures, and have seen some exciting progress across a bunch of new user-facing "personal wikis". but bridging from personal to communal is still a challenge, partially bc of tooling.
this is why i'm excited about the [[Discourse Modeling]] idea, which i sort of understand as a way to try to instantiate something like [[Discourse Graphs]] into a wiki (bc wikis have a lot more in-built affordances for collaboration, such as edit histories, talk pages, etc.), which may hopefully lead to a lower barrier to entry for collaborative discourse graphing.
a high hope is that we can develop a process that is easy enough to understand and implement that can then be applied to discourse graphing the IPCC or similarly large body of research on a focused, contentious, interdisciplinary topic.
other examples include:
- effects of masks on community transmission (can't do decisive RCTs, need to synthesize)
- effects of social media on political (dys)function: (existing crowdsourced lit review here, in traditional narrative form: https://docs.google.com/document/d/1vVAtMCQnz8WVxtSNQev_e1cGmY9rnY96ecYuAj6C548/edit#) +
we think the problem now is user-friendly tools and workfows that can create discourse graph structures, and have seen some exciting progress across a bunch of new user-facing "personal wikis". but bridging from personal to communal is still a challenge, partially bc of tooling.
this is why i'm excited about the [[Discourse Modeling]] idea, which i sort of understand as a way to try to instantiate something like [[Discourse Graphs]] into a wiki (bc wikis have a lot more in-built affordances for collaboration, such as edit histories, talk pages, etc.), which may hopefully lead to a lower barrier to entry for collaborative discourse graphing.
a high hope is that we can develop a process that is easy enough to understand and implement that can then be applied to discourse graphing the IPCC or similarly large body of research on a focused, contentious, interdisciplinary topic.
other examples include:
- effects of masks on community transmission (can't do decisive RCTs, need to synthesize)
- effects of social media on political (dys)function: (existing crowdsourced lit review here, in traditional narrative form: https://docs.google.com/document/d/1vVAtMCQnz8WVxtSNQev_e1cGmY9rnY96ecYuAj6C548/edit#) +