Form:Participant: Difference between revisions

Latest revision as of 19:31, 12 November 2022

This is the "Participant" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page.

Discord

sneakers-the-rat#discourse-modeling22-11-12 19:32:48

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.

@@ Line 10: / Line 10: @@
 {{{for template|Participant}}}
 {| class="formtable"
-! :
-| {{{field|}}}
 |-
 ! Timezone:
@@ Line 19: / Line 17: @@
 | {{{field|Homepage|input type=text}}}
 |-
-! (optional) Institutional Affiliation(s):
+! Institutional Affiliation(s): <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional)</p>
 | {{{field|Affiliation|input type=tokens}}}
 |-
-! (optional) Relevant Projects:
+! Relevant Projects: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional)</p>
 | {{{field|Projects|input type=tokens}}}
 |-
@@ Line 28: / Line 26: @@
 | {{{field|Interests|input type=tokens}}}
 |-
-! (optional) ORCID:
+! Groups(s)
+| {{{field|Group|input type=tokens|values from category=Group}}}
+|-
+! Table Assignment
+| {{{field|Table Assignment|input type=tokens}}}
+|-
+!  Discord Handle: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">of the form <code>handle#nnnn</code> where nnnn is a disambiguating number</p>
+| {{{field|Discord Handle|input type=text}}}
+|-
+!  ORCID: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional)</p>
 | {{{field|ORCID|input type=text}}}
 |-
-! (optional, without @) Twitter Handle:
+! Twitter Handle: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional, without @) </p>
 | {{{field|Twitter|input type=text}}}
 |-
-! (optional, use full URL) Mastodon/Fediverse Handle:
+! Mastodon/Fediverse Handle: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional, use full URL) </p>
 | {{{field|Fediverse|input type=text}}}
 |-
-! (optional) GitHub handle:
+! GitHub handle: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional)</p>
 | {{{field|Github|input type=text}}}
 |-
-! (optional, use full URLs, separate multiple values with commas) Other Git Handles (Codeberg/GitLab/etc.):
+! Other Git Handles (Codeberg/GitLab/etc.): <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional, use full URLs, separate multiple values with commas) </p>
 | {{{field|Other Git Handles|input type=text}}}
 |-
-! (optional) FOAF URI:
+! FOAF URI: <br><p class="pfFieldDescription" style="font-size:0.7em; color:gray;">(optional)</p>
 | {{{field|FOAF|input type=text}}}
 |}
@@ Line 54: / Line 61: @@
 |-
 ! With what "frame" do you approach the workshop? (or identity)?:
-| {{{field|Frame|input type=dropdown}}}
+| {{{field|Frame|input type=tokens}}}
 |-
 ! What materials can you contribute to the workshop for consideration?:
@@ Line 68: / Line 75: @@
 {{{standard input|free text|rows=10}}}
 </includeonly>
+== Discord ==
+{{Message
+|Author=sneakers-the-rat
+|Avatar=https://cdn.discordapp.com/avatars/305044217393053697/2970b22bd769d0cd0ee1de79be500e85.png?size=1024
+|Date Sent=22-11-12 19:32:48
+|Channel=discourse-modeling
+|Text=[[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.
+|Link=https://discord.com/channels/1029514961782849607/1038988750677606432/1041073096687370250
+}}