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

Automate removing things from NOR dashboard after they're accepted in OBO Foundry #22

Open
cthoyt opened this issue Nov 15, 2022 · 3 comments · May be fixed by #23
Open

Automate removing things from NOR dashboard after they're accepted in OBO Foundry #22

cthoyt opened this issue Nov 15, 2022 · 3 comments · May be fixed by #23

Comments

@cthoyt
Copy link

cthoyt commented Nov 15, 2022

Would it make sense to automate removing things from the NOR dashboard after they're accepted in OBO Foundry?

The steps that could be taken in a script in a GitHub Actions workflow running once nightly or on request:

  1. Get all ontologies' prefixes from https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/registry/ontologies.yml
  2. Filter all entries in https://github.com/OBOFoundry/obo-nor.github.io/blob/master/dashboard-config.yml that have a prefix that's in the OBO Foundry already
  3. Commit the dashboard-config.yml back to the repo if there are any changes
@matentzn
Copy link
Collaborator

Yeah, good idea. However, we will have a curator appointed to this task anyways soon, so I wouldn't go nuts with personal time resources on this one.

@cthoyt
Copy link
Author

cthoyt commented Nov 16, 2022

I estimate it will take 10 minutes to get this working. I'm sure the person doing it manually will take much more effort than this to train and spend on it :p

@cthoyt
Copy link
Author

cthoyt commented Nov 16, 2022

I'll do this over the weekend. When you assign someone to this role, we can check see if they can understand it and where it needs more docs.

cthoyt added a commit to cthoyt/obo-nor.github.io that referenced this issue Nov 19, 2022
@cthoyt cthoyt linked a pull request Nov 19, 2022 that will close this issue
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