bkn-relation-bind

To classify relation types, analyze bound object view schemas to determine if relationships are direct or require a data_view based on foreign keys, field name alignment, or cross-source links. This classification enables accurate intermediate view binding for complex relationships.

You need to bind intermediate views when object relationships require a data_view type rather than a direct connection. This occurs when foreign keys, field name alignment, or cross-source links indicate that an intermediate data view is necessary to support the relationship.

To set up relation binding, run this step after object binding and before mapping extraction. It operates on bound object views and relation lists to classify relations, propose intermediate views, and manage pending workflows with user confirmation when needed.

Yes, you can extract mapping rules after relation type detection. This step coordinates with the mapping phase by preparing bound intermediate views and supporting pending states, ensuring mapping rule extraction operates on correctly classified direct and data_view relationships.

The best way to handle cross-source links is to classify them as data_view relationships and bind recommended intermediate views with candidate recommendations. This approach ensures cross-source relationships are properly supported before proceeding to mapping extraction.

Relation binding requires user confirmation when proposed intermediate views need validation before binding. This ensures proposed candidate recommendations for data_view relationships are verified, allowing the workflow to proceed accurately from object binding to mapping extraction.