search

midas-isg / digital-commons

The MIDAS Digital Commons
http://epimodels.org/apps/mdc
GNU General Public License v3.0
2 stars 1 forks source link

Eliminate use of NA, or N/A to describe dataInputFormats and dataOutputFormats #273

Closed JohnLevander closed 5 years ago

JohnLevander commented 5 years ago

We use NA to either mean "not applicable" or "not available" this is not precise enough.

When we use NA to mean "not applicable" (as in there is no value for this field) we should say "None." For example if there is software that does not accept an input, we should set the value of this field to be "None."

When we use NA to mean "not available" that means we don't know the input type for some reason. We should replace this usage of NA with "Syntax Not Available."

jeffstazer commented 5 years ago

The data shows ZERO entries with NA or N/A for dataInputFormats. The data shows THREE entries with N/A for dataOutputFormats; none contain NA.

Epi-Data API VirFinder VirHostMatcher

jeffstazer commented 5 years ago

We are transferring the contents of dataOutputFormats into outputs->dataFormats (Update Software XSD to increase clarity of input/output data formats). dataOutputFormats containing N/A were not transferred. As we convert to using outputs instead of dataOutputFormats the contents of these 3 with N/A will disappear.

jeffstazer commented 5 years ago

If no data has been entered (meaning dataInputFormats or dataOutputFormats doens't exist in the json, in the commons.js file at line 680 we were inserting 'N/A'. Changed this to 'Syntax Not Available.'.

So I now believe the 3 entry's above should have 'None'.

jeffstazer commented 5 years ago

Updated

Epi-Data API VirFinder VirHostMatcher

to have None as an Output