Skip to content

Class: TrackedIssue

Structured pointer to an external tracker issue (typically a GitHub issue) used to record curation provenance. Use this for things like upstream ontology term requests, ontology coverage gaps, schema follow-ups, or any external ticket tied to a dismech object, instead of stashing raw URLs in free-text notes fields. Attachable at multiple levels of the model (disease entries, mappings, etc.).

URI: dismech:class/TrackedIssue

 classDiagram
    class TrackedIssue
    click TrackedIssue href "../../classes/TrackedIssue/"
      TrackedIssue : notes

      TrackedIssue : title

      TrackedIssue : tracked_issue_role

      TrackedIssue : tracked_issue_status

      TrackedIssue : url

Slots

Name Cardinality and Range Description Inheritance
url 1
Uri		 Canonical URL of the tracked issue direct
title 0..1
String		 Short human-readable title of the tracked issue direct
tracked_issue_role 0..1
String		 Role this tracked issue plays relative to the dismech content it is attached ... direct
tracked_issue_status 0..1
String		 Last known status of the tracked issue (e direct
notes 0..1
String		 direct

Usages

used by used in type used
SurrogateEndpointCollection tracked_issues range TrackedIssue
Disease tracked_issues range TrackedIssue
TermMapping tracked_issues range TrackedIssue
ICD10CMMapping tracked_issues range TrackedIssue
ICD11FMapping tracked_issues range TrackedIssue
MondoMapping tracked_issues range TrackedIssue
NCITMapping tracked_issues range TrackedIssue
FDASurrogateEndpointCollection tracked_issues range TrackedIssue

Identifier and Mapping Information

Schema Source

  • from schema: https://w3id.org/monarch-initiative/dismech

Mappings

Mapping Type Mapped Value
self dismech:TrackedIssue
native dismech:TrackedIssue

LinkML Source

Direct

name: TrackedIssue
description: Structured pointer to an external tracker issue (typically a GitHub issue)
  used to record curation provenance. Use this for things like upstream ontology term
  requests, ontology coverage gaps, schema follow-ups, or any external ticket tied
  to a dismech object, instead of stashing raw URLs in free-text `notes` fields. Attachable
  at multiple levels of the model (disease entries, mappings, etc.).
from_schema: https://w3id.org/monarch-initiative/dismech
slots:
- url
- title
- tracked_issue_role
- tracked_issue_status
- notes
slot_usage:
  url:
    name: url
    description: Canonical URL of the tracked issue.
    required: true
  title:
    name: title
    description: Short human-readable title of the tracked issue.

Induced

name: TrackedIssue
description: Structured pointer to an external tracker issue (typically a GitHub issue)
  used to record curation provenance. Use this for things like upstream ontology term
  requests, ontology coverage gaps, schema follow-ups, or any external ticket tied
  to a dismech object, instead of stashing raw URLs in free-text `notes` fields. Attachable
  at multiple levels of the model (disease entries, mappings, etc.).
from_schema: https://w3id.org/monarch-initiative/dismech
slot_usage:
  url:
    name: url
    description: Canonical URL of the tracked issue.
    required: true
  title:
    name: title
    description: Short human-readable title of the tracked issue.
attributes:
  url:
    name: url
    description: Canonical URL of the tracked issue.
    from_schema: https://w3id.org/monarch-initiative/dismech
    rank: 1000
    alias: url
    owner: TrackedIssue
    domain_of:
    - ExternalAssertion
    - TrackedIssue
    range: uri
    required: true
  title:
    name: title
    implements:
    - linkml:title
    description: Short human-readable title of the tracked issue.
    comments:
    - 'The `linkml:title` annotation is INERT for linkml-reference-validator detection
      — lrv''s TitleURIs matches only "dcterms:title" / "dc/terms/title". Where this
      slot IS title-checked (on PublicationReference) that happens via lrv''s exact-name
      fallback FallbackSlotNames.TITLE = ("title",), not via this annotation. Kept
      because it is a reasonable semantic mapping, and noted here for the same reason
      the EvidenceItem `reference_title` comment exists: an annotation that looks
      like it enables a check, but does not, misleads readers. The title-normalization
      work that this deferral pointed at has now happened (EvidenceItem.reference_title
      carries `dcterms:title` and is checked), but this slot is still NOT retargeted:
      it is shared by PublicationReference, Dataset and TrackedIssue, so swapping
      the URI would newly expose Dataset.title and TrackedIssue.title to lrv detection.
      PublicationReference.title loses nothing by waiting — it is already checked
      via the exact-name fallback. Retarget only alongside a check of what the other
      two classes would then be asserting.'
    from_schema: https://w3id.org/monarch-initiative/dismech
    rank: 1000
    alias: title
    owner: TrackedIssue
    domain_of:
    - Dataset
    - PublicationReference
    - TrackedIssue
    range: string
  tracked_issue_role:
    name: tracked_issue_role
    description: Role this tracked issue plays relative to the dismech content it
      is attached to. Free-text but common values include "ontology_term_request",
      "ontology_coverage_gap", "schema_followup", "curation_followup", and "external_tracker_link".
    examples:
    - value: ontology_term_request
    - value: schema_followup
    from_schema: https://w3id.org/monarch-initiative/dismech
    rank: 1000
    alias: tracked_issue_role
    owner: TrackedIssue
    domain_of:
    - TrackedIssue
    range: string
  tracked_issue_status:
    name: tracked_issue_status
    description: Last known status of the tracked issue (e.g., "OPEN", "CLOSED", "MERGED").
      This is a curator-recorded snapshot and may drift from the live tracker state.
    examples:
    - value: OPEN
    - value: CLOSED
    from_schema: https://w3id.org/monarch-initiative/dismech
    rank: 1000
    alias: tracked_issue_status
    owner: TrackedIssue
    domain_of:
    - TrackedIssue
    range: string
  notes:
    name: notes
    examples:
    - value: Contagious stage where symptoms appear and the bacteria can be spread
        to others.
    from_schema: https://w3id.org/monarch-initiative/dismech
    rank: 1000
    alias: notes
    owner: TrackedIssue
    domain_of:
    - GeneticContext
    - OnsetDescriptor
    - PhenotypeContext
    - Dataset
    - ExperimentalModel
    - Experiment
    - ExperimentalPerturbation
    - ExperimentalReadout
    - ExperimentalControl
    - ClinicalTrial
    - ComputationalModel
    - ModelVariable
    - DifferentialDiagnosis
    - ReferenceRange
    - SurrogateEndpoint
    - SurrogateEndpointCollection
    - ExternalAssertion
    - TrackedIssue
    - Prevalence
    - GeneCaseFraction
    - ProgressionInfo
    - ClinicalBurden
    - EpidemiologyInfo
    - Pathophysiology
    - Phenotype
    - Biochemical
    - HistopathologyFinding
    - ImagingFinding
    - Genetic
    - Environmental
    - Disease
    - Stage
    - AgentLifeCycle
    - AgentLifeCycleStage
    - AnimalModel
    - Treatment
    - Transmission
    - Diagnosis
    - ClassificationAssignment
    - Definition
    - CriteriaSet
    - TermMapping
    - MappingConsistency
    - ComorbidityAssociation
    - AssociationSignal
    - AssociationMetric
    - AssociationStatistics
    - MechanisticHypothesis
    - Discussion
    - Grouping
    - GroupingCriteria
    - GroupingMember
    - DifferentiatingMechanism
    - ModuleCollection
    - ModuleCollectionMember
    range: string