PM87989: MODELER ENTITY ANALYTICS DOCUMENTATION DESCRIBING "USAGE TYPES" IS INADEQUATE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as fixed if next.

Error description

  • You are trying to understand "Usage Types" within Modeler Entity
    Analytics - what values it can have and the effect of these. The
    current documentation does not explain this sufficiently.
    

Local fix

  • Further details on this option are available below:
    
    Usage Type in Entity Analytics
    
    -Usage types are arbitrary labels.
    -You can make up your own usage types in the Repository
    Configuration window.
    -Pretty much any string will do. We prevent you from entering
    spaces and invalid characters.
    -We automatically change what you type to upper case as it is
    entered.
    -You can have as many usage types as you want.
    -Usage types don't have to be meaningful, but it will help you
    when mapping later.
    -When you are mapping we do warn (in a red font) if you have
    mapped some elements with one usage type and others with a
    different one.
    
    Usually an error is displayed if you try to map two fields to
    the same feature.element. Usage types are a way of letting you
    map two or more fields to the same feature.element, and be able
    to match across them.
    
    For example if you defined two separate features: HOMEADDRESS
    and WORKADDRESS, there would be no matching between these.
    
    If one entity has a HOMEADDRESS which is the same as the
    WORKADDRESS of another entity,  there is no matching - because
    it is a different feature.
    
    However, if you re-use a single feature with different usage
    types then the resolution understands that ADDRESS.WORK is the
    same as ADDRESS.HOME.
    
    You can re-use usage types for different features or have
    different ones; for example, HM and WK for telephone and HOME
    and WORK for address.  It does not matter because we don't match
    across telephones against addresses; however, if you can be
    consistent it will help you to identify and group fields
    together later on.
    
    When we feed multiple entity types into a single repository,
    provided you are using the same feature, it should not matter
    what the usage types are. For example, if you define WK and HM
    as usage types of ADDRESS for the entity type COMPANY that
    should still be matched against WORK and HOME as usage types of
    ADDRESS for PERSON.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to IBM SPSS Modeler 16.0                      *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM87989

  • Reported component name

    SPSS ENT ANALYT

  • Reported component ID

    5725A64EA

  • Reported release

    F00

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-29

  • Closed date

    2013-12-10

  • Last modified date

    2013-12-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • RF00 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

SPSS Modeler
Entity Analytics

Software version:

15.0

Reference #:

PM87989

Modified date:

2013-12-10

Translate my page

Machine Translation

Content navigation