Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

This is a major release containing a range of new features, significant enhancements to the referencing functionality, a new beta feature to generate citation footnotes in SIs and some bug fixes.

It was released on [20 August 2024].

References to other provisions and documents

Reference tagging (including external references)

The referencing functionality in Lawmaker has been significantly improved and expanded in v.17.

The most significant change is that the Tag References function will now tag external references (i.e. references to other enacted legislation like Acts, SIs or EU legislation) as well as internal references (i.e. references to provisions within the same document).

Other improvements include:

  • The tag references function is much better able to distinguish between internal and external references.

  • References that rely on other reference for their full context (e.g. where there is a reference in the opening words of a provision which qualifies every reference in the child provisions) are now handled correctly in most cases.

  • The tag references function now updates and, where necessary, retags existing references at the same time.

  • The colour of internal links has been updated to make it more accessible and external references have been given a different colour.

To tag external references, Lawmaker uses the data behind http://legislation.gov.uk to lookup and identify the appropriate legislative documents.

In addition, the tag references function now includes support for:

  • References that refer back to a previously mentioned Act or SI etc., e.g. “section 7 of that Act

  • References that are external due to their context but don’t directly include the title of the Act or SI etc., e.g. references in provisions following a statement like “Section 32 of the Criminal Justice Act 2000 is amended as follows.”

  • References that rely on defined names for an Act or SI rather than its proper name, e.g. “Regulation 17 of the 2009 Regulations”, so long as the name is defined in the same document somewhere.

See References and Guide to x-ref changes in version 17 .

Referencing toolbar

The new referencing toolbar (accessible by double clicking on a reference) makes it easy to complete a number of actions directly in the Editor.

You can jump directly to any referenced provision, whether it is internal or external. In the latter case, the referenced provision will open up in http://legislation.gov.uk in a separate tab.

The text of a reference can no longer be directly edited in the Editor but you can use the Edit reference option in the toolbar to update the text and metadata fields if necessary.

You can also trigger an update of the reference, mark it to be ignored or remove the reference mark-up from the toolbar.

See References.

Creating internal references from provisions in the Editor (rather than the structure view)

By right-clicking on a provision in the Editor and selecting Copy reference to provision you can choose a reference to that provision to be copied to the clipboard which can then be pasted elsewhere.

This replicates the functionality that was previously only available from the structure view.

See References.

Generating citation footnotes in SIs

Lawmaker v.17 includes a new beta feature to automatically generate legislative history footnotes for external references in an SI or SSI.

This feature relies on the data from legislation.gov.uk to generate footnotes that contain summarised amendment history of the referenced provision.

See Citation footnotes (legislative history footnote) for more on this.

Church Measures

Lawmaker can now be used to create and manage Church Measures.

Church Measure is a new document type available from the Create New Project dialog box. Broadly speaking the functionality and presentation for Church Measures is the same as for UK Bills. However, there is no ability to create amendments or amendment lists.

See Drafting Church Measures, Managing a Church Measure in Parliament and Creating an Enacted version of a draft Church Measure .

Quoted text

When drafting a textual amendment to another enactment that only involves a word or phrase rather than a whole provision, you can insert a Quoted Text element to represent the text that is being left out, inserted or substituted.

The new “Quoted text” element can be inserted from the Content Completion Assistant by pressing Enter and selecting Quoted text.

Quote marks automatically appear but can be removed or altered if necessary.

See Quoted Text.

Sorting amendments by marshalled order on the Amendment Manager Tab

A new option on the Amendment Manager (via the Sort by marshalled order button) allows you to sort all the visible amendments by the order that they would appear in a marshalled list, including reflecting any Order of Consideration. This feature uses the same logic for generating a marshalled list that is already present in Lawmaker.

The previous “OoC sort” function has been removed.

See Sorting amendments on the Amendment Manager Tab.

Scripted marshalled list improvements

Some limited improvements to the functionality for generating Scripted Marshalled Lists in the Scottish Parliament have been implemented.

These are:

  • new CCA options to add script boxes with or without headings;

  • new CCA options to add script boxes before or after the currently selected amendment;

  • CCA option to add the pre-populated ‘Question on amendment’ box directly from anywhere in the list, without having to create a blank script box first.

Submitting amendments from a LoDA

When amendments are submitted directly from a list of draft amendments, the receiving organisation (e.g. the Commons or Scottish Parliament) will also receive a copy of the list (accessible from the Amendment Workspace tab) so they can see the order in which they appeared on that list and to help them manage the amendment checking and tabling process.

See Submitting amendments.

Uploading amendment list XML to create new amendments

A new option on the Amendment Workspace tab allows you to upload amendment list XML in order to create new Draft amendments against a specific bill version.

Amendment list XML can be downloaded by selecting ‘Download ZIP file’ from the Actions menu next to any amendment list on the Amendment Workspace or Official Lists tabs. The ZIP file contains XML which can then be uploaded to any other bill project to recreate the amendments from that list as new draft amendments.

Editing fragments of a schedule

Schedules in Bills and SIs are now fragmented at the grouping level (e.g. Part, Chapter, cross-heading) as well as at the schedule level.

This means that more than one user can edit provisions in the same schedule at the same time. It also means that the Edit Portion function can be used to open up a portion of a schedule rather than only the whole schedule.

In consequence of this change, the structure view now shows the grouping levels within a schedule by default.

SI improvements and changes

  • Dates in the date block that are left empty now automatically show as three asterisks “***”.

  • If all the paragraphs within a regulation or article are deleted other than one, the remaining paragraph is automatically unwrapped so an undivided regulation or article is left.

  • The banner is now locked in the Editor to prevent accidental changes. It will still update automatically if the procedure is changed.

  • The content of the subject, title and number blocks at the beginning of an SI are now locked in the main Editor window to prevent accidental changes. You can still update the subject by clicking on it and selecting the appropriate subjects in the dialog box. The title and number can still be updated via the Document Information panel on the right.

  • The list of available subjects in the Subjects dialog box has been updated.

  • OFGEM and OFCOM have been added as new Lawmaker organisations.

Bug fixes

SI/SSIs

Issue key

Summary

User support ticket

SPT-1703

Error when copying an SI to another project when SI doesn't have enacting text

SPT-1700

Smart paste of SI prov1 with auto-renumber ON strips trailing full stop from num

SPT-1695

Updated SI subject heading list

SPT-1689

SI Paragraph (1) spacing differs in quoted structure as starting element

SPT-1679

Specific wordings of SI/SSI dates still causes line break

SPT-1676

Procedure of SI on the Project tab or Dashboard is locked in after creation and unchangeable

SPT-1671

Add OFGEM and OFCOM as new organisations

Editor

Issue key

Summary

User support ticket

SPT-1713

Editor fails to revert to using the correct document filter after an unknown action in the editor results in a failure to switch back to the LDAPPDocumentFilter

SPT-1711

Oxygen sometimes fails to retrieve the XML from the server for operations like auto-save, save and structure view updates

SPT-1706

The "A problem has occurred" modal appears in documents with lots of spelling errors.

SPT-1702

Performance issue in getElementByGuid(Oxygen client-side code) (included in patch release 16.2.1)

SPT-1701

TNA - Screen Jumps On Paste

SPT-1699

Poor performance when copying a reasonable number of provisions (included in patch release 16.2.1)

SPT-1683

Mark as done toggle not working in certain cases

SPT-1672

Issues with rejecting "surround" tracked changes in Oxygen v25.1.

SPT-1653

Updates to document during a renumber operation result in strange document modifications

SPT-1656

Promote/Demote of closing words unwraps inline formatting and footnotes

SPT-1631

Incorrect Document Push in Copy Provisions Operation

SPT-1616

Strange restrictions on using the Structure View to move a Schedule in a version of a bill where a New Schedule amendment has been applied

https://lawmaker.atlassian.net/browse/LMS-2739

SPT-1611

Oxygen exceptions occurring when a user accepts tracked change edits ("A problem has occurred") (included in patch release 16.2.1)

https://lawmaker.atlassian.net/browse/LMS-2803

SPT-1609

Cross references inside tracked change deletions are re-added without deleted markup after updating cross references in the provision

https://lawmaker.atlassian.net/browse/LMS-2796

PDFs

Issue key

Summary

User support ticket

SPT-1696

Quoted structure in change track have incorrect indent

SPT-1693

Text in ukpga quoted structure //section/intro is not justified in PDF

SPT-1692

Page numbering broken from page 10 onwards in Scottish Parliamentary Amendment lists

SPT-1691

Empty paragraph element wrongly aligned in PDF

SPT-1682

Long hyperlinks (URLs) that are split across multiple lines have line spacing issues in the PDF and CSS issues in footnotes in the editor

SPT-1558

Resolve PDF rendering issues caused by missing attributes on quotedStructures (ukl:docName and ukl:indent)

Amendments

Issue key

Summary

User support ticket

SPT-1690

Wrong placement of material dragged into containers in amendment QSs

SPT-1651

Auto-apply: amendments which leave out words after a Defined term can't be applied if the quotation marks on the defined term are included in the amendment instruction

https://lawmaker.atlassian.net/browse/LMS-2740

SPT-1646

Extra spaces appear in certain substituting amendments when auto-applied to a bill version

SPT-1633

Auto-applying amendments to rref elements sometimes results in too much text being included in the rref; original rref's href attributes also persist

https://lawmaker.atlassian.net/browse/LMS-668

SPT-1632

Auto-applied amendment which inserts text beginning with punctuation after a <ref> element adds the text inside the <ref> when accepted

https://lawmaker.atlassian.net/browse/LMS-668

SPT-1266

Side-lining on auto-applied insert section amendment goes down too far

https://lawmaker.atlassian.net/browse/LMS-76

SPT-1608

Moving an amendment in a LoDA using the Structure View with tracked changes turned on results in the amendment being duplicated

https://lawmaker.atlassian.net/browse/LMS-2785

SPT-1541

Auto-saved traditional amendments in an inline LoDA cannot be restored into the working version

Document management (Project tab, comparison, permissions etc.)

Issue key

Summary

User support ticket

SPT-1662

Duplicating an 'Auto backup' snapshot results in the wrong XML content being retrieved - later changes are included in the duplicate 

SPT-1218

User who first created document still has read-only access when their permissions are removed

SPT-1677

ALL CAPS text is displayed with additional spacing in the Edit Portion dropdown

SPT-1648

Opening an Edit portion document in parallel with others causes issues

SPT-1645

When logging out with two Editor tabs open (one containing a portion of a version), it's not possible to 'Save all changes' in the 'Unsaved changes' modal

SPT-1665

Comparison output moves opening words into the wrong position on Scottish Bill

SPT-1657

XML comparison functionality doesn't handle processing instructions appropriately

SPT-1627

Incorrect comparison result when an x-ref has been updated within a <mod>

https://lawmaker.atlassian.net/browse/LMS-2836

API and misc

Issue key

Summary

User support ticket

SPT-993

Updated authentication to the API to prevent api accounts being unnecessarily disabled

Known issues

This section of the release note highlights any minor issues identified with the release that will be corrected in a future release:

  • Order of provisions in CCA is incorrect after a quoted text element is inserted: Normally, if your cursor is in a provision such as a subsection, when you press Enter, the item at the top of the list will be the most common sibling provision to the one you are in. So, if you are in a subsection then “Subsection” will be at the top of the list. This means that pressing Enter twice, or pressing ctrl+Enter originally, will insert the common sibling element. However, in version 17, if you have inserted a quoted text element into a provision and you subsequently press Enter when your cursor is not in the quoted text element, then “Quoted text” will appear at the top of the CCA instead leading to incorrect behaviour in relation to pressing Enter twice or pressing ctrl+Enter.

  • No labels