Content
BCF Entries - 1 per element or 1 per problem with linked elements
Added by Glen Worrall 13 days ago
This is a question mainly for the OpenProject community.
I am in the process of integrating https://index.itwin.app with the OpenProject (including hosted or BYO).
For issues
2. Group Publishing: 1 BCF Topic with Multiple Elements vs. Multiple BCF Entries
I have the following query ...
Current Behavior: Publishing at the group level publishes individual BCF entries for each issue in the group (in your case, 2 distinct BCF topics).
Why: Each defect has its own distinct GUID, element viewpoint, and status lifecycle, allowing project members in OpenProject to assign, track, resolve, and close each defect independently.
Alternative: Single Group-Level Cluster Topic
In buildingSMART BCF 2.1, a single BCF topic can contain multiple element component references:
json
{
"guid": "cluster-uuid",
"title": "[WRSH_FireAlarm.ifc] 2 Classification & Data Quality Issues",
"components": [
{ "ifc_guid": "0x10000000009" },
{ "ifc_guid": "0x1000000000b" }
]
}
Option A (Current - 1 Topic per Issue): Best for granular tracking where each element issue may be resolved by different subcontractors or at different times.
Option B (1 Topic per Group with Multiple Components): Best for high-volume batch triage where you want a single ticket in OpenProject covering all elements in that group.
Would you prefer group publishing to generate 1 single BCF Topic with multiple element components, or continue publishing individual BCF entries per issue in batch?
See screen shot in comments ... would you want 5 individual BCF issues to track for the same type of issue ... or 1 issue with 5 elements ?
Cross-posted from LinkedIN
https://www.linkedin.com/feed/update/urn:li:activity:7499408365459075072/