Document solution for renaming misnamed JPG datastreams

[mjordan]

We should document a solution to the problem caused by #452. Datastream CRUD is capable of doing this. Maybe a good Cookbook entry?

[MarcusBarnes]

Good idea. Would someone be able to confirm what happens if you try regenerating the misnamed JPEG datastream? Does it stay JPEG or does it become JPG? (I'm assuming that it stays JPEG, if not, there could be a solution that involves batch derivative regeneration.)

[mjordan]

@MarcusBarnes We've got about 900,000 JPEG datastreams, so I'll check this. Checking one of the 900,000 or page objects we migrated from CONTENTdm, I notice that the JPEG datastream doesn't have a 'regenerate' link:

like the properly named JPG datastream does:

My plan is to use Datastream CRUD to download the JPEG, then upload the same files as JPG, then delete the JPEG.

[MarcusBarnes]

Thank you for confirming.

[mjordan]

How about documenting how to change a DSID in the CRUD README, and then in the MIK cookbook entry, point out that documentation and contextualize it for the JPEG/JPG issue?