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

Implement minimum cell size for matching subjects/dataset #267

Open
1 task done
alyssadai opened this issue Jan 25, 2024 · 1 comment
Open
1 task done

Implement minimum cell size for matching subjects/dataset #267

alyssadai opened this issue Jan 25, 2024 · 1 comment
Labels
feat:add The first minimal viable change that implements a new functionality. feedback:feature request Request for a new functionality or for an enhancement. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:feature Effort to deliver new features, feature changes & improvements

Comments

@alyssadai
Copy link
Contributor

alyssadai commented Jan 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues

New feature

Each node API should have as part of its configuration a minimum cell size (with a sensible default), representing the # matching subjects in a dataset below which the dataset as a whole will not be shown in the query results.

Unclear documentation

No response

@alyssadai alyssadai added feedback:feature request Request for a new functionality or for an enhancement. feat:add The first minimal viable change that implements a new functionality. type:feature Effort to deliver new features, feature changes & improvements flag:schedule Flag issue that should go on the roadmap or backlog. labels Jan 25, 2024
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 26, 2024
Copy link

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat:add The first minimal viable change that implements a new functionality. feedback:feature request Request for a new functionality or for an enhancement. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:feature Effort to deliver new features, feature changes & improvements
Projects
Status: No status
Development

No branches or pull requests

2 participants