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

Decide how to handle Database and Tool models - then implement them #39

Closed
joncison opened this issue Aug 11, 2020 · 2 comments
Closed
Assignees
Labels
high priority A high-priority issue that should be acted on ASAP.

Comments

@joncison
Copy link
Collaborator

These are both currently defined here as subclass of Resource, but it's unclear how to model them: the bio.tools API already handles databases and tools and we should re-use this so far as possible (an implementation of a database and tool model in the IFB catalogue may not be necessary, or perhaps just a simple one that leverages the bio.tools API).

@joncison joncison changed the title Decide how to handle Database and Tool models Decide how to handle Database and Tool models - then implement them Sep 4, 2020
@joncison joncison added the high priority A high-priority issue that should be acted on ASAP. label Sep 4, 2020
@joncison
Copy link
Collaborator Author

From discussions with @hmenager - need to settle on a short list of attributes for databases and tools (could be one, or two different lists) which would be a subset of what's available in bio.tools. This is to support search over this content.

@bryan-brancotte
Copy link
Member

Tool is down, model is ongoing with #228 #239

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high priority A high-priority issue that should be acted on ASAP.
Projects
None yet
Development

No branches or pull requests

3 participants