Rule system for ADO to Type Mapping (or maybe an ADO Rule system in general)

[DiegoPino]

What?

Even if we would love that users would be way more concrete about what media they put into their objects, we have to realize that sometimes a simple ADO Type, e.g DigitalDocument to a single "View Mode", e.g Digital Object with Mirador Viewer, might not be sufficient to cover the variations and needs of a particular Object.

In my dream world people would use more Types to differentiate what is what, but we, as a project can understand and see that even if that "should be done" (looking at you folks) there will be always edge cases like "Book" where a large PDF might need to use PDF.js, a medium PDF might use Mirador and a compounded one will have a different IIIF Endpoint need.

So. The Rule system.

User interface, select and checkboxes will allow users to create a simple UX friendly Rule. Stating
"If Digital Object AND has_only PDF AND SOMETHING ELSE" use X View MODE with MIRADOR"
"If Digital Object COLLECTION AND has_NOT PDF AND SOMETHING ELSE" use View MODE with MIRADOR 4"
"default" Use Y Video MODE

Rules will be made of CONDITIONS -> RESULT
Rules can be used in the ADO Type to View Mode Settings as an additional option to a "pure" view Mode (no deprecation)

UI/UX hints for admins will be added to every user with edit capacity will be able to see WHY mirador is being shown instead of PDF.js. etc.

Thanks

[DiegoPino]

Postponing. I am a bit concerned about D11 and performance on this one (code does work, I just feel it does a LOT of processing)
Same can be achieved already with JMESPATH conditions (and good docs?) so not sure yet we will need it directly