DCAT-US Validator Feature: Load File

[jbrown-xentity]

User Story

In order to validate a locally stored DCAT-US file, data.gov admins want the dcat-us validator to be able to accept an uploaded file.

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• GIVEN a DCAT-US provider has a dcat-us file
  WHEN the file is loaded into the DCAT-US validator
  THEN a report is generated on the validity of the DCAT-US file

Background

#3503 (comment)
https://dashboard.data.gov/validate compared to https://catalog.data.gov/dcat-us/validator

Security Considerations (required)

Need to take care with anything loaded by the public, but nothing is "executed" or "evaluated" other than as strings against previously defined regex. This should be a no-op.

Sketch

Not sure at this point, we don't have current examples of this kind of work.

[jbrown-xentity]

I cannot tell how often this is used via New Relic logs, but I do know that there were 70K requests to validate a DCAT-US file at a public URL for September (search gsa-datagov.prod.dashboard validate datajson_url in New Relic) versus 11,590 requests to validate a DCAT-US file with either raw JSON or loading a file (search gsa-datagov.prod.dashboard validate POST -datajson_url).
So the feature requested above represents < 14% (say half, roughly 7%) of the total validator usage on dashboard.