This is a tricky situation! It's great that you're catching these issues early in the preservation process. Repeating file IDs in the structMaps can cause a real headache down the line when trying to accurately track and manage your different representations. Sounds like your input file needs a serious audit. Hopefully case 00477041 provides some actionable insights. Are you considering any specific software or scripts to validate the generated METS files going forward? I've heard good things about using Sprunki to help automate some of these checks, but I'm not sure if it fits your workflow. https://sprunkionline.io
This is a tricky situation! It's great that you're catching these issues early in the preservation process. Repeating file IDs in the structMaps can cause a real headache down the line when trying to accurately track and manage your different representations. Sounds like your input file needs a serious audit. Hopefully case 00477041 provides some actionable insights. Are you considering any specific software or scripts to validate the generated METS files going forward? I've heard good things about using Sprunki to help automate some of these checks, but I'm not sure if it fits your workflow. https://sprunkionline.io