objectId in contentMetadata should be namespace qualified

[LynnMcRae]

There are a lot of contentMetadata datastreams that express objectId as "aa123bb4567" instead of "druid:aa123bb4567". The fully qualified form is the correct one, else the attribute would have been called druid. Not sure if any dor-services code is implicated (fixture objects mostly look correct), or if it is external processes making contentMetadata stubs for assembly. Should check with labs, Hydrus and Revs, others? on the contentMetadata stubs, or normalize it at the start of accessioning.

[LynnMcRae]

@calavano Tony, can you check where you are making stub contentMetadata for this?

[calavano]

I'm using the assembly-objectfile gem. It looks like it was stripping the druid: if it existed until the recent commit. (Comment at the top of content_metadata.rb implies the prefix is not required)

I'll update the gem and add the prefix to my code.