m |
m |
||
Line 31: | Line 31: | ||
==Options for referencing a manual version== | ==Options for referencing a manual version== | ||
− | There are options for referencing a version of the Minnesota Stormwater Manual. For example, an ordinance might state "design | + | There are options for referencing a version of the Minnesota Stormwater Manual. For example, an ordinance might state "design specifications must conform to the Minnesota Stormwater Manual". Example language for this scenario is included in the option discussions below. |
− | *Option 1 | + | *Option 1: Reference the most recent version of the manual. Example language would be "design specifications must conform to the current version of the Minnesota Stormwater Manual". An advantage of this option is that the most current information will be used. A disadvantage is that manual updates occur often and may occur for a single project during the life of that project. |
+ | *Option 2: Reference the manual version that existed at the start of a project. Example language would be "design specifications must conform to the version of the Minnesota Stormwater Manual at the start of the project". This language would not result in changes during the life of a project. A disadvantage is that project leads and developers will have to determine if changes occurred since their last project. | ||
+ | *Option 3: reference the manual at a specific point in time. Example language would be "design specifications must conform to the January 1, 2017 version of the Minnesota Stormwater Manual". This prevents shifting requirements over time and does not require the project lead or developer to determine if recent versions of the manual exist. A disadvantage is that the project lead or developer must find the appropriate version of the manual using the methods described above. Also, the concern with outdated information becomes an issue over time. | ||
+ | |||
+ | ==Citing the Minnesota Stormwater Manual== | ||
+ | As a point of clarification, citing the manual, such as in a document, differs from the discussion above in which a version of the manual or manual page is being referenced. |
The wiki format for the Minnesota Stormwater Manual allows for continual updates. While this has the advantage of keeping the information in the manual aligned with the most recent technologies, it creates challenges for developers who comply with specifications in the manual. Specifications may change from one project to the next. Local regulations, such as ordinances, may refer to the manual, which creates either a challenge of keeping on top of changes in the manual or having to refer to a specific version of the manual.
The MPCA strongly recommends that older guidance, such as the 2005 or 2008 Minnesota Stormwater Manual (Version 2.X or earlier) and the Stormwater Best Management Practices Manual (Protecting water quality in urban areas), not be used in stormwater development projects or be incorporated into local regulations and ordinances. Significant advances in BMP design, construction, maintenance, and performance require using recent information. This page describes some options for addressing the problem of using and referencing the Minnesota Stormwater Manual.
At the bottom of each page is a statement identifying the date and time of the most recent update to the page. Another option is to click on Page information in the left toolbar. This opens a page listing the date of latest edit, as well as other information about the page.
The wiki retains copies of all edited pages. It can be challenging to find the specific page and date of interest. Follow this procedure to identify updates of interest.
The image gallery below illustrates this process for the manual page called Design criteria for bioretention.
Using the manual page called Design criteria for bioretention as an example, assume we are looking at the January 19, 2017 version of this page. The image to the left shows a screen shot of the resulting page. You can select from different versions immediately before or after the selected version. To see the difference between two versions, click on the diff link. A screen shot in the image to the right shows that two versions are laid next to each other to allow comparisons of text that has been added (orange shading) or deleted (blue shading). You can view the source coding by clicking on view source. Note that each version also includes information on the date and time the revision was created and the name of the person who made the revisions. A link to all stormwater manual revisions is included (shown as contribs, which was discussed in the previous section).
There are options for referencing a version of the Minnesota Stormwater Manual. For example, an ordinance might state "design specifications must conform to the Minnesota Stormwater Manual". Example language for this scenario is included in the option discussions below.
As a point of clarification, citing the manual, such as in a document, differs from the discussion above in which a version of the manual or manual page is being referenced.