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

iterate through bricks and add .bb directory with linkml.yaml #29

Open
2 tasks done
Tracked by #27
tomlue opened this issue Apr 1, 2024 · 2 comments
Open
2 tasks done
Tracked by #27

iterate through bricks and add .bb directory with linkml.yaml #29

tomlue opened this issue Apr 1, 2024 · 2 comments
Assignees

Comments

@tomlue
Copy link
Contributor

tomlue commented Apr 1, 2024

start with:

  • ctdbase
  • ice, toxcast, tox21
@tomlue tomlue mentioned this issue Apr 1, 2024
5 tasks
@bhlieberman
Copy link

CTDBase is incoming here. I made the file brick.yaml because that is the name in ToxicoDB. Should it be changed to linkml.yaml instead?

@zmughal
Copy link
Contributor

zmughal commented Apr 18, 2024

CTDBase is incoming here. I made the file brick.yaml because that is the name in ToxicoDB. Should it be changed to linkml.yaml instead?

brick.yaml is fine for now. It's a data file that contains metadata describing the brick. I was thinking that if there needs to be a schema file, that might be better managed in another file that would use a LinkML model (classes, slots, types, enums). That can be called brick-schema.yaml. That can import other schemas and in turn brick.yaml would use identifiers from brick-schema.yaml to associate tables with the schemas.

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

3 participants