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

Instantiate DRSMetaresolver from external data rather than hard-coded in constructor #4

Open
ianfore opened this issue Jul 28, 2022 · 2 comments
Assignees

Comments

@ianfore
Copy link
Contributor

ianfore commented Jul 28, 2022

Options include

Note that client sub-class required depends on the server.
There may be sufficient information in registry to drive this.

@ianfore ianfore self-assigned this Jul 28, 2022
@briandoconnor
Copy link
Contributor

Need a ticket on DRS repo for seeing what's happening with n2t.org and bioregistry.io. For now Michael L will just cache info from identifiers.org

@ianfore
Copy link
Contributor Author

ianfore commented Aug 3, 2022

Merged in @MichaelLukowski 's standalone resolver class in resolver.py

Will look at incorporating the capability into DRSMetaresolver.

Note that we still have the problem that the method of authorization is host specific and identifiers.org does not give us any information about that. This is the sub-class issue mentioned above. Besides the service information from GA4GH registry the /service-info endpoint on the server itself may be useful.

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

No branches or pull requests

2 participants