Tessa Walsh

If it's not clear from the context, the collection sequence should be configured in your `config.yaml` file.

Hi @osintalex, thanks for the issue! The use case and rationale makes perfect sense to me. I think if we're going to expand the metadata fields on the archived items,...

@ikreymer To update with smaller improvements

Hi Kyle, I think it might be your folder structure that's the issue. The Disk Image Processor expects that all of your disk images (as well as log files, photos,...

Hi Kyle, My best guess is that there's something about disk image ARCH281911.img (or the next one) that's causing the script to crash - otherwise, even if it was unable...

Need to find generic disk images that can be hosted on Github repo for these

Hi Johan. This would be a great addition! I wonder if Alex Nelson's [disktype_to_dfxml](https://github.com/ajnelson-nist/disktype_to_dfxml) might come in handy here. It's been on my list to add better handling of multi-partition...

There's also [disktype_json](https://github.com/felixbaumann/disktype_json), which spits out JSON instead of plain text files. That might make parsing/handling a bit easier.

> ~I think this is a problem for `queued` and `failed` as well?~ > > Nevermind, I see those sections actually expect serialized JSON objects? I believe these both should...

Copying comment from #563: I think this may be as expected. In the 1.x releases, if `--failOnInvalidStatus` is not set, the crawler doesn't consider 4xx/5xx responses failures, so they wouldn't...