Class AnnotationsWebService.RuledOutTermValueObject

java.lang.Object
ubic.gemma.rest.AnnotationsWebService.RuledOutTermValueObject
Enclosing class:
AnnotationsWebService

public static class AnnotationsWebService.RuledOutTermValueObject extends Object
One term that was retrieved for the query and rejected as not naming it.
Author:
tesarst
  • Field Details

    • REASON_NEAR_MATCH

      public static final String REASON_NEAR_MATCH
      Lexically near the query but not naming it — a different entity.
      See Also:
    • REASON_OUT_OF_CATEGORY

      public static final String REASON_OUT_OF_CATEGORY
      Names the query, but sits in a namespace that is impossible for the stated category.
      See Also:
  • Constructor Details

    • RuledOutTermValueObject

      public RuledOutTermValueObject(@Nullable String value, @Nullable String valueUri, @Nullable String matchedVia, String reason)
  • Method Details

    • getReason

      public String getReason()
      Why this term is not the answer: near_match (lexically close, different entity) or out_of_category (right name, impossible namespace for the category). The two warrant different downstream handling — an out-of-category hit may indicate the FACTOR is mis-categorised rather than the term being wrong.
    • getValue

      @Nullable public String getValue()
    • getValueUri

      @Nullable public String getValueUri()
    • getMatchedVia

      @Nullable public String getMatchedVia()
      Why it came back at all — label_prefix, label_tokens, … Never one of the equality tiers; those are exactly the rows that were kept. null when the term could not be attributed (see the matchedVia notes on the search endpoint).