New term added with flexible metadata not exported

[laritakr]

Summary

This is for flexible = TRUE and FALSE

A new term added through flexible metadata was not included in the export CSV

[ShanaLMoore]

isn't this because it's not in the tenant's bulkrax field mappings? We saw this behavior for hyku up/st jude and when we made her field mappings match her profile it exported correctly.

[laritakr]

isn't this because it's not in the tenant's bulkrax field mappings? We saw this behavior for hyku up/st jude and when we made her field mappings match her profile it exported correctly.

I don't think that's how it's supposed to behave. I believe it's supposed to pick up all the metadata, and it DID import my foo term without mapping it, so I expected it to export it as well.

This may not be a top priority to fix, but even if this is temporary behavior, I don't think it's what we want long-term.

[ShanaLMoore]

Triage RESULTS: ✅ CONFIRMED cc @laritakr

tested locally (HYKU7 FLEX ON)

I updated the metadata profile with a test field. bulkrax -> export everything. That test property was missing from the exported csv.

Problem

When HYRAX_FLEXIBLE=true, new metadata terms added to the profile (m3_profile.yaml) are not included in Bulkrax CSV exports. This happens because:

• Bulkrax uses tenant-specific field mappings stored in Account#bulkrax_field_mappings
• These mappings are initialized when the tenant is created from Hyku.default_bulkrax_field_mappings
• When new properties are added to the profile later, the tenant's stored mappings are not updated
• Result: Exports only include fields that existed when the tenant was created

Brainstorming a Solution

Modify lib/bulkrax/per_tenant_field_mapping_decorator.rb to dynamically merge properties from the current Hyrax::FlexibleSchema profile into the field mappings at runtime when HYRAX_FLEXIBLE=true.
Implementation approach:

• Check if HYRAX_FLEXIBLE is enabled
• Fetch current profile properties from Hyrax::FlexibleSchema.current_version
• For each parser (CSV, Bagit, OAI, etc.), add any missing profile properties with default mappings: { from: [property_name], split: true }
• Preserve existing tenant customizations (don't override existing mappings)

[laritakr]

What I am curious about here is how the importer brings in the additional terms, but the exporter doesn't. Is there anything on the importer side that already works and might be relevant?

[SixtyGrit]

Is there a workaround here? I.e. manually-update the bulkrax field mapping?

[ShanaLMoore]

This is a known pre-existing, not a hyku7-specific issue. Enabling Flexible metadata amplifies the problem.