> For the complete documentation index, see [llms.txt](https://help.simnetonline.com/manager/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.simnetonline.com/manager/getting-started/best-practices/naming-conventions.md). # Naming Conventions After a few semesters of using SIMnet, the amount of content and courses can build up. To find and use your materials efficiently; get accurate and timely support; and avoid that colleague who puts an asterisk in front of everything it is important to name your content with specific, repeated naming conventions. ![The Beginning of an Arms Race](/files/-MKa2aw4EEqXsbCm_08_) The important thing is to select a convention and enforce it throughout SIMnet. ## Courses and Sections Course names in SIMnet should include the name of the course as it appears elsewhere at your school. For example, many schools use SIMnet as a part of their Computer Science intro course. Their course name at the registrar's office and in Canvas is **CS 101**. The SIMnet course name should match. Section names in SIMnet should describe which section of the course it is, when the course is taking place, who is teaching it, or when the course is meeting. If there are 4 sections in the Spring of 2021 taught by different instructors meeting on different days. Those section names may be * Section 1 Spring 2020 Smith TTr 12:15-1:10 * Section 2 Spring 2020 Smith WF 3:15-4:10 * Section 3 Spring 2020 Ndebe MW 9:15-10:10 * Section 4 Spring 2020 Ndebe F 5:45-7:35 Each semester there is at least one instructor who has a course archived or deleted and cannot tell SIMnet Support what their course is called, which makes recovering their course more difficult and slower than it would otherwise be. {% hint style="success" %} **Success**: Create a class 'template' and name the section to include 'template' or 'main' to indiicate the the class should only be copied. Remeber to close your template class so students can't enroll into it! {% endhint %} ## SIMnet Content SIMnet content is typically used across many courses and will be more context-dependent than course names are. Content may be used by all of the courses at a URL, all the sections of a single course, or for a single instructor. SIMnet course content should mention the course name and the content covered in the assignment. It should also mention the version of the Office materials covered in the content. For example, simply naming the first quiz for an Access course Access Quiz 1 is hard to use when a school switches from 2016 to 365/2019 content. So the first quiz covering Access would be **CS 101 365 Access Quiz 1**. ## Master Classes Creating a master course can allow you to copy a course without any of the modifications that individual instructors make to the course. This course should be clearly labelled as a Master course and should not have any students added or any associated grades. Adding students and allowing them to complete coursework in the master class limits the long term flexibility of your master course. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.simnetonline.com/manager/getting-started/best-practices/naming-conventions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.