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

Tag definitions #18

Open
Azorlogh opened this issue Feb 5, 2023 · 0 comments
Open

Tag definitions #18

Azorlogh opened this issue Feb 5, 2023 · 0 comments
Labels
D:difficult needs design There is no obvious solution P:high Lack of this feature severely impacts usability

Comments

@Azorlogh
Copy link
Owner

Azorlogh commented Feb 5, 2023

Tags need to exist as independent objects in the app in order to carry some metadata:

For example, tags might have different sensible ranges & default values:

  • "valence" make more sense having the default value at the middle value (eg: [0, 1] with default 0.5)
  • genre tags make more sense having the default value at the minimum value (eg: [0,1] with default 0)

Therefore, tags probably need to carry information besides their name.
Possible useful information:

  • Default value
  • Range ("valence" could be [-1, 1] with default 0)
  • Type: String tags might be useful?
@Azorlogh Azorlogh added D:difficult P:high Lack of this feature severely impacts usability needs design There is no obvious solution labels Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D:difficult needs design There is no obvious solution P:high Lack of this feature severely impacts usability
Projects
None yet
Development

No branches or pull requests

1 participant