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

Improve user tagging usability #2722

Closed
alondhe opened this issue Jul 27, 2022 · 1 comment · Fixed by #2731
Closed

Improve user tagging usability #2722

alondhe opened this issue Jul 27, 2022 · 1 comment · Fixed by #2731
Assignees
Milestone

Comments

@alondhe
Copy link
Contributor

alondhe commented Jul 27, 2022

Expected behavior

A user can tag their assets (concept sets, cohorts, characterizations, IRs, pathways, etc) in batch.

Current behavior

Our initial tagging release does not have this capability. Instead, a user needs to go to each study asset they own / have write access to and tag individually. This is cumbersome, as often a study requires many assets.

Steps to development

We have begun development of this new enhancement for 2.12:

image
image

@anthonysena
Copy link
Collaborator

anthonysena commented Jul 27, 2022

Some initial thoughts here:

  • When this is implemented, the "Tagging" item on the left-hand menu item should be hidden by default and optionally enabled for those that want to use the feature.

  • image

  • The screenshot above is a bit confusing to me as I believe the (x) in the screenshot above refers to the tag ID and I'd actually interpret this as the # of entities with the tag. Perhaps it could be formatted as "Tag Name (ID = X)" to make it clear? Or use a hover over to show the ID when required?

anton-abushkevich added a commit that referenced this issue Sep 20, 2022
Improve user tagging usability #2722
anton-abushkevich added a commit to OHDSI/WebAPI that referenced this issue Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants