Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Improvements to the “on the fly” option for adding new taxonomy terms #1804

Open
csbarrett opened this issue Apr 29, 2024 · 2 comments
Labels
Type: enhancement An improvement to existing functionality.

Comments

@csbarrett
Copy link

Current Behaviour

AtoM provides multiple ways to add new terms: Users can use add a term via the Manage Taxonomy screen or they can create place and subject terms “on the fly” from the archival description edit page. Users can also add new terms via the relevant taxonomy page (e.g., subject, place, genre).

When users search the auto-complete drop-down menus in the archival description edit page, they sometimes add new terms through the “on the fly” approach when they are actually trying to find an existing term.

Desired Behaviour

No duplicate, incomplete, or erroneous terms should be added to taxonomies through the “on the fly” approach.

Possible solutions

  1. Provide administrators with a setting to toggle on or off the “on the fly” method for all users (preferred).
  2. Allow administrators to grant permissions for create new terms via the Manage Taxonomy screen but not using the “on the fly” method.
  3. Provide users with a prompt to indicate a that they are about to add a new term “on the fly” and give them an option to proceed or cancel.

Context and Notes

The autocomplete drop-down interface is touchy and makes it too easy to inadvertently enter incomplete or duplicate terms. In practice, what happens is that users inadvertently add new terms when they are searching the autocomplete drop-down for a relevant access point. There is no prompt or "create" button or anything else to indicate that they have actually created a new term rather than linked to an existing term.

Version

AtoM 2.7.3

@fiver-watson
Copy link
Contributor

Hi @csbarrett !

It's up to the Maintainers to handle these types of requests now, not me, but I wanted to share one more possible solution I had kicking around to the underlying problem - one that I personally think would combine well with your solution 1 as an additional protection when adding terms on the fly IS enabled:

I can no longer find the related old Redmine wishlist ticket, but here's a mockup (from 2014!) I found kicking around in my AtoM stuff:

Auto-complete-fields

With this approach, autocomplete fields would default to only linking to existing entries.

By adding a simple toggle, users would have to manually choose to change the radio button to "Add new" before they could create a new term on the fly. Otherwise, the field will only accept existing matched entries. This seems like a small addition to the end user workflow that in turn prevents many problems - a fair tradeoff, in my opinion, and one that could work on any autocomplete field that allows new entries on the fly (as you can see here, the example mockup was for an archival institution field).

If your Option 1 above (adding a global admin setting to enable or disable the addition of on-the-fly terms) was added, then when set to deny the addition of on-the-fly terms, these radio buttons could simply be hidden from input fields.

Just a thought!

@csbarrett
Copy link
Author

Hi, @fiver-watson! That is a great suggestion, thanks for sharing.

mcantelon added a commit that referenced this issue May 2, 2024
Added functionality, to the digital object load task, to import URLs in
addition to files.

Did minor cleanup and improved CLI help to include a list of valid CSV
columns.
mcantelon added a commit that referenced this issue May 2, 2024
Added functionality, to the digital object load task, to import URLs in
addition to files.

Did minor cleanup and improved CLI help to include a list of valid CSV
columns.
@anvit anvit added the Type: enhancement An improvement to existing functionality. label May 3, 2024
@anvit anvit modified the milestone: 2.8.2 May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: enhancement An improvement to existing functionality.
Projects
None yet
Development

No branches or pull requests

3 participants