Bulkrax Importer ID listed on Works list PID and Link to Incorrect Importer

[KevinJonesMeta]

Descriptive summary

Work PID is listed in Bulkrax Importer ID value at bottom of work showpage. The Importer ID value links to importer 1097 which is incorrect on example works.
Both example works from recent OSU importers go to the same UO importer.
https://oregondigital.org/concern/documents/0v838297v
Correct importer: https://oregondigital.org/importers/3964
https://oregondigital.org/concern/documents/dz010s42r
Correct importer: https://oregondigital.org/importers/3961

Affected works are faceted under importer id 1097 in Review Submissions queue. 32 works listed under that facet as of 01/05/26, all are recent OSU works.

Expected behavior

The bulkrax importer ID that created the work is the value for Bulkrax Importer ID on work show page. Importer ID link goes to correct importer page.

Related work

Link to related tickets or prior related work here.

Accessibility Concerns

Add any information here to indicate any known or suspected accessibility issues for this ticket

[lsat12357]

Overwriting original_identifier should result in the show page importer link changing to the most recent importer. The bug here was that the code was returning the id of an exporter.

[lsat12357]

QA:

1. export a work
2. in the csv, set the original_identifier to the pid and import
3. after import is finished, the show page importer link should reference the oldest importer associated with work

[KevinJonesMeta]

QA Fail.
@lsat12357 After import is finished the pid is listed as the importer link and opens the latest importer. https://staging.oregondigital.org/concern/documents/47429921g

Same outcome for this work https://staging.oregondigital.org/concern/documents/c247ds185

So they are going to the most recent importer, but the displayed Importer ID is the pid.

[lsat12357]

I looked at your export for these 2 works, and you selected 2 test items that have no original_identifier or original_identifier_1 values, so there is no importer associated with the work other than the one you used for the test

[KevinJonesMeta]

Ah, okay. I misunderstood that part. So for everything we already have, this issue is not going to go away because they are legacy works that don't have an importer from migration?

[lsat12357]

to prep an object for QA, I created a new image with this importer
https://staging.oregondigital.org/importers/256?locale=en
which created
https://staging.oregondigital.org/concern/images/3b591867r?locale=en
then I exported with
https://staging.oregondigital.org/exporters/91?locale=en
modified the export by removing the value for original_identifier
and imported with
https://staging.oregondigital.org/importers/257?locale=en
and now the value of bulkrax_identifier is ["257-0", "256-0"]
which can be verified here: https://staging.oregondigital.org/concern/images/3b591867r.json
Once #3591 is merged/deployed, admin metadata on the show page should display 256-0 as the identifier and link to importer 256