Several checks relate to machine-readability of data, whether code generated from the eml can successfully load the data. Often a human can still use the data even when those checks fail (warn status). Should portal offer a one-glance summary infographic to indicate to users if a dataset is auto-workflow-ready? Or "Programmatically Readable" (@mobb 's term).
Example: maybe the pastaProg buttons would grey-out if there are relevant warns.
Or, a visual summary of the checker report could decorate the left margin of the portal landing page, one row of color for each check, blue, green, or orange (no red since those do not upload). See whiteboard sketch below. (Although that might be all checks, not just machine readability related checks.) Note to @mobb this graphic could be generated from the checker report xml to an svg graphic.
Several checks relate to machine-readability of data, whether code generated from the eml can successfully load the data. Often a human can still use the data even when those checks fail (warn status). Should portal offer a one-glance summary infographic to indicate to users if a dataset is auto-workflow-ready? Or "Programmatically Readable" (@mobb 's term).
Example: maybe the pastaProg buttons would grey-out if there are relevant warns.
Or, a visual summary of the checker report could decorate the left margin of the portal landing page, one row of color for each check, blue, green, or orange (no red since those do not upload). See whiteboard sketch below. (Although that might be all checks, not just machine readability related checks.) Note to @mobb this graphic could be generated from the checker report xml to an svg graphic.
