Allow Duplicate Markbook Column Names During Import

Feature Requests
1

Hi @sandra @Ali

I use the same column names across terms. It is possible to manually add a new column with an existing name. However, I cannot do this when importing columns, which is the primary way I create/add columns.

Each time, I have to edit resources/imports/markbookColumns.yml and change:

uniqueKeys:
    - [ gibbonCourseClassID, name ]

to:

uniqueKeys:
    - [ ]

in order to allow duplicate column names.

Could there be a way for the user to specify during import whether the intention is:

  • column names are unique for the school year, or

  • column names are not unique for the school year?

In other words, during import, are we updating an existing column or inserting a new one? Currently, when the name is the same, the import behaves as an update rather than allowing insertion of another column with the same name.

An added plus would be the ability to define uniqueness based on either:

  • the school year, or

  • the term.

Thanks