Category:Participant: Difference between revisions
No edit summary |
(→Discord: new section) |
||
(One intermediate revision by the same user not shown) | |||
Line 487: | Line 487: | ||
</PageSchema> | </PageSchema> | ||
A workshop participant! See [[Participants]] | A workshop participant! See | ||
* [[Participants]] | |||
* [[Form:Participant]] | |||
* [[Template:Participant]] | |||
== 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 | |||
}} |
Latest revision as of 19:31, 12 November 2022
Page schema | |
Form: Participant | |
standardInputs | |
Template: Participant | |
format | infobox |
Connecting property | |
Field: Timezone | |
Label | Timezone |
Form input | |
Input type | combobox |
existing values only | |
Semantic property: Timezone | |
Type | Text |
AllowedValue | WET (GMT+00:00/GMT+01:00) |
Field: Homepage | |
List | |
Display | nonempty |
Label | Homepage(s) |
Form input | |
Input type | text |
Semantic property: Has Homepage | |
Type | URL |
Field: Affiliation | |
List | |
Display | nonempty |
Label | Institutional Affiliation(s) |
Form input | |
Input type | tokens |
(optional) | |
Semantic property: Affiliated With | |
Type | Page |
Field: Projects | |
List | |
Display | nonempty |
Label | Relevant Projects |
Form input | |
Input type | tokens |
(optional) | |
Semantic property: Associated with | |
Type | Page |
Field: Interests | |
List | |
Display | nonempty |
Label | Topic Interests |
Form input | |
Input type | tokens |
Semantic property: Interested In | |
Type | Page |
Field: ORCID | |
Display | nonempty |
Label | ORCID |
Form input | |
Input type | text |
(optional) | |
Semantic property: Has ORCID | |
Type | External identifier |
Field: Twitter | |
Display | nonempty |
Label | Twitter Handle |
Form input | |
Input type | text |
(optional, without @) | |
Semantic property: Has Twitter Handle | |
Type | External identifier |
Field: Fediverse | |
Display | nonempty |
Label | Mastodon/Fediverse Handle |
Form input | |
Input type | text |
(optional, use full URL) | |
Semantic property: Has Fedi Handle | |
Type | URL |
Field: Github | |
Display | nonempty |
Label | GitHub handle |
Form input | |
Input type | text |
(optional) | |
Semantic property: Has Github Handle | |
Type | External identifier |
Field: Other Git Handles | |
List | |
Display | nonempty |
Label | Other Git Handles (Codeberg/GitLab/etc.) |
Form input | |
Input type | text |
(optional, use full URLs, separate multiple values with commas) | |
Semantic property: Has Git Handle | |
Type | URL |
Field: FOAF | |
Display | nonempty |
Label | FOAF URI |
Form input | |
Input type | text |
(optional) | |
Semantic property: Has FOAF | |
Type | URL |
Section: Submission Information | |
Level | 2 |
Template: Workshop Submission | |
format | sections |
Connecting property | |
Field: Interest | |
Label | What's your interest in this workshop? |
Form input | |
Input type | textarea |
Semantic property | |
Type | Page |
Field: Frame | |
Label | With what "frame" do you approach the workshop? (or identity)? |
Form input | |
Input type | dropdown |
Semantic property: Has Frame | |
Type | Text |
AllowedValue | Tool-builder |
Field: Materials | |
Label | What materials can you contribute to the workshop for consideration? |
Form input | |
Input type | textarea |
Semantic property | |
Type | Page |
Field: Organizer Topics | |
List | |
Label | Organizer-estimated Topics |
Form input | |
Input type | tokens |
Topics that the organizers interpreted from your application materials - feel free to edit these :) | |
Semantic property: Interested In | |
Type | Page |
A workshop participant! See
Discord
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.
Pages in category "Participant"
The following 58 pages are in this category, out of 58 total.