To confirm: the first link is to common MR metadata fields for inclusion in the sidecar JSON files, rather than DICOM fields. It references relevant DICOM fields in the field description, to help in populating the field.
EDIT: The link corresponds to page 311 in the provided PDF.
There is some work in HeudiConv on automatically populating the IntendedFor field correctly, but this is still certainly something that you’d want to check.
To your question of using B0FieldIdentifier and B0FieldSource: Yes, you’d want to place the B0FieldSource field in the BOLD images’ JSON sidecar ! The _phasediff.json sidecar should look like this example
{
"EchoTime1": 0.00600,
"EchoTime2": 0.00746,
"B0FieldIdentifier": "phasediff_fmap0"
}
I’d expect that to work appropriately. There have been previous reports of the reverse situation (i.e., not working with IntendedFor only), but since these reports occur sporadically, I’m wondering if the working directory wasn’t accidentally re-used. Can you confirm that you re-ran both cases in a clean environment ?