No edit summary
No edit summary
Line 8: Line 8:


If we miss a page then it is possible to go back - but it's not easy. I can restore an old version of the database and run the report against that data. That will produce a report correct for that point in time - but of course any other data that has changed since then (e.g. corrections, new titles, etc) will not be in that report. It also takes time and can only be done by me - so it's worth avoiding where possible.
If we miss a page then it is possible to go back - but it's not easy. I can restore an old version of the database and run the report against that data. That will produce a report correct for that point in time - but of course any other data that has changed since then (e.g. corrections, new titles, etc) will not be in that report. It also takes time and can only be done by me - so it's worth avoiding where possible.


==Event Updateable==
==Event Updateable==

Revision as of 12:26, 11 May 2022

Overview

There are several pages on the wiki which can be generated by any member of the wiki contributors team either to create them, or to update them if they need it. This page lists and links those pages along with an explanation of when they should be updated.

Workflow

The timing is crucial for some of these pages. A handful of them must be updated before the downtime code is run, a handful of them must be updated after downtime is run.

This is because the downtime code will remove anyone from a title if that title falls vacant at or during the next event. We make this change at the point where we run downtime because that's the one point we're guranteed to run an update - so it can't be overlooked - and because removing people from positions after downtime has closed and is being processed makes no difference to the players. But it does make a difference to the data that is put on the wiki pages - hence why it's important to run them at the right time.

If we miss a page then it is possible to go back - but it's not easy. I can restore an old version of the database and run the report against that data. That will produce a report correct for that point in time - but of course any other data that has changed since then (e.g. corrections, new titles, etc) will not be in that report. It also takes time and can only be done by me - so it's worth avoiding where possible.

Event Updateable

The following pages can be updated at any time during an event or before downtime is processed. When downtime is processed anyone due for election next event is removed from the title (so that the title appers in vacant title lists), so you should not update these pages after downtime but before the event.

These pages need to be updated immediately after an event once all election data is complete.

Update Once

These pages should be updated carefully at the appropriate time.

  • Current Event Imperial Elections (pending) - Elections falling due - update with Elections Event Vacant - update after downtime and before an event starts.
  • Current Event Imperial Elections (results) - Election results - update with Election Event Results - update only once after all election data is complete.
  • Current Event Roll of Honour - update with Roll of Honour - needs to be updated after downtime is processed.

Always Updateable

These pages can be updated at any time.

Unknown/Broken

I'm not sure what state these reports are in, they need work.

  • Paid Work report - should generate lists of who did what in downtime. Seems broken.