If an APO druid is included in a bulk action for descriptive metadata export, it causes the bulk action to retry indefinitely. The problem seems to be that the bulk action looks for a source id, which APOs don't have.
APOs aren't part of descriptive metadata bulk actions. so if an APO is included in a list, the bulk action should report an error to the log and continue to process the rest of the druids in the list.
Backtrace
line 16 of [PROJECT_ROOT]/app/jobs/descriptive_metadata_export_job.rb: block (2 levels) in perform
line 14 of [PROJECT_ROOT]/app/jobs/descriptive_metadata_export_job.rb: each
line 14 of [PROJECT_ROOT]/app/jobs/descriptive_metadata_export_job.rb: each_with_object
If an APO druid is included in a bulk action for descriptive metadata export, it causes the bulk action to retry indefinitely. The problem seems to be that the bulk action looks for a source id, which APOs don't have.
APOs aren't part of descriptive metadata bulk actions. so if an APO is included in a list, the bulk action should report an error to the log and continue to process the rest of the druids in the list.
Backtrace
View full backtrace and more info at honeybadger.io