Turn on datetime validation for known types

[mjgiarlo]

Now that we have a datetime validator in cocina-models, we want to turn it on once the related datetime reports in dor-services-app all run clean. Once they run clean, this issue will no longer be blocked and will be ready to work on.

• [x] Make changes to the datetime validator that were made on the report side (covered by tests)
  • [x] Update the W3CDTF regex to /\A\d{4}(-0[1-9]|-1[0-2])?\Z/
  • [x] Allow EDTF failures matching /\AY-?\d{5,}\Z/ to be considered valid
• [x] Add to validators list
• [x] Test validation changes

[ndushay]

We are officially taking Andrew out of this loop at his request; @arcadiafalcone - you are now the PO for this ticket; you can talk to infrateam devs, esp. Mike and Naomi about how to take this forward.

How to update the Catalhoyuk dates (144k objects) remains tricky but we can figure this out. We will let Andrew know how we will proceed and when it will happen.

[arcadiafalcone]

Thanks. We're down to just a few non-Catalhoyuk invalid dates which have to go through ArcGIS. I can manually remove the encoding from the MODS if those are still being worked on once Catalhoyuk is sorted out. For Catalhoyuk, we are not changing the values, just removing encoding: "w3cdtf" from the dates, per consultation with Claudia.

[ndushay]

So ... is there an action for someone to take re: converting Catalhoyuk records? Who will undertake the action(s)?

[mjgiarlo]

@ndushay I think the question @sul-dlss/infrastructure-team has to resolve is: what is the best way to remediate metadata for ~144K items? And then we can work with @arcadiafalcone on the resolution.

[arcadiafalcone]

@ndushay @mjgiarlo Is there a ticket for the Catalhoyuk work / should I make one?

[mjgiarlo]

@arcadiafalcone I don't believe there is one. Sure, please do, and we'll make sure to prioritize it and get it in front of the team.

[arcadiafalcone]

Blocked by #496.