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.

Sign up for GitHub

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

Jump to bottom

Import terms workflow #1766

Closed
anitacaron opened this issue Dec 9, 2022 · 1 comment · Fixed by #1852
Closed

Import terms workflow #1766

anitacaron opened this issue Dec 9, 2022 · 1 comment · Fixed by #1852
Assignees
@gouttegd
Labels
tech

Comments

@anitacaron
Copy link
Contributor

anitacaron commented Dec 9, 2022 •
edited
Loading

Off topic for this PR but: adding IRIs directly has the great advantage that it can be used instantly without having to wait for someone to help or disrupting your editing flow run a slow import update. I wonder if we should tolerate it and have a clean-up job that removes stray declarations from the edtor's file. Alternatively maybe we could have some super minimal temp import update (say IRI + label only) that editors can use rapidly while working on a PR, postponing a full update to later - Maybe add to agenda for Monday tech call?

Originally posted by @dosumis in #1763 (comment)
@anitacaron anitacaron added the tech label Dec 9, 2022
@anitacaron anitacaron changed the title { Off topic for this PR but: adding IRIs directly has the great advantage that it can be used instantly without having to wait for someone to help or disrupting your editing flow run a slow import update. I wonder if we should tolerate it and have a clean-up job that removes stray declarations from the edtor's file. Alternatively maybe we could have some super minimal temp import update (say IRI + label only) that editors can use rapidly while working on a PR, postponing a full update to later - Maybe add to agenda for Monday tech call? } Import terms workflow Dec 9, 2022
@anitacaron
Copy link
Contributor Author

Tech Call on 6th Feb: we agree to support import terms workflows.

@gouttegd gouttegd mentioned this issue Feb 20, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gouttegd gouttegd

Labels
tech
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document policy on delegating import refresh to the tech support group. obophenotype/cell-ontology
2 participants
@anitacaron @gouttegd