Create and Query Tables: Difference between revisions
Malcolmmcc (talk | contribs) No edit summary |
Malcolmmcc (talk | contribs) No edit summary |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<data table="E-Week 2019" fields=" | <data table="E-Week 2019" fields="Event,Read,Description,Location,Start,End,DoubleSub,RankTier,Scale,Points,ASAscore,BUSSscore,BREEscore,CEUSscore,CHESSscore,CMEUSscore,ECSESSscore,MAMEscore,MEUSscore,OLDscore,ASAplace,BUSSplace,BREEplace,CEUSeach,CEUSplace,CHESSplace,CMEUSplace,ECSESSeach,ECSESSplace,MAMEeach,MAMEplace,MEUSplace,OLDplace,DamnThing,ASAdt,BUSSdt,BREEdt,CEUSdt,CHESSdt,CMEUSdt,ECSESSdt,MAMEdt,MEUSdt,OLDdt"> | ||
{{E-Wiki 2019}}</data> | |||
</data> | |||
Preyansh, this might be way more complicated than you had in mind, so forgive me. I think it could be more automated, but if you'd rather another way it's ALL YOURS! This was fun for me, so if you want another way that's all good. | Preyansh, this might be way more complicated than you had in mind, so forgive me. I think it could be more automated, but if you'd rather another way it's ALL YOURS! This was fun for me, so if you want another way that's all good. | ||
So in short here's what's going on. If the coords have a table that has the data laid out as below, where ''' | So in short here's what's going on. If the coords have a table that has the data laid out as below, where '''Start''' and '''End''' are the YmdHi (concatenated timestamp sans seconds), we can insert that as comma separated syntax (see [[#The Data|the data]]) and then have it output in a table or other sort of fashion. This allows us to have all the event information accessible and reformattable from one location, as opposed to having to update say three locations at once. | ||
==The Input== | ==The Input== | ||
<pre> | <pre> | ||
<data table="E-Week 2019" fields=" | <data table="E-Week 2019" fields="Start,End,Event,Location,Points,Rank/Tier,DoubleSub,Description,ASA,BUSS,BREE,CEUS,CHESS,CMEUS,ECSESS,MAME,MEUS,OLD"> | ||
201811271700,101811271830,Captain's Challenge,[[Blues Pub]],0,N/A,No,The captain's go on a hunt for clues! | 201811271700,101811271830,Captain's Challenge,[[Blues Pub]],0,N/A,No,The captain's go on a hunt for clues!,10,20,30,40,50,60,70,80,90,100 | ||
201811271930,201811280230,Bus Trip to Nowhere,Nowhere,400,Ranked,No,TripleBogieNoDescription | 201811271930,201811280230,Bus Trip to Nowhere,Nowhere,400,Ranked,No,TripleBogieNoDescription,1,2,3,4,5,6,7,8,9,10 | ||
201811280900,201811281000,Breakfast,Common Room,150,Tiered,No,This is where you eat food， points for participation | 201811280900,201811281000,Breakfast,Common Room,150,Tiered,No,This is where you eat food， points for participation,100,200,300,400,500,600,700,800,900,10000 | ||
201811281030,201811281430,Sports,Lower West Field,500,Ranked,Yes,You play the sports here | 201811281030,201811281430,Sports,Lower West Field,500,Ranked,Yes,You play the sports here,1000,2000,3000,4000,5000,6000,7000,8000,9000,10000 | ||
</data> | </data> | ||
| Line 21: | Line 17: | ||
==The Data== | ==The Data== | ||
I've not yet gone over with you what these alternative databases are.... In short, it's like mySQL but accessible to queries inside of the wiki. So when we input the information below, it creates and inserts information into a table called '''[[Table:E-Week 2019]]''' into the different fields we specify. Below is a full table of what is contained in that table, and will auto update as the information above is altered. It does not store anything, so if the above text is removed the table would have no information. | I've not yet gone over with you what these alternative databases are.... In short, it's like mySQL but accessible to queries inside of the wiki. So when we input the information below, it creates and inserts information into a table called '''[[Table:E-Week 2019]]''' into the different fields we specify. Below is a full table of what is contained in that table, and will auto update as the information above is altered. It does not store anything, so if the above text is removed the table would have no information. | ||
<repeat table="E-Week 2019"></repeat> | <tab collapsed><repeat table="E-Week 2019"></repeat></tab> | ||
==Output Examples== | ==Output Examples== | ||
Now that it's all neat and tidy in one place, you can query it! So you can say things like | Now that it's all neat and tidy in one place, you can query it! So you can say things like | ||
Start>201811280000 | |||
Day = Tuesday | Day = Tuesday | ||
Points = 500 | Points = 500 | ||
Or a combination therein. Better yet, you can format the ''' | Or a combination therein. Better yet, you can format the '''Start''' and '''End''' using <code><nowiki>{{#time:FORMAT|STRING}}</nowiki></code> parser functions to change the string into 6:00PM, Tuesday, or other date/time formats. | ||
As far as I can tell, there's not an easy way to give viewers access to that kind of querying, but that's OK. | As far as I can tell, there's not an easy way to give viewers access to that kind of querying, but that's OK. | ||
| Line 41: | Line 37: | ||
|- | |- | ||
</header> | </header> | ||
{{#ifexpr:{{{ | {{#ifexpr:{{{Start|0}}}>201811271900|{{Test3|1={{{Event}}}|2={{{Location}}}|3={{#time:H:iA|{{{End}}} }} }}| | ||
|{{Test3|1={{{Event}}}|2={{{Location}}}|3={{#time:H:iA|{{{ | |||
}} | }} | ||
<footer> | <footer> | ||
| Line 48: | Line 43: | ||
</footer> | </footer> | ||
</repeat> | </repeat> | ||
===Bulleted=== | ===Bulleted=== | ||
;Criteria | ;Criteria | ||
| Line 53: | Line 49: | ||
---- | ---- | ||
<repeat table="E-Week 2019">{{#ifexpr:{{{ | <repeat table="E-Week 2019">{{#ifexpr:{{{Start}}}>201811271900 | ||
|{{Test4|1={{{Event}}}|2={{{Location}}}}} | |{{Test4|1={{{Event}}}|2={{{Location}}}}} | ||
}}</repeat> | }}</repeat> | ||