Search by property
This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.
List of results
- WikiBot#Konrad Hinsen-22-11-13 08:26:56 + (Thanks <@322545403876868096> ! Added to https://synthesis-infrastructures.wiki/Discourse_Modeling. I guess I could have used [[Wikibot]] for that, but it was easier to do it by hand than figuring out the intricacies of Wikibot.)
- Discord Messages#Konrad Hinsen-22-11-13 08:26:56 + (Thanks <@322545403876868096> ! Added to https://synthesis-infrastructures.wiki/Discourse_Modeling. I guess I could have used [[Wikibot]] for that, but it was easier to do it by hand than figuring out the intricacies of Wikibot.)
- Discord Messages#petermr-22-11-15 10:57:35 + (Thanks for [[Glamorous Toolkit]] … Thanks for [[Glamorous Toolkit]] . Watched the video and understood most of it. Impressive, and maybe the future, but not quite what I wanted now - it requires a fluency with creating new types of object on the fly and so a change in orientation. I want something that I can tag the methods with (say) 'PDF conversion', 'prototype`, etc. I don't mind dumping that as static docs and navigating with Obsidian. static docs and navigating with Obsidian.)
- Glamorous Toolkit#petermr-22-11-15 10:57:35 + (Thanks for [[Glamorous Toolkit]] … Thanks for [[Glamorous Toolkit]] . Watched the video and understood most of it. Impressive, and maybe the future, but not quite what I wanted now - it requires a fluency with creating new types of object on the fly and so a change in orientation. I want something that I can tag the methods with (say) 'PDF conversion', 'prototype`, etc. I don't mind dumping that as static docs and navigating with Obsidian. static docs and navigating with Obsidian.)
- Discord Messages#Konrad Hinsen-22-11-11 05:26:42 + (That said, the more abstract idea of defin … That said, the more abstract idea of defining a data model plus execution semantics that any programming language can plug into looks very promising. That aspect of WikiLambda was in fact one of my inspirations for developing [[Digital Scientific Notations]].[[Digital Scientific Notations]].)
- Digital Scientific Notations#Konrad Hinsen-22-11-11 05:26:42 + (That said, the more abstract idea of defin … That said, the more abstract idea of defining a data model plus execution semantics that any programming language can plug into looks very promising. That aspect of WikiLambda was in fact one of my inspirations for developing [[Digital Scientific Notations]].[[Digital Scientific Notations]].)
- WikiBot#sneakers-the-rat-22-11-02 08:17:07 + (Then i just made a page to link to the pages. There's not really a well defined way to do meta-categorization like that in-medium as far as I'm aware, but am happy to receive [[WikiBot#Feature Requests]] about it)
- Discord Messages#sneakers-the-rat-22-11-02 08:17:07 + (Then i just made a page to link to the pages. There's not really a well defined way to do meta-categorization like that in-medium as far as I'm aware, but am happy to receive [[WikiBot#Feature Requests]] about it)
- Discord Messages#joelchan86-22-11-11 14:08:30 + (These tools are still not entirely mainstr … These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!</br></br>IMO the best way to get a feel for what they are is to see some examples/videos.</br></br>I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s</br></br>I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417ntly gave: https://youtu.be/jH-QF7rVSeo?t=1417)
- Roam Discourse Graph extension#joelchan86-22-11-11 14:08:30 + (These tools are still not entirely mainstr … These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!</br></br>IMO the best way to get a feel for what they are is to see some examples/videos.</br></br>I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s</br></br>I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417ntly gave: https://youtu.be/jH-QF7rVSeo?t=1417)
- Roam#joelchan86-22-11-11 14:08:30 + (These tools are still not entirely mainstr … These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!</br></br>IMO the best way to get a feel for what they are is to see some examples/videos.</br></br>I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s</br></br>I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417ntly gave: https://youtu.be/jH-QF7rVSeo?t=1417)
- Logseq#joelchan86-22-11-11 14:08:30 + (These tools are still not entirely mainstr … These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!</br></br>IMO the best way to get a feel for what they are is to see some examples/videos.</br></br>I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s</br></br>I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417ntly gave: https://youtu.be/jH-QF7rVSeo?t=1417)
- Notion#joelchan86-22-11-11 14:08:30 + (These tools are still not entirely mainstr … These tools are still not entirely mainstream compared to tools like [[Notion]], which is related to your experience trying to learn more about the tools - so they tend to have a steep learning curve!</br></br>IMO the best way to get a feel for what they are is to see some examples/videos.</br></br>I like this video for an overview of [[Logseq]]: https://www.youtube.com/watch?v=ZtRozP8hfEY&t=6s</br></br>I describe [[Roam]] and the [[Roam Discourse Graph extension]] in this portion of a talk I recently gave: https://youtu.be/jH-QF7rVSeo?t=1417ntly gave: https://youtu.be/jH-QF7rVSeo?t=1417)
- Discord Messages#sneakers-the-rat-22-11-14 23:15:29 + (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]])
- Pandoc#sneakers-the-rat-22-11-14 23:15:29 + (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]])
- Git-Mediawiki#sneakers-the-rat-22-11-14 23:15:29 + (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]])
- Collaboration#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- Standards#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- Reading List#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- Linked Data#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- ActivityPub#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- Discord Messages#sneakers-the-rat-22-11-08 23:32:39 + (To add to the [[Reading List#Linked Data]] … To add to the [[Reading List#Linked Data]] on [[Linked Data]], [[Standards]], and [[Collaboration]]: a piece from one of the authors of [[ActivityPub]] on the merger of the distributed messaging and linked data communities that I think puts into context what a massive achievement AP was</br>http://dustycloud.org/blog/on-standards-divisions-collaboration/blog/on-standards-divisions-collaboration/)
- Discord Messages#petermr-22-11-15 10:44:45 + (We have been developing code for extractio … We have been developing code for extraction of "claims" from IPCC [[executive summary]]s . <@322545403876868096> <@499904513038090240> So far we have the following design:</br>* exec summary for chapter => 15-20 paras</br>* bold leading sentence for each para => leading_claim</br>* subsequent sentences => supporting_claims</br>* annotation (highsubsequent sentences => supporting_claims * annotation (high)
- Executive summary#petermr-22-11-15 10:44:45 + (We have been developing code for extractio … We have been developing code for extraction of "claims" from IPCC [[executive summary]]s . <@322545403876868096> <@499904513038090240> So far we have the following design:</br>* exec summary for chapter => 15-20 paras</br>* bold leading sentence for each para => leading_claim</br>* subsequent sentences => supporting_claims</br>* annotation (highsubsequent sentences => supporting_claims * annotation (high)
- Discord Messages#petermr-22-11-13 09:08:25 + (Yes, as a scientist I also made this assumption. For example the [[IPCC report]] is 10,000 pages of scientific discourse. Hmm!)
- IPCC report#petermr-22-11-13 09:08:25 + (Yes, as a scientist I also made this assumption. For example the [[IPCC report]] is 10,000 pages of scientific discourse. Hmm!)
- Discord Messages#Konrad Hinsen-22-11-13 13:07:02 + (Yes, that's a prominent use case for [[Glamorous Toolkit]].)
- Glamorous Toolkit#Konrad Hinsen-22-11-13 13:07:02 + (Yes, that's a prominent use case for [[Glamorous Toolkit]].)
- A System for Interleaving Discussion and Summarization in Online Collaboration#sneakers-the-rat-22-11-12 16:02:25 + ([[A System for Interleaving Discussion and Summarization in Online Collaboration#Evidence]] This section of the document references some [[Other Work]])
- Other Work#sneakers-the-rat-22-11-12 16:02:25 + ([[A System for Interleaving Discussion and Summarization in Online Collaboration#Evidence]] This section of the document references some [[Other Work]])
- Discord Messages#sneakers-the-rat-22-11-12 16:02:25 + ([[A System for Interleaving Discussion and Summarization in Online Collaboration#Evidence]] This section of the document references some [[Other Work]])
- Blue Obelisk#petermr-22-11-13 09:06:34 + ([[Blue Obelisk]] is (i.e. still active) a … [[Blue Obelisk]] is (i.e. still active) a remote asynchronous collaboration with no central management or funding. A large part consists of nodes representing software packages. See [[https://en.wikipedia.org/wiki/Blue_Obelisk]]. It works because several of the authors knew/know each other and agreed at the outset to adopt an interoperability mantra "Open Data, Open Standards, Open Source" (ODOSOS). </br>Because everyone agrees the same approach to interoperability the nodes can develop indeoendently! The management is informal - a mailing list and occasional back channels. So there is a collaborative network - see WP article. a collaborative network - see WP article.)
- Https://en.wikipedia.org/wiki/Blue Obelisk#petermr-22-11-13 09:06:34 + ([[Blue Obelisk]] is (i.e. still active) a … [[Blue Obelisk]] is (i.e. still active) a remote asynchronous collaboration with no central management or funding. A large part consists of nodes representing software packages. See [[https://en.wikipedia.org/wiki/Blue_Obelisk]]. It works because several of the authors knew/know each other and agreed at the outset to adopt an interoperability mantra "Open Data, Open Standards, Open Source" (ODOSOS). </br>Because everyone agrees the same approach to interoperability the nodes can develop indeoendently! The management is informal - a mailing list and occasional back channels. So there is a collaborative network - see WP article. a collaborative network - see WP article.)
- Discord Messages#petermr-22-11-13 09:06:34 + ([[Blue Obelisk]] is (i.e. still active) a … [[Blue Obelisk]] is (i.e. still active) a remote asynchronous collaboration with no central management or funding. A large part consists of nodes representing software packages. See [[https://en.wikipedia.org/wiki/Blue_Obelisk]]. It works because several of the authors knew/know each other and agreed at the outset to adopt an interoperability mantra "Open Data, Open Standards, Open Source" (ODOSOS). </br>Because everyone agrees the same approach to interoperability the nodes can develop indeoendently! The management is informal - a mailing list and occasional back channels. So there is a collaborative network - see WP article. a collaborative network - see WP article.)
- Page Schemas#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Page Forms#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Category:Participant#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Discord Messages#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Jodi Schneider#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Kyle MacLaury#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Graham Johnson#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Jonny Saunders#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Joseph Chee Chang#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Katherine Baney#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Angelina Lesnikova#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Matthew Akamatsu#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Ronen Tamari#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Finn Macken#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Belinda Mo#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Leo Ware#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Pao Siangliulue#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)
- Brad DeGraf#sneakers-the-rat-22-11-12 19:32:48 + ([[Page Schemas#Creating a new Schema]] Pag … [[Page Schemas#Creating a new Schema]]</br>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.</br></br>For an example of how this shakes out, see</br>[[:Category:Participant]]</br>[[Template:Participant]]</br>[[Form:Participant]]</br></br>* go to a `Category:CategoryName` page, creating it if it doesn't already exist.</br>* Click "Create schema" in top right</br>* 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)</br>* Click "add template" If you are only planning on having one template per category, name the template the same thing as the category.</br>* 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.</br>* Once you're finished, save the schema</br>* 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. take a few minutes, bc it's pretty buggy.)