HDMS Wiki Home

  • BadEorank
  • Last edited by Donna_Reynolds on Oct 2, 2003 5:32 pm

    EOR_BAD_EORANK

    The EORANK data in the BCD (formerly a free-for-all entry field of up to 4 characters, with some guidelines) is now a constrained entry field in Biotics 4 (constrained by the D_BASIC_EO_RANK domain).

    There are now exactly 22 valid BasicEoRank values. During this QC, you will find all the entries in your database that do not match one of those values, then you will either edit your values to comply, or you will configure the transformation from your values to one of the 22 valid values in the arev\hdms\ini\custom.cfg file in the [EORANK] section.

    Below is the list of the valid BasicEoRank values:

    [D_BASIC_EO_RANK]
    ; hand modified 2002-10-04 for new basic eo ranks
    ; modified again 2003-07-28 for newer basic eo rank values
    ; and again 2003-10-2 to revert to previous values pending adoption of newer ones!
    A|Excellent estimated viability
    A?|Possibly excellent estimated viability
    AB|Excellent or good estimated viability
    AC|Excellent, good, or fair estimated viability
    B|Good estimated viability
    B?|Possibly good estimated viability
    BC|Good or fair estimated viability
    BD|Good, fair, or poor estimated viability
    C|Fair estimated viability
    C?|Possibly fair estimated viability
    CD|Fair or poor estimated viability
    D|Poor estimated viability
    D?|Possibly poor estimated viability
    E|Verified extant (viability not assessed)
    F|Failed to find
    F?|Possibly failed to find
    H|Historical
    H?|Possibly historical
    X|Extirpated
    X?|Possibly extirpated
    U|Unrankable
    NR|Not ranked
    

    QC Procedure:

    1. SELECT EOR WITH HDMS_EORANK [] 'BAD' BY EORANK
    2. LIST EOR EORANK HDMS_EORANK JUSTLEN 50
    3. For each record listed, either fix the value, or configure it in the arev\hdms\ini\custom.cfg file in the [EORANK] section so that the value is listed and assigned to a standard value.(From the Main Menu choose 'Adjuncts' | 'HDMS Conversion Utilities' | 'Edit CUSTOM.CFG')
    4. After making and saving the edits to the arev\hdms\ini\custom.cfg file, execute LOAD_CONFIG HDMS\INI\CUSTOM.CFG (this is done automatically once you save and exit the CUSTOM.CFG file if you used the 'Edit CUSTOM.CFG' option on the 'HDMS Conversion Utilities' menu).
    5. Re-run the QC until there are no records found.

    Resolution:

    Either fix the data or modify the configuration in the [EORANK] section of the arev\hdms\ini\custom.cfg file.

    Below is the original configuration in the [EORANK] section of the arev\hdms\ini\custom.cfg file:

    [EORANK]
    * HDMS EORANK custom conversion. In HDMS, the EORANK is split into a 'basic eo rank'
    * and an 'origin subrank'. You can configure the basic eorank here. Although you may override
    * a standard rank, ultimately, you must assign BCD values to a standard rank.
    *
    * RULE SYNTAX: {liternal rank as stored in BCD} + "=" + {new literal rank for HDMS}
    *
    *	ex: O=F
    *
    * List rules in elimination order. In other words, if a rule passes, it eliminates
    * checking subsequent rules. Reduce extraneous spaces as much as possible. Use the 
    * list in the section [D_BASIC_EORANK] in the domain.cfg for valid ranks.
    *
    * You can assign a default value to the blank EORANKS by starting the line with the equals sign:
    *  
    *    =H
    *
    *A/B=AB
    *AB?=AB
    *B6=B
    *BC?=BC
    *CB=BC
    *CD?=CD
    * VAHP's ranks with special rules: take rank on the left if lastobs is before 1981
    *    otherwise take rank on the right. This is being handled in the local 
    *    symbolic HDMS_BASIC_EORANK.
    *?=H|E
    *O=H|E
    *T=H|E
    *]=H|E
    

    Did you notice the special treatment for VAHP's ranks? You can also take advantage of this logic or modify it for your particular needs. Below is the original symbolic field for the HDMS_BASIC_EORANK symbolic field for the EOR file. Note that VAHP's logic will not kick in unless you configure a pipe-separated value on the right-hand side of the equals sign in the CUSTOM.CFG file:

    * HDMS conversion symbolic
    * Modified the output of HDMS_EORANK if HDMS_EORANK contains pipes.
    *
    * VAHP's logic: take first value if lastobs is less than 1981,
    *        else take the 2nd
    ANS = {HDMS_EORANK}
    IF INDEX( ANS, "|", 1) THEN
      LASTOBS = {LASTOBS}[1,4]
      IF NOT(NUM(LASTOBS)) OR LASTOBS < 1981 THEN
        ANS = FIELD( ANS, "|", 1)
      END ELSE
        ANS = FIELD( ANS, "|", 2)
      END
    END
    @ANS = ANS
    

    Back to HdmsQcBatchProcess
    Back to DataQc