Skip to content

Distinguish between solutions intended to partially address vs fully address a problem #694

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

Open
keyserj opened this issue Apr 24, 2025 · 0 comments
Labels
awkward UX relates to some feeling of awkwardness in the user experience clarity makes something easier to understand criteria table improves the criteria table enhancement New feature or request needs refining More details should be discussed before implementing ontology uses or improves categorizations of info or relations between the categorizations

Comments

@keyserj
Copy link
Collaborator

keyserj commented Apr 24, 2025

Describe your issue

Sometimes it'd be nice if we could be explicit that some solutions are only intended to partially address a problem (i.e. be combined with other solutions probably), as opposed to fully addressing alone.

See discussion in this Discord thread.

Solution you'd like

Lots of possible ideas:

  • ability to mark some solutions as "not mutually exclusive"
  • "partially addresses" or "contributes to addressing" edge

Questions:

  • should the criteria table behave differently for solutions that are partial vs those that are full?

Alternatives you've considered

  • just score the "addresses" edge lower if it's partial. but it seems like there's intent not being communicated in this case, like the "partialness" might be best as something not user-specific

Additional context

No response

Technical ideas and questions

No response

@keyserj keyserj added awkward UX relates to some feeling of awkwardness in the user experience clarity makes something easier to understand criteria table improves the criteria table enhancement New feature or request needs refining More details should be discussed before implementing ontology uses or improves categorizations of info or relations between the categorizations labels Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awkward UX relates to some feeling of awkwardness in the user experience clarity makes something easier to understand criteria table improves the criteria table enhancement New feature or request needs refining More details should be discussed before implementing ontology uses or improves categorizations of info or relations between the categorizations
Projects
Status: No status
Development

No branches or pull requests

1 participant