Course Materials: Term name uniqueness too strict

[Michele Morgan]

Different libraries in a consortium may need course terms with different starting and ending dates, and may choose to use the same name for their course term as another library.

There is a uniqueness constraint on asset.course_module_term on 'name' which prohibits this. It would make more sense in a consortium for the uniqueness constraint to be on 'owning_lib' as well as 'name'.

[MaryAnn Alexander (maryann-alexander)]

A patch is available at the tip of

working/user/malexander/lp1942645-term-name-uniqueness / https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/malexander/lp1942645-term-name-uniqueness

[Martha Driscoll (mjdriscoll)]

The syntax of the database upgrade script is not quite right. The DROP and ADD need to be part of the ALTER TABLE statement. I modified the script to this:

ALTER TABLE asset.course_module_term
        DROP CONSTRAINT course_module_term_name_key;

ALTER TABLE asset.course_module_term
        ADD CONSTRAINT cmt_once_per_owning_lib UNIQUE (owning_lib, name);

The script ran and successfully dropped the constraint and added the new one. We will now test the functionality of the new constraint.

[Beth Willis (willis-a)]

I have tested this code and it works as expected. I consent to signing off on it with my name,
Beth Willis and my email address, <email address hidden>

[Jane Sandberg (sandbergja)]

Thanks, Beth. To be clear, are you signing off on the code as modified by Martha?

[Beth Willis (willis-a)]

Jane, yes! Sorry, I should have been more explicit. I am signing off on the code with the modifications provided by Martha Driscoll.

[Jane Sandberg (sandbergja)]

Thanks so much, MaryAnn, Martha, and Beth. With Martha's corrections, it works well for me; I am now able to create terms at different libraries that have the same name. I've pushed that version to master, rel_3_8, and rel_3_7.