- Updated the warning message.

- Updated warning message per feedback.

- Updated notification of malformed metadata file upload per feedback.

Tested with json, yaml, and xml files. Errors caught and displayed if there was a syntax error, e.g., missing colon in yaml file.

Errors in naming conventions (e.g., "units" instead of "unit") were not caught. It would be helpful to add in checks for these. Specifically:

1) If the value for "type" is not "integer," "double," "text," "radio", "select," or "checkbox," throw an error.

2) Throw an error if "value" and "type" are not provided

3) Give a warning if anything other than "value," "type", or "unit" are listed for a parameter, e.g., Non-conventional term "X" was defined for the parameter A

Also, please update existing messages:

1) If error encountered, first state "Check metadata files." followed by error message. If possible, include folder name, e.g., "Check metadata file in folder X".

2) Instead of saying "No errors encountered during import." say "Import completed." We don't check for all possible errors, so we don't want to let user get that potentially false reassurance.

To make this work properly will take a bit of work. For now please update the instructions to indicate that spaces are allowed. Also, remove display of Import Status. Change this task status back to "Accepted"

1) Confirmed that import status is updated
2) However, basic errors are not being caught by the system. See examples below.
o No error appears when formatting is off, e.g., in the following:
overground_walking_speed:
type: double
unit: meters/seconds
value: 1.28
However, this parameter doesn’t show up in the query which seems to imply that there were issues with the indexing.
o If multiple values are assigned to a given parameter, indexer only registers first value assigned to parameter. No error message appears.
o When does parameter type matter? When I put in a mismatch between value and value type, no error appears. In some cases, the query still works and in some it doesn’t.

3) It seems like parameter names can have spaces. Please confirm if this is the case. If so, update instructions in https://simtkdata-stage-hk.stanford.edu/apps/import/metadata.php by removing text “Parameter names cannot have spaces and…”
4) Date-stamp
o Wrong date-stamp on import status. Import at 2:34 PM. Status message says 14:17:52.
o Add time zone to date- stamp