Skip to content

Make decisions one way or the other on converting additional class imports to proper ODK imports #253

New issue
New issue
Closed
Feature
Closed
Make decisions one way or the other on converting additional class imports to proper ODK imports#253
Feature
Labels
discussion

Description

@hoganwr
hoganwr
opened on Aug 14, 2024

Besides issues #249, #250, #251, and #252, we have classes from the following ontologies that could be converted to proper ODK import. We need to decide, for each one, whether to do it and the priority (the ones for which issues already logged are top priority):

  1. OBI
  2. DOID
  3. PATO
  4. UBERON
  5. VO
  6. UO
  7. FBCV

Activity

  1. hoganwr
    added
    discussion
    on Aug 14, 2024

  2. hoganwr commented on Jul 21, 2026

    @hoganwr
    hoganwr
    on Jul 21, 2026
    ContributorAuthor

    OBI was made a separate import in ODK in #274

  3. hoganwr
    removed
    discussion
    on Jul 25, 2026
  4. hoganwr
    pinned this issue on Jul 25, 2026
  5. hoganwr
    unpinned this issue on Jul 25, 2026
  6. hoganwr
    pinned this issue on Jul 25, 2026
  7. hoganwr
    unpinned this issue on Jul 25, 2026
  8. hoganwr
    added
    discussion
    on Jul 25, 2026
  9. hoganwr
    added the
    Bug
    issue type on Jul 25, 2026
  10. hoganwr
    changed the issue type from
    Bug
    to
    Feature
    on Jul 25, 2026
  11. ApolloDev
    locked and limited conversation to collaborators on Jul 28, 2026
  12. hoganwr
    converted this issue into a discussion #276 on Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussion

    Type

    Feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions