Interim updates are executed in early July of the even-numbered year and include all changes since prior codification up to that point and changes identified that will occur after that period through the beginning of the session in January of the odd-numbered year. New updates to the MCA database done during the interim include:
-
Changes due to effective dates or terminations dates
-
Changes caused by the occurrence of contingencies (e.g., oil prices hit level specified in law)
-
Miscellaneous nonsubstantive updates and corrections
Changes are proactively tracked throughout the session and leading up to the beginning of the Interim Code Update processing. These are tracked in a notebook compiled by the Editors. Others may be requested by appropriate agencies when contingency thresholds or points have been reached. Changes are tracked in a batch covering 2-year cycle.
Special codes (italics) have been inserted into MCA master to identify contingencies and effective dates. These codes appear within the section after the section number and before the catchline (title) and may be removed during Interim Code Update processing. If existing law is subject to changes after the current interim cycle period, these codes will remain in the data for later processing.
Sometimes in even-numbered years an event occurs and a compiler’s comment is written in the MCA to be published one time in the next odd-numbered year publication of the MCA. That note is coded so that it is moved to Annotations (see Annotations Process) and removed from MCA.
All changes effected in an odd-numbered year are reflected in the Code Update after the regular session. All changes in effect in even-numbered years are reflected in the even-numbered year Interim Code Update. Exceptions to this rule include:
-
Supreme Court Rules updates (as needed)
-
Database changes
-
Unpredicted changes
Note: The Code Commissioner publishes the Supreme Court Rules as a courtesy to the Supreme Court. Some rules appear in Titles 25 and 26 of the MCA as section text documents and some rules appear only in Annotations various titles.
Note: If an election occurs and referendums or initiatives were voted on and approved in the election, another Interim Code Update is performed immediately following the election and prior to the next session. The CD-ROM is not updated at this time and will not reflect election updates until produced in the next regularly scheduled production.
Note: Special sessions require a separate Interim Code Update (see Session Law Process and Code Update Process).
Process Notes:
-
Sheet listing affected sections of MCA is used to create copies of those sections for updating (it takes about 1 week to copy all affected sections to working area). Includes known effective date changes for the entire year (period since last regular code update was completed through beginning of next session as noted above). Also includes contingency changes that have occurred and were requested. Also includes database changes collected to this point.
Note: Goal is to preserve MCA database and make only nonsubstantive corrections to it directly, while enabling more significant and substantive changes to be made to working copy during Interim Code Update. Change access to MCA is limited to very few people.
Note: Interim Code Updates may affect interim bill drafting (see Interim Bill Drafting Process). All interim drafts are redrafted after the interim update is complete.
-
Changes are made to MCA sections by Editors.
-
Supreme Court Rule changes are reviewed by Editors and are entered by Document Processor after this review then checked by Proofreaders.
-
Compiler’s comments from the previous session are removed from the MCA after they have been extracted for Annotations processing (see Annotations Process).
The Annotations Volumes created from a compilation of many items that are related or affect statutes. This includes:
-
Case notes
-
Attorney General opinions
-
Compiler’s comments
-
Official comments
-
Law review articles
-
Cross-references
-
Collateral references
-
Cites to ARM
Annotations are prepared and kept current throughout the year and are published (in book form) in 3 batches (March, May, and August of even-numbered years) to provide current information to users of the MCA. History (when enacted and when amended), permanent or most recent compiler’s comments, and cross references appear in the MCA at the end of each section. The compiler’s comments and the entire numbered list above except the cross-references and histories are included in the stand-alone Annotations volumes.
6.Database Preparation -
Annotations Merge Processor runs an ALF process to copy all non-permanent MCA compilers’ comments from the MCA database to the Annotations database.
-
P tag – permanent (tagged as a permanent comment – open and close ‘P’ tag)
-
O tag – includes year to designate the time frame that tag applies to. Special Session ‘O tags’ are given the year of the special session which can be anytime between sessions.
-
Annotations Merge Processor runs an ALF to replace documents in the Annotations database with the corresponding document from the MCA database for these document types:
-
Chapter name
-
Part name
-
Catchline
-
Annotations Merge Processor runs an ALF to move all documents in renumbered sections to their new locations.
-
Editor prepares a list of repealed, renumbered, and terminated sections and name changes. Editor then does a Folio search using those sections so any reference in a case note, Attorney General’s opinion, or official comment to a section is updated with information saying the section has been repealed (or any other action).
Share with your friends: |