Press n or j to go to the next uncovered block, b, p or k for the previous block.
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 | 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x 1x | import React from "react";
import { Accordion } from "react-bootstrap";
import BasicLayout from "main/layouts/BasicLayout/BasicLayout";
import csvFixtures from "fixtures/csvFixtures";
export default function HelpCsvPage() {
return (
<BasicLayout>
<div className="pt-2">
<h1 className="my-4">CSV Upload/Download Formats</h1>
<h2>Roster Student CSV Upload formats</h2>
<p>
Instructors can upload a course roster from a CSV file. The following
formats are supported. If you would like your university's format
to be supported, please contact the Frontiers development team,
supplying a sample CSV (with fictional data).
</p>
<Accordion data-testid="rosterUploadsAccordion">
<Accordion.Item eventKey="0">
<Accordion.Header>UC Santa Barbara</Accordion.Header>
<Accordion.Body>
<p>
The following CSV format can be obtained from the EGradessystem
at UC Santa Barbara:
</p>
<pre className={"csvExample"} data-testid="ucsbEgradesCsvExample">
{csvFixtures.ucsbEgrades}
</pre>
<p>We map the fields as follows:</p>
<table className="table table-striped">
<thead>
<tr>
<th>Roster Field</th>
<th>CSV Field</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Student Last</td>
<td>Student Last Name</td>
<td></td>
</tr>
<tr>
<td>Student First</td>
<td>Student First Name</td>
<td></td>
</tr>
<tr>
<td>Perm #</td>
<td>Student ID</td>
<td></td>
</tr>
<tr>
<td>Email</td>
<td>Email</td>
<td>
We translate all <code> @umail.ucsb.edu </code> addresses
to <code> @ucsb.edu</code>
</td>
</tr>
<tr>
<td>Section</td>
<td>Enrl Cd</td>
<td>We keep the enrollment code for the Section column.</td>
</tr>
</tbody>
</table>
<p className="text-muted">
All other columns exported by eGrades (Grade, Units, Quarter,
etc.) are ignored.
</p>
</Accordion.Body>
</Accordion.Item>
<Accordion.Item eventKey="1">
<Accordion.Header>Chico State University</Accordion.Header>
<Accordion.Body>
<p>
The following CSV format can be obtained from the Canvas system
at Chico State, through the "New Analytics" feature:
</p>
<pre className={"csvExample"} data-testid="chicoStateCsvExample">
{csvFixtures.chicoStateCanvas}
</pre>
<table className="table table-striped">
<thead>
<tr>
<th>Roster Field</th>
<th>CSV Field</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Student Last</td>
<td>Student Name</td>
<td>
We split the value at the last space; double-check
suffixes such as Jr. or III to ensure they end up on the
correct side.
</td>
</tr>
<tr>
<td>Student First</td>
<td>Student Name</td>
<td>
Everything before the final space (blank if no space is
present).
</td>
</tr>
<tr>
<td>Student ID</td>
<td>Student SIS ID</td>
<td>The “Student ID” column from Canvas is ignored.</td>
</tr>
<tr>
<td>Email</td>
<td>Email</td>
<td></td>
</tr>
<tr>
<td>Section</td>
<td>—</td>
<td>
Canvas includes a Section Name column, but Frontiers
ignores it and leaves the Section field blank for this
format.
</td>
</tr>
</tbody>
</table>
<p className="text-muted">
All other columns from the Canvas “New Analytics” export are
ignored, so you can upload the file as-is; this includes Section
Name, so roster sections remain blank after the upload.
</p>
</Accordion.Body>
</Accordion.Item>
<Accordion.Item eventKey="2">
<Accordion.Header>Oregon State University</Accordion.Header>
<Accordion.Body>
<p>
The following CSV format can be obtained for courses at Oregon
State University.
</p>
<pre className={"csvExample"} data-testid="oregonStateCsvExample">
{csvFixtures.oregonStateCSV}
</pre>
<table className="table table-striped">
<thead>
<tr>
<th>Roster Field</th>
<th>CSV Field</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Student Last</td>
<td>Sortable name</td>
<td>Everything before the comma.</td>
</tr>
<tr>
<td>Student First</td>
<td>Sortable name</td>
<td>Everything after the comma (or blank if none).</td>
</tr>
<tr>
<td>Student ID</td>
<td>SIS Id</td>
<td></td>
</tr>
<tr>
<td>Email</td>
<td>Email</td>
<td></td>
</tr>
</tbody>
</table>
<p className="text-muted">
Other analytics columns (grades, participation timestamps, etc.)
are ignored when the CSV is processed, so the Section column in
Frontiers remains blank for this format.
</p>
</Accordion.Body>
</Accordion.Item>
</Accordion>
<h3 className="mt-4">How Frontiers handles dropped students</h3>
<p>
Each time you upload a roster CSV, Frontiers temporarily marks every
roster student that originally came from a CSV (status{" "}
<code>ROSTER</code>) as <code>DROPPED</code>. As rows from your new
file are processed, matching students are switched back to{" "}
<code>ROSTER</code> (or inserted if they were new).
</p>
<ul>
<li>
Only students that appeared in a prior CSV upload can move into the
dropped section automatically.
</li>
<li>
Students that you added manually keep their <code>MANUAL</code>{" "}
status and are never moved to DROPPED by an upload.
</li>
<li>
After the upload finishes, anyone still marked <code>DROPPED</code>{" "}
is listed in the Dropped tab, and Frontiers queues them for removal
from the linked GitHub organization.
</li>
</ul>
<p>
If a student disappears from your roster because their identifier
changed, update the CSV before uploading so that they are not treated
as dropped.
</p>
<h2 className="mt-4">Team Information</h2>
<p>
Teams can be managed using a simple CSV upload with the following
format.
</p>
<Accordion data-testid="teamsAccordion">
<Accordion.Item eventKey="0">
<Accordion.Header>Teams (by Email)</Accordion.Header>
<Accordion.Body>
<p>
You can upload teams using a simple CSV with the following
format:
</p>
<pre className={"csvExample"} data-testid="teamsCsvExample">
{csvFixtures.teamsByEmail}
</pre>
<p>We interpret the fields as follows:</p>
<table className="table table-striped">
<thead>
<tr>
<th>Roster Field</th>
<th>CSV Field</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>Team Name</td>
<td>team</td>
<td>
Rows with the same team value belong to the same team.
</td>
</tr>
<tr>
<td>Email</td>
<td>email</td>
<td>
Student's email address used to match to the roster.
</td>
</tr>
</tbody>
</table>
</Accordion.Body>
</Accordion.Item>
</Accordion>
<h2 className="mt-4">Roster Student CSV Download formats</h2>
<p>
Instructors can download a course roster as a CSV file. The download
will include all roster students with their current status
information.
</p>
<Accordion>
<Accordion.Item eventKey="0">
<Accordion.Header>Frontiers CSV Download Format</Accordion.Header>
<Accordion.Body>
<p>
When you download a roster as CSV, you will get the following
format:
</p>
<p>
The header row uses uppercase names and the columns appear in
the exact order shown below.
</p>
<pre
className={"csvExample"}
data-testid="rosterDownloadCsvExample"
>
{csvFixtures.rosterDownload}
</pre>
<p>The fields are described as follows:</p>
<table className="table table-striped">
<thead>
<tr>
<th>CSV Field</th>
<th>Description</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<code>ID</code>
</td>
<td>Internal database ID</td>
<td>Unique identifier for each roster entry</td>
</tr>
<tr>
<td>
<code>COURSEID</code>
</td>
<td>Course database ID</td>
<td>Identifies which course this student is enrolled in</td>
</tr>
<tr>
<td>
<code>STUDENTID</code>
</td>
<td>Student ID</td>
<td>Student's university ID (e.g., Perm # at UCSB)</td>
</tr>
<tr>
<td>
<code>FIRSTNAME</code>
</td>
<td>Student's first name</td>
<td>Required when re-uploading this CSV.</td>
</tr>
<tr>
<td>
<code>LASTNAME</code>
</td>
<td>Student's last name</td>
<td>Required when re-uploading this CSV.</td>
</tr>
<tr>
<td>
<code>EMAIL</code>
</td>
<td>Student's email address</td>
<td>Required when re-uploading this CSV.</td>
</tr>
<tr>
<td>
<code>USERID</code>
</td>
<td>Internal user ID</td>
<td>Links to the user account in the system</td>
</tr>
<tr>
<td>
<code>GITHUBID</code>
</td>
<td>GitHub user ID</td>
<td>Student's GitHub account ID, if connected</td>
</tr>
<tr>
<td>
<code>GITHUBLOGIN</code>
</td>
<td>GitHub username</td>
<td>Student's GitHub username, if connected</td>
</tr>
<tr>
<td>
<code>ROSTERSTATUS</code>
</td>
<td>Roster enrollment status</td>
<td>
ROSTER (from uploaded roster), MANUAL (manually added), or
DROPPED
</td>
</tr>
<tr>
<td>
<code>ORGSTATUS</code>
</td>
<td>GitHub organization status</td>
<td>PENDING, JOINCOURSE, INVITED, MEMBER, or OWNER</td>
</tr>
<tr>
<td>
<code>TEAMS</code>
</td>
<td>Team names</td>
<td>
A comma-separated list showing every team assigned to the
student.
</td>
</tr>
</tbody>
</table>
<p>
When you re-upload a file that originated from this download,
Frontiers only reads the following columns; everything else is
ignored, so you can upload the file without trimming it.
</p>
<ul>
<li>
<code>EMAIL</code>
</li>
<li>
<code>FIRSTNAME</code>
</li>
<li>
<code>LASTNAME</code>
</li>
<li>
<code>STUDENTID</code>
</li>
<li>
<code>SECTION</code>
</li>
</ul>
</Accordion.Body>
</Accordion.Item>
</Accordion>
</div>
</BasicLayout>
);
}
|