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

Check for equivalence of term labels for duplicate TermURLs across nodes #68

Open
alyssadai opened this issue Feb 4, 2024 · 3 comments
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again

Comments

@alyssadai
Copy link
Contributor

alyssadai commented Feb 4, 2024

for list_of_terms in cross_node_results:
for term in list_of_terms[data_element_URI]:
unique_terms_dict[term["TermURL"]] = term

If we overwrite previous instances here, would it be reasonable to check first if the term is the same as the one we've already stored? If we ever encounter a situation where some jokester has a neurobagel node where they just make up their own TermURLs for our terms, we could end up with a tricky to debug situation if all that determines what we return here is the order in which we unpack the responses from nodes.

Originally posted by @surchs in #65 (comment)

@surchs surchs added this to Neurobagel Feb 4, 2024
@alyssadai alyssadai added the flag:schedule Flag issue that should go on the roadmap or backlog. label Feb 4, 2024
@rmanaem rmanaem moved this to Backlog in Neurobagel Feb 5, 2024
@rmanaem rmanaem removed the flag:schedule Flag issue that should go on the roadmap or backlog. label Feb 5, 2024
@surchs
Copy link
Contributor

surchs commented Mar 25, 2024

I would vote to bump this from the backlog and give it a someday label instead - this is a yet-to-be-encountered problem. We should address it, but we have more pressing things to do at the moment I think

@surchs surchs added the flag:discuss Flag issue that needs to be discussed before it can be implemented. label Mar 25, 2024
@alyssadai
Copy link
Contributor Author

Sure, that sounds okay to me.

@alyssadai alyssadai removed the flag:discuss Flag issue that needs to be discussed before it can be implemented. label Mar 26, 2024
@alyssadai alyssadai removed the status in Neurobagel Mar 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 Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
_flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again
Projects
Status: No status
Development

No branches or pull requests

3 participants