Warning before creating duplicate top containers


Following up on issue ANW-945, the Usability Team supports a warning feature when creating duplicate top containers. In order for Top Containers to be considered duplicates, they would have identical container types and indicators and be attached to the same primary record.


Christine Di Bella
April 29, 2020, 3:25 PM

Thanks for that additional detail. To make this ready for pickup by a developer, it would be helpful to have information on where the warning should appear and what it should say.

Also, a head's up that this will probably need to be a configuration that can be set since some institutions specifically create multiple containers with the same container type and indicator.

Lori Dedeyan
October 20, 2020, 3:56 AM

Following up on this ticket with a mockups for a couple of options:

Wording and location for a hard stop on creating duplicate top containers-

Activating the hard stop could be a checkbox option in the Repository settings- mocked up below:

Alternatively, it could be a warning that the user could click through if they wanted to proceed- see below:

Lori Dedeyan
November 2, 2020, 3:42 PM

Hi , I’ve included some mockups for what this function might look like. Usability is recommending the second option- a warning that appears when the “Create and Link to Top Container” is clicked. If the user wants to proceed, they can continue. This was modeled on the old warning for creating records without a Language property.

The warning would appear when a Top Container with duplicate Container Type and Indicator information is created within the same primary record. Please let me know if there is anything other info I can add. Thanks!

Randy Kuehn
December 8, 2020, 3:39 PM

Recommend plugin development for community developer - Dev Pri




Lori Dedeyan