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

Provide way for user to indicate agreement to a data usage agreement #268

Open
1 task done
alyssadai opened this issue Jan 25, 2024 · 3 comments
Open
1 task done
Labels
flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. someday Not a priority right now, but we want to keep this around to think or discuss more.

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

  • This should be either node or dataset specific
  • Should ideally work in both curl requests (i.e., the query tool or a direct API user can handle the agreement info) and in the interactive docs

Unclear documentation

No response

@alyssadai alyssadai added flag:schedule Flag issue that should go on the roadmap or backlog. type:feature labels Jan 25, 2024
@rmanaem rmanaem moved this to Backlog in Neurobagel Jan 26, 2024
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Jan 26, 2024
@rmanaem rmanaem removed the status in Neurobagel Mar 6, 2024
@samadpls
Copy link
Contributor

samadpls commented Mar 6, 2024

Hi @alyssadai, 😋 I'm interested in working on this issue if it's still available. could you also provide the reference file for this task? Thank you!

@alyssadai
Copy link
Contributor Author

Hi @samadpls, thanks for your interest on this! Unfortunately, this issue is not currently suitable or ready for an external contribution as the exact specification still needs to be discussed with data owners before we can work on it. In other words, input is needed from our collaborators before we can implement the feature.

If you have specific ideas for this issue however, we welcome you to leave relevant links or resources here!

@alyssadai alyssadai added the flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. label Mar 7, 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 May 22, 2024
@surchs surchs added someday Not a priority right now, but we want to keep this around to think or discuss more. and removed _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag:detail needed Issue requires additional clarification before a decision can be made or it can be implemented. someday Not a priority right now, but we want to keep this around to think or discuss more.
Projects
Status: No status
Development

No branches or pull requests

4 participants