Add force argument in ingest_zarr_archive

[jjnesbitt]

Addresses underlying cause of #1004.

@dchiquito Right now, the management command defaults to force=False. I'd think most of the time we're using the management command, we'd want to use force=True. Do you think we should default force=True in the management command? I'm leaning towards yes.

I'm also wondering how we can improve the process of checksum updates. That is, if there is ever a need again to update the checksum format, it'd be good to have some automated process around this, rather than someone needing to manually run a management command. I get the feeling that any automated solution would be overly costly in the average case of not needing to update. @dchiquito any thoughts?

[dchiquito]

I think the least destructive option should always be the default, so I vote for force=False. The first thing I always do after digging up a management command is checking the --help to see what options it has, and possibly reviewing the source code so I know exactly what it's going to do.

I also don't think an automated process is a good idea here. Having a silently watching daemon thingy that will swoop in and reingest everything when it feels like something has changed sounds creepy to me, not reassuring. If we make a change to the data format, we should expect to have to do some data migration, which I would always expect to be a manual process. I would not trust some automated script written in the distant past to handle that migration for me.

[dandibot]

🚀 PR was released in v0.2.8 🚀