Yeah, I wondered about this. The logic is: semantically, it makes sense to put the conversion from ``wm_uncertainty_ew`` to ``ra_err`` in the model, rather than the presentation layer, since it's clearly a property of the object. Then, for consistency, you want to do the same for ``decl_err``.

Converting from degrees to arcsec is a matter of consistency with what was there before: the rest of the codebase is predicated on the assumption that ``ra_err`` and ``decl_err`` are in arcseconds, because that's what was previously stored in the DB, but now they are in degrees. So I could check the rest of the codebase to find every conversion that previously used an error in arcesc and try to update it appropriately... or I could make a work-alike method on the model, so that the rest of the code doesn't need to change.