Bitstream and Bundle embargo dates differ

[Carolyn Sullivan]

Hello all,

Our team has been coming across a weird error where the bitstream and bundle embargo dates sometimes differ.  So far, we've only been able to replicate this error for CC-License and the License, ie:

To produce these results in the CC license and License fields, I:

(1) Submitted an item to a collection with an 'Editors' step, wherein the item had an embargo date of 2027-07-21 initially applied.

(2) Changed the embargo date to 2027-12-25 during the 'Editors' step of the review workflow.

My questions:

(1) Is this actually an error?  I don't think we really care if the text of the CC license and the actual license is embargoed?  I'm not really sure why the software bothers to embargo these documents to begin with, considering they're boilerplate anyways.

(2) I'm more concerned with why we've occasionally gotten mismatches in the bundle and bitstream embargo dates for Bundle ORIGINAL and the primary file.  It's not that problematic given that the updated embargo gets applied to the bitstream anyways, but I can't figure out how to replicate it.  Any ideas?

I've made a Github issue for this problem, but I haven't been able to provide as much detail as I'd like, given that we still can't resolve the main issue: https://github.com/DSpace/DSpace/issues/12805

Any suggestions would be excellent, and thank you so much for your help.

Carolyn.