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

Clarify content in resources.yaml #39

Closed
4 of 5 tasks
glass-ships opened this issue Nov 16, 2023 · 1 comment · Fixed by #40
Closed
4 of 5 tasks

Clarify content in resources.yaml #39

glass-ships opened this issue Nov 16, 2023 · 1 comment · Fixed by #40
Assignees

Comments

@glass-ships
Copy link
Contributor

glass-ships commented Nov 16, 2023

Blocker to monarch-initiative/monarch-app#463

It would be helpful to understand what is in this file and how it is organized.

For example:

  • what do we define as "standards"
  • what differentiates "data" from "ontologies"
  • how are we separating tools from repositories
  • what is the point of the documentations section, when the documentation field exists for entries in the other sections?
  • anything else to make maintaining this beast of a file (and using it in such cases as generating the resources page for the website) easier
@matentzn
Copy link
Member

matentzn commented Nov 17, 2023

Thank you for this issue. In #40 I have:

  1. Defined all sections (standards, tools, data, ontologies)
  2. Removed everything from the documentation section that is not just documentation (leaving two items). The website uses the other fields now to generate the overview page.
  3. I generated the overview of the file you need now automatically and deposit it as part of the documentation (docs/resources/monarch_app_resources.json).

What is still missing is

how are we separating tools from repositories

Right now they are redundant, but in a future push we should get rid of the "repository" section altogether and let it be driven entirely by asset (tool, standards) list.

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 a pull request may close this issue.

2 participants