Search Tips

Court chooses law clerks for 2024-2025 term Tuesday, September 26, 2023

The North Dakota Supreme Court is pleased to announce the following individuals who have been selected to serve a one-year clerkship with the North Dakota Supreme Court for the 2024-2025 term beginning August 1, 2024.

Jack Blotsky of Fargo, North Dakota, received a B.S. in Criminal Justice with a minor in Political Science from the North Dakota State University. Mr. Blotsky is expected to receive his J.D. from the University of North Dakota School of Law in May 2024.

Gabrielle Frawley of Farmingdale, New York, received a B.A. Honors Degree in Germanic Studies from Boston College; and a M.A. and Ph.D. in Germanic Languages and Literatures from the University of Kansas. Ms. Frawley is expected to receive her J.D. from the Washburn University School of Law in December 2023.

Danielle Middleton of St. George, Utah, received a B.S. in Interdisciplinary Studies and English from Utah Tech University. Ms. Middleton is expected to receive her J.D. from the University of North Dakota School of Law in May 2024.

Taylor Schmidt of Fargo, North Dakota, received a B.S. in Political Science and minors in Honors, Pre-Law and Writing from North Dakota State University. Ms. Schmidt is expected to receive her J.D. from the Creighton School of Law in May 2024.

McKenna Weisenburger of Wilton, North Dakota, received a B.S. in Criminal Justice and a minor in Emergency Management from the North Dakota State University. Ms. Weisenburger is expected to receive her J.D. from the University of North Dakota School of Law in May 2024.

 

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>