Difference between revisions of "Corrections"
| Line 32: | Line 32: | ||
[[File: Corrections_2.png]] | [[File: Corrections_2.png]] | ||
| − | + | fter correcting the TOES data, we need to reset update (in fact it’s easier to correct TOES if we reset the Act first) and (as is the case here) we may also need to actually delete the existing update tasks (e.g. “Update to 28/3/2007”) and allocate them over again from scratch because they have the wrong date in them. Also, the timeline may need to be regenerated before reallocation of update is allowed. | |
==Notes about Corrections== | ==Notes about Corrections== | ||
Revision as of 15:48, 26 April 2021
Page being edited
Amendment coming into force before the provision it is amending comes into force
This scenario results in “later sld version errors” which prevent you from starting update. It is caused because at least one amendment has a start date earlier than one of the provisions in the affected document, so there are several different ways of getting round this depending on the exact situation:
- if the amended doc is being revoked before it comes into force, then you will have to reset update and re-do sld initial edit to make it prosp and redeploy and then do the update to revoke it;
- if an amendment comes into force before the affected provision comes into force, there are two options:
- do a TOES correction to change the IFDate of the effect to make it the same as the start date of the affected provision, ensuring that you also provide a “Suggested Commentary” for the effect that contains its REAL start date. (A suggested commentary should be written properly in our house style, including punctuation, legislation title and commencement order details). Then do update.
- if the amendments have start dates between the earliest date that the affected doc comes into force and one or more subsequent commencements, then you should reset update, re-do sld initial edit to make the subsequently commenced provisions prosp; then you should do a TOES correction to add coming into force effects for those now prosp provisions. Then when you re-allocate update the coming into force effects will be added as I-notes as part of the update task and will appear in the update timeline.
Example: "Later Legislation version"
Error message on starting update:
"Later legislation version dated '2007-05-01' found. Your request to update PiT dated '2007-03-28' cannot be completed. There is a later version of this legislation and this is not currently supported for updates other than commencements"
The "Later legislation version" error message occurs here because the IF Date of the effects (28.3.2007) is earlier than the start date of the affected legislation (1.5.2007).
https://www.legislation.gov.uk/ssi/2006/534/regulation/1/made
https://www.legislation.gov.uk/ssi/2007/166/regulation/1/made
We can work around by changing the TOES data so that the IF Dates for the effects coincide with the start date (1.5.2007) of the affected provisions, but we also need to add a Suggested Commentary using our house style so that the annotation contains the actual date (28.3.2007) that the amendments come into force:
fter correcting the TOES data, we need to reset update (in fact it’s easier to correct TOES if we reset the Act first) and (as is the case here) we may also need to actually delete the existing update tasks (e.g. “Update to 28/3/2007”) and allocate them over again from scratch because they have the wrong date in them. Also, the timeline may need to be regenerated before reallocation of update is allowed.
Notes about Corrections
TOES
- Be careful when doing TOES corrections not to delete and re-insert entries i.e. you should amend the existing entries as doing so will preserve the KeyIDs for the existing entries (which should not be removed).