diff --git a/handbook/bankofexpo.html b/handbook/bankofexpo.html index c56ad5fd6..ec3f9f9d5 100644 --- a/handbook/bankofexpo.html +++ b/handbook/bankofexpo.html @@ -21,9 +21,40 @@

The split mechanism transparently underlies everything, but for user-friendliness there are various handy web-forms provided which generate the split tables (`Transaction Groups'). These range from a simple person-to-person swap, to a customizable `Event' with costs for various items being automatically squirrelled away into pre-set cost-pools." +

Source and docs for the upstream version are online at https://github.com/malc0/BoC which has a link to a demonstration system that you can play with (CUCC meets 2014-15).

+ +

Configure BOE for a new Expo

+

In /home/expo/boe create a new folder for the data , e.g. for 2029: +

+and a new folder to hold last-year's code: + +Copy everything from /home/expo/boe/boc/ into /home/expo/boe/boc-2028/ +and then edit the first line of the file /home/expo/boe/boc/boc_config to read: +
+Root	/home/expo/boe/data/boe29
+TemplateDir	resources
+#StyleURL /boe/boc/resources/bocstyle.css
+#StyleURL /boe/boc/boc.pl?serve=bocstyle
+#TimeoutURL /boe/boc/resources/timeout.js
+
+Now the code is in the place that the webserver expects it, and the code is configured to point to the new data for 2029. +

+Now copy everything in the most recent year from, e.g. /home/expo/boe/boc-2028/ into /home/expo/boe/boc-2029/ . +Then go into the folder /home/expo/boe/data/boe29/ and delete the files for all the users except for you and wookey. +(Assuming you were on expo in the previous year). +Edit your file to have the line +

+IsAdmin
+
From this point on all the configuration you do with be directly with the online BoE running on the server. Set up a password for yourself is the first thing to do. + +

Now read the the documentation (PDF) (for the version running on the expo server).

-

Source and docs for the upstream version are online at https://github.com/malc0/BoC which has a link to a demonstration system that you can play with (CUCC meets 2014-15).

+
Go back to Expo Treasurer Role
diff --git a/handbook/i/lloyds-card-reader.jpg b/handbook/i/lloyds-card-reader.jpg new file mode 100644 index 000000000..dac8e558e Binary files /dev/null and b/handbook/i/lloyds-card-reader.jpg differ diff --git a/handbook/natwest-cr.jpg b/handbook/natwest-cr.jpg deleted file mode 100644 index d59c70e5e..000000000 Binary files a/handbook/natwest-cr.jpg and /dev/null differ diff --git a/handbook/treasurer.html b/handbook/treasurer.html index f1ad303eb..f27c5a8f2 100644 --- a/handbook/treasurer.html +++ b/handbook/treasurer.html @@ -88,9 +88,9 @@
- +
-NatWest card-reader +Lloyds card-reader
@@ -103,11 +103,6 @@ Online access at Lloyds was Microsoft Authenticator app on a phone or a hardware key such as Yubikey: see MFA enrollment. - -Natwest requires special NatWest hardware or biometric -configuration. - You need to send all your details to the previous expo treasurer with the form so that he/she can sign it and send it to the bank. These are @@ -123,20 +118,8 @@ can sign it and send it to the bank. These are
  • selfie photo - -
    -
    - -
    -NatWest webpage -
    -
    -
    -

    EDIT: we use Lloyds not NatWest now. - -

    The bank is the Market Street branch of Nat West, which is where you get the paper mandate form. Expo a/c 22997253. See below for how to operate the account. -

    In 2023 NatWest are now moving to an online method (click on "Add an account holder") for adding account holders. Try it out and then edit this page to include the new instructions. - +

    The bank is the Sidney Street branch of Lloyds, which is where you get the paper mandate form. Expo is in the name "CUCC Expo" and if you have trouble, the bank account number is on the expo server in /home/expo/boe/accountnumber.txt. +

    The next most urgent thing: Accounting policy

    Study the previous expo accounting policies and write one specifically for the coming expo you will be managing. Then everyone knows which policy is "active" and you won't get conflicting requests from incompatible historic approaches.