Search Tips

FILINGS IN COUNTIES USING THE ODYSSEY CASE MANAGEMENT SYSTEM -Administrative Order 18

Effective Date: 10/30/2009

Obsolete Date: 7/1/2012

To facilitate implementation of Odyssey, the new trial court case management system, this order applies in those counties in which Odyssey is used, until further order of the Supreme Court.

A. Traffic tickets

Electronic images of traffic tickets submitted in a paper form are confidential. On request to the clerk of court, under N.D.Sup.Ct.Admin.R. 41, a copy of a ticket will be redacted as required by N.D.R.Ct. 3.4 and made available for public access.

B. Court filings

In documents prepared for filing with the court, information that would otherwise be included in the document but required by N.D.R.Ct. 3.4 to be redacted in court documents must be separately filed in a reference sheet (confidential information form, see appendix) and may be included in those documents only by reference. Any document not complying with this order is subject to N.D.R.Ct. 3.4(g).

The Supreme Court of the State of North Dakota convened this 30th day of October, 2009, with the Honorable Gerald W. VandeWalle, Chief Justice, and the Honorable Dale V. Sandstrom, the Honorable Mary Muehlen Maring, the Honorable Carol Ronning Kapsner, and the Honorable Daniel J. Crothers, Justices, directing the Clerk of the Supreme Court to enter the above order.

Penny Miller
Clerk
North Dakota Supreme Court
Effective Date Obsolete Date
07/01/2012 View
10/30/2009 07/01/2012 View

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>