Skip to content

[ENG-8026] Reference LINK addon implementation: Zenodo #285

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

Conversation

opaduchak
Copy link
Collaborator

@opaduchak opaduchak commented May 15, 2025

Purpose

Reference LINK addon implementation: Zenodo

Ticket

https://openscience.atlassian.net/browse/ENG-8026

@cslzchen cslzchen changed the title Reference Zenodo imp Reference LINK addon implementation: Zenodo May 16, 2025
@cslzchen cslzchen changed the title Reference LINK addon implementation: Zenodo [ENG-8026] Reference LINK addon implementation: Zenodo May 16, 2025
Copy link
Collaborator

@cslzchen cslzchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to my comments, can we add some comments or Docstring in the implementation file addon_imps/link/zenodo.py to info readers of what each class methods do.

Another note, after we feel good with the reference PR, we can close this PR (to get rid of the conversations, JIRA stuff, etc.) and open a new clean PR as the final reference PR.

Copy link
Collaborator

@cslzchen cslzchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Let me make a PR to the feature branch to adjust the order. I won't change the number to avoid migration for now. starting from 103x is good enough for now. If we ever run out of 1001~1029 for other types of addons in the future, we will handle it when it happens.

Copy link
Collaborator

@cslzchen cslzchen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Closing this PR to open a new one for documentation & reference purpose.

@cslzchen cslzchen closed this May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants