Create and Query Tables: Difference between revisions

(84 intermediate revisions by the same user not shown)

Line 1:

{{#~~time:"BANANA" H:i~~|~~5:30PM}}~~

{{E-Wiki 2019}}</data>

~~2018-11-27~~,~~5:00PM,6:30PM~~,Captain's Challenge,[[Blues Pub]],0,N/A,The captain's go on a hunt for clues!

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.

~~2018-11-27~~,~~7:30PM,2:30AM~~,Bus Trip to Nowhere,400,Ranked,~~TripleBogie~~

~~2018-11-28~~,9~~:00AM~~,10~~:00AM~~,Breakfast,150,~~Ranked~~,This is where you eat ~~food \,~~ points for participation

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.

~~2018-11-28~~,~~10:30AM~~,~~2:30PM~~,~~Sports~~,500,Ranked,

==The Input==

<pre>

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,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,100,200,300,400,500,600,700,800,900,10000

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>

</pre>

{{#time:Y-m-d|{{~~LOCALTIMESTAMP~~}}}}

==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.

==Output Examples==

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

Points = 500

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.

After all this you can create a <code><nowiki><repeat table="E-Week 2019"></nowiki></code> Repeat Table. The repeat tag will apply the syntax to every line that matches the query. For example, you can create a table or bullet separated or button separated or any kind of format that pulls the row's data, over and over.

===Table===

;Criteria

:Start Time < 201811271900 ''<small>({{#time:Y-m-d H:i|201811271900}})</small>''

{| class="wikitable"

! Event !! Location !!Time End

|-

</header>

{{#ifexpr:{{{Start|0}}}>201811271900|{{Test3|1={{{Event}}}|2={{{Location}}}|3={{#time:H:iA|{{{End}}} }} }}|

}}

|}

</footer>

</repeat>

===Bulleted===

;Criteria

:Start Time > 201811271900 ''<small>({{#time:Y-m-d H:i|201811271900}})</small>''

----

<repeat table="E-Week 2019">{{#ifexpr:{{{Start}}}>201811271900

|{{Test4|1={{{Event}}}|2={{{Location}}}}}

}}</repeat>

@@ Line 1: / Line 1: @@
-{{#time:"BANANA" H:i|5:30PM}}
+<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">
-<data table="E-Week19" fields="Day,Start,End,Event,Location,Points,Type,Double,Description">
+{{E-Wiki 2019}}</data>
--11-27,5:00PM,6:30PM,Captain's Challenge,[[Blues Pub]],0,N/A,The captain's go on a hunt for clues!
+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.
--11-27,7:30PM,2:30AM,Bus Trip to Nowhere,400,Ranked,TripleBogie
--11-28,9:00AM,10:00AM,Breakfast,150,Ranked,This is where you eat food \, points for participation
+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.
--11-28,10:30AM,2:30PM,Sports,500,Ranked,
+==The Input==
+<pre>
+<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!,10,20,30,40,50,60,70,80,90,100
+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,100,200,300,400,500,600,700,800,900,10000
+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>
-<repeat table="E-Week19" criteria="Day={{#time:Y-m-d|{{LOCALTIMESTAMP}}}}"></repeat>
+</pre>
-{{#time:Y-m-d|{{LOCALTIMESTAMP}}}}
+==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.
+<tab collapsed><repeat table="E-Week 2019"></repeat></tab>
+==Output Examples==
+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
+ Points = 500
+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.
+After all this you can create a <code><nowiki><repeat table="E-Week 2019"></nowiki></code> Repeat Table. The repeat tag will apply the syntax to every line that matches the query. For example, you can create a table or bullet separated or button separated or any kind of format that pulls the row's data, over and over.
+===Table===
+;Criteria
+:Start Time < 201811271900 ''<small>({{#time:Y-m-d H:i|201811271900}})</small>''
+<repeat table="E-Week 2019">
+<header>
+{| class="wikitable"
+! Event !! Location !!Time End
+|-
+</header>
+{{#ifexpr:{{{Start|0}}}>201811271900|{{Test3|1={{{Event}}}|2={{{Location}}}|3={{#time:H:iA|{{{End}}} }} }}|
+}}
+<footer>
+|}
+</footer>
+</repeat>
+===Bulleted===
+;Criteria
+:Start Time > 201811271900 ''<small>({{#time:Y-m-d H:i|201811271900}})</small>''
+----
+<repeat table="E-Week 2019">{{#ifexpr:{{{Start}}}>201811271900
+|{{Test4|1={{{Event}}}|2={{{Location}}}}}
+}}</repeat>