In the Gradebook, it is currently possible to create multiple columns with the same name within a single course/class. This is a useful feature, as many schools reuse identical assessment names across different terms.
However, this creates ambiguity when importing marks using the DataStructure-markbookEntry.xlsx template, since there is no way to distinguish between columns that share the same name.
Request:
Add an additional field—such as “Term” (see attachment)—to the import template to help uniquely identify the target column during import.
While duplicate column names within the same term may still present an edge case, this enhancement would address the most common use case where assessments are repeated across terms.
To keep things consistent with other import files that already include a Term column—such as markbookColumns.yml—I suggest that markbookEntryByTerm.yml also use the short name, even though my original screenshot displayed the full name.
