You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For context, please see this issue on the "dbmdz/mirador-plugins" repository.
Currently, if an implementer supplies physical dimension metadata according to schemes 3) or 4) (i.e., embedded in or referenced by info.json), that PhysicalRuler plugin breaks. The problem is that once the info.json metadata is fetched, it is thrown away when the callback returns. In order to support the physical ruler plugin move towards complete spec compliance, the metadata should be made available as a property on the ImageView object. So, inside that callback function, do something like
This ticket is being closed as part of the Mirador 3 issues review. We encourage all Mirador 2 implementers to try out Mirador 3 and leave feedback in new tickets.
For context, please see this issue on the "dbmdz/mirador-plugins" repository.
Currently, if an implementer supplies physical dimension metadata according to schemes 3) or 4) (i.e., embedded in or referenced by
info.json
), that PhysicalRuler plugin breaks. The problem is that once the info.json metadata is fetched, it is thrown away when the callback returns. In order to support the physical ruler plugin move towards complete spec compliance, the metadata should be made available as a property on theImageView
object. So, inside that callback function, do something likeThe text was updated successfully, but these errors were encountered: