expoweb/handbook/computing/newyear.html

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>CUCC Expedition Handbook: Programmers manual</title>
<link rel="stylesheet" type="text/css" href="/css/main2.css" />
</head>
<body>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>
<h1>New Expo Maintenance - Creating a New Year</h1>

<h2><a id="manual">Creating a New Year in the Expo online systems</a></h2>

<ul>

<li>This page <i>is a checklist for programmers</i> who are configuring the systems for next year's expo .
  <li>We are steadily automating these tasks, so the list is shorter every year.
</ul>

<h3>Adding a new year in the Expo online systems</h3>

<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly 
overwriting what is on the server. Changes to <var>:expoweb:</var> and <var>:troggle:</var> must be done using the version control 
system as these are <a href="../computing/repos.html">repositories</a>.
<p>[Many website pages generated by troggle will fail for the new year you are creating until you do the folk-update process 
to create a new year column (see below). ]


    <h4>Well before Expo as these pages are used in planning</h4>
<ul>
<li>Manually edit these HTML pages as lots of other pages link to them and they are not troggle pages. Longer job, replace each of these hard-coded HTML pages with a troggle page.
<ul>
    <li>Edit <a href="/infodx.htm">expoweb/infodx.htm</a> with the new year number (top and bottom). -  130 pages link to this...
    <li>Edit <a href="/pubs.htm">expoweb/pubs.htm</a> with the new year number. -  165 pages link to this...
    <li>Edit <a href="/index.htm">expoweb/index.htm</a> - edit the title and make it link to e.g. <var>expoweb/years/2025/</var> - 1,212 pages link to this...
</ul>

<li><strike>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo. </strike>  &nbsp; Now automatic, after 31st Dec.
<li>edit <var>troggle/templates/walletform.html</var> - change to this coming year
<li>copy the contents of the previous year's <var>expoweb/years/</var> folder, e.g. /2016/ to /2017/ and edit all the files therein. You should start with at least an index.html and a mission.html
<li>edit <var>expoweb/folk/folk.csv</var> - see below - just to add a column for the coming year. Until that year column exists, the online system will be unaware that there is an expedition that year.
  <li>Create the Bank of Expo <a href="../bankofexpo.html"><var>boe</var></a> for the expected attendees. 
    This is done directly in an <var>ssh</var> terminal session on the server.</li>
<li>Create a new <var>expoweb</var> website folder e.g. /2025/ in 
<ul>
<li>expoweb/years/
</ul>
</ul>

<h4>Whenever you like before Expo</h4>
<ul>
    <li>Create new subfolders e.g. /2025/ in <var>expofiles/</var>, in each of
        <ul>
        <li>expofiles/writeups/
        <li><strike>expofiles/photos/</strike>  &nbsp; Now automatic, after 31st Dec.
        <li>expofiles/gpslogs/
        <li>expofiles/accounts/ - optional. Used for archiving after expo.
        <li>expofiles/videos/ - optional. We don't do this much.
        <li><s>expofiles/surveyscans/</s> - this now happens automatically when a wallet is created
       </ul>
    <li>Test that the bierbook and seshbook LaTeX scripts <a href="/documents/bierbook"><var>expoweb/documents/bierbook</var></a> work on your machine. Or use an online LaTeX system to generate them, e.g. <a href="https://www.overleaf.com/user/subscription/plans">Overleaf.com</a> (free plan, for the moment)</li>
    
</ul>

<h4>A week or so before Expo</h4>
<ul>
     <li>create initial versions of the bierbook and the seshbook in <var>expoweb/documents/bierbook</var> 
     (the final copies after expo will be scanned and put in 
       e.g. <var>expofiles/writeups/2025/</var> along with the scanned logbook). These need an updated <var>names.txt</var> file of expoers.</li>
  <li>update the gear tape colours for the expected expoers in <a href="../geartape.html"><var>/expoweb/handbook/geartape.html</var></a> </li>
      <li>edit <var>expoweb/folk/folk.csv</var> - see below - to add people. Until a name is recorded in the Folk file that person will not be recognised within the online system as a cave surveyor or logbook entry writer.</li>
</ul>
<p>Edit <var>expoweb/folk/folk.csv</var> according to the instructions in the <a href="folkupdate.html">Folk Update process</a>.
</p>

Return to the main <a href="manual.html">online systems manual</a>.

<hr /></body>
</html>
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
			`<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />`
			`<title>CUCC Expedition Handbook: Programmers manual</title>`
fix CSS link 2024-02-09 00:01:17 +00:00			`<link rel="stylesheet" type="text/css" href="/css/main2.css" />`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`</head>`
			`<body>`
Making handbook more consistent 2021-04-29 13:00:37 +01:00			`<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`<h2 id="tophead">CUCC Expedition Handbook - Online systems</h2>`
Making handbook more consistent 2021-04-29 13:00:37 +01:00			`<h1>New Expo Maintenance - Creating a New Year</h1>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00
			`<h2><a id="manual">Creating a New Year in the Expo online systems</a></h2>`

			`<ul>`

			`<li>This page <i>is a checklist for programmers</i> who are configuring the systems for next year's expo .`
add automation comment - online edit of handbook/computing/newyear.html 2024-02-07 21:13:46 +00:00			`<li>We are steadily automating these tasks, so the list is shorter every year.`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`</ul>`

			`<h3>Adding a new year in the Expo online systems</h3>`

Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<p>There is no script to do this (yet). In the list below everything in expofiles is done by directly`
			`overwriting what is on the server. Changes to <var>:expoweb:</var> and <var>:troggle:</var> must be done using the version control`
			`system as these are <a href="../computing/repos.html">repositories</a>.`
2022 updates 2022-02-24 12:29:51 +00:00			`<p>[Many website pages generated by troggle will fail for the new year you are creating until you do the folk-update process`
			`to create a new year column (see below). ]`


Preparing for 2021 Expo, deleting 2020 expo 2021-02-05 13:07:47 +00:00			`<h4>Well before Expo as these pages are used in planning</h4>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`<ul>`
next year auto for wallets 2024-03-14 23:59:57 +00:00			`<li>Manually edit these HTML pages as lots of other pages link to them and they are not troggle pages. Longer job, replace each of these hard-coded HTML pages with a troggle page.`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`<ul>`
next year auto for wallets 2024-03-14 23:59:57 +00:00			`<li>Edit <a href="/infodx.htm">expoweb/infodx.htm</a> with the new year number (top and bottom). - 130 pages link to this...`
			`<li>Edit <a href="/pubs.htm">expoweb/pubs.htm</a> with the new year number. - 165 pages link to this...`
			`<li>Edit <a href="/index.htm">expoweb/index.htm</a> - edit the title and make it link to e.g. <var>expoweb/years/2025/</var> - 1,212 pages link to this...`
more automation 2024-03-14 21:36:26 +00:00			`</ul>`
next year auto for wallets 2024-03-14 23:59:57 +00:00
			`<li><strike>edit <var>troggle/templates/base.html</var> - change the title and add a link to this year's expo. </strike>   Now automatic, after 31st Dec.`
Next year planning updates 2022-10-15 21:31:01 +03:00			`<li>edit <var>troggle/templates/walletform.html</var> - change to this coming year`
Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<li>copy the contents of the previous year's <var>expoweb/years/</var> folder, e.g. /2016/ to /2017/ and edit all the files therein. You should start with at least an index.html and a mission.html`
2022 updates 2022-02-24 12:29:51 +00:00			`<li>edit <var>expoweb/folk/folk.csv</var> - see below - just to add a column for the coming year. Until that year column exists, the online system will be unaware that there is an expedition that year.`
Move 'make new BOE year' earlier in the process. - online edit of handbook/computing/newyear.html 2023-02-15 20:31:43 +00:00			`<li>Create the Bank of Expo <a href="../bankofexpo.html"><var>boe</var></a> for the expected attendees.`
			`This is done directly in an <var>ssh</var> terminal session on the server.</li>`
more automation 2024-03-14 21:36:26 +00:00			`<li>Create a new <var>expoweb</var> website folder e.g. /2025/ in`
			`<ul>`
			`<li>expoweb/years/`
			`</ul>`
Preparing for 2021 Expo, deleting 2020 expo 2021-02-05 13:07:47 +00:00			`</ul>`

			`<h4>Whenever you like before Expo</h4>`
			`<ul>`
starting 2025 updates 2024-03-14 18:32:52 +00:00			`<li>Create new subfolders e.g. /2025/ in <var>expofiles/</var>, in each of`
Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<ul>`
			`<li>expofiles/writeups/`
next year auto for wallets 2024-03-14 23:59:57 +00:00			`<li><strike>expofiles/photos/</strike>   Now automatic, after 31st Dec.`
Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<li>expofiles/gpslogs/`
			`<li>expofiles/accounts/ - optional. Used for archiving after expo.`
			`<li>expofiles/videos/ - optional. We don't do this much.`
Fixups for next-expo pages 2022-10-15 22:21:50 +03:00			`<li><s>expofiles/surveyscans/</s> - this now happens automatically when a wallet is created`
			`</ul>`
next year auto for wallets 2024-03-14 23:59:57 +00:00			`<li>Test that the bierbook and seshbook LaTeX scripts <a href="/documents/bierbook"><var>expoweb/documents/bierbook</var></a> work on your machine. Or use an online LaTeX system to generate them, e.g. <a href="https://www.overleaf.com/user/subscription/plans">Overleaf.com</a> (free plan, for the moment)</li>`
Next year planning updates 2022-10-15 21:31:01 +03:00
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`</ul>`
Preparing for 2021 Expo, deleting 2020 expo 2021-02-05 13:07:47 +00:00
			`<h4>A week or so before Expo</h4>`
			`<ul>`
Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<li>create initial versions of the bierbook and the seshbook in <var>expoweb/documents/bierbook</var>`
			`(the final copies after expo will be scanned and put in`
starting 2025 updates 2024-03-14 18:32:52 +00:00			`e.g. <var>expofiles/writeups/2025/</var> along with the scanned logbook). These need an updated <var>names.txt</var> file of expoers.</li>`
Move 'make new BOE year' earlier in the process. - online edit of handbook/computing/newyear.html 2023-02-15 20:31:43 +00:00			`<li>update the gear tape colours for the expected expoers in <a href="../geartape.html"><var>/expoweb/handbook/geartape.html</var></a> </li>`
			`<li>edit <var>expoweb/folk/folk.csv</var> - see below - to add people. Until a name is recorded in the Folk file that person will not be recognised within the online system as a cave surveyor or logbook entry writer.</li>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`</ul>`
Creating Expo 2021 and documenting annual updates 2021-02-05 20:08:22 +00:00			`<p>Edit <var>expoweb/folk/folk.csv</var> according to the instructions in the <a href="folkupdate.html">Folk Update process</a>.`
Documenting how to add a new year and new people in folk.csv and test that it works by running the databaseRest.py people command 2020-02-21 00:23:59 +00:00			`</p>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00
Moving online systems overview and computing manual pages 2020-04-09 19:13:18 +01:00			`Return to the main <a href="manual.html">online systems manual</a>.`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00
Making handbook more consistent 2021-04-29 13:00:37 +01:00			`<hr /></body>`
Extracted the bit about creating a new year in the online systems into a separate file 2019-12-29 00:36:42 +00:00			`</html>`