New subject term types should not auto-populate


When adding a new subject Term, the type auto-populating with ‘Culture’.

This causes a lot of mistaken Culture terms, whereas an empty option would force users to make an intentional selection.




Nancy Kennedy
January 17, 2020, 1:58 PM

In the sandbox, a New subject term has the type dropdown pre-selected to “Cultural context”. Ideally, the Type would be still be required, but the Type value would be blank/null at first – not pre-filled to “Culture”.



(in, it’s the same basic story, except that “Function” is first in the list rather than Culture. It’s possible to change which type will appear by default (by changing the order of the list), but it’s not possible to have the type initially appear blank (thereby requiring an intentional selection).


Lydia Tang
January 17, 2020, 2:10 PM

Oh! Thanks for responding! Yes, I see what you mean. Yes, it sounds like it should default to blank, just like the Source field above it. Would it be helpful to also be able for users or repository managers to set the type as a Default value, in case there’s a predominant type?


Nancy Kennedy
January 17, 2020, 2:26 PM

It looks that admins can do that in the usual way, via Systems > Manage Controlled Vocab Lists.

But that should really be a repository level decision: in my experience, even when there’s a very common or dominant type, it’s often a bad idea to let that be an actual, system level default because the exceptions are that much easier to miss. People go on auto-pilot – I do too! And then, down the road, it’s so hard to retroactively address accidental defaults.

Rachel Searcy
October 16, 2020, 7:25 PM

When creating a new subject term in the staff interface of the ArchivesSpace test environment, the type field does not auto-populate.

Elizabeth Roke
October 20, 2020, 1:11 PM

When creating a new subject term, the type field does not auto-populate. However, I noticed that I am now not able to set a default for Subject as the admin/admin login in . I am able to suppress subject terms and it looks like I can still set a default with the button (a gear icon shows when I click on it), but nothing happens. I can set defaults in other controlled vocabularies. Perhaps the default button on subject term should be removed or greyed out?





Nancy Kennedy

Fix versions

Affects versions