RITE Ingestion Ignores Special Character Errors

[pauls4GE]

Background:
RITE Ingestion Ignores Special Character Errors

Acceptance Criteria:

Implementation Details:

Test Data:

[baoluomeng]

Was this caused by ingesting using the manifest file or the new functionality "upload as ingestion package"?

[chrisage]

@pauls4GE Can you provide a test case example (and expected vs actual results)?

[pauls4GE]

Is this only limited to special characters in Owl files or even in CSVs?

[saratge]

@pauls4GE we encountered this in the FAA project where the SADL files and their subsequent translation into OWL had special chars

[pauls4GE]

Does it have an issue with special characters inside csv files as well?

[saratge]

Does not seem to fail if the special char is within Ontology, but fails same character within instance data csv

Sample CSV:
description,identifier,title,definedIn_identifier,actedOnBehalfOf_identifier,dataInsertedBy_identifier
,SC-205,,�,,
,RTCA,,,,

[saratge]

It is okay to fail with � which is un-renderable and hence is displayed in that fashion.
However, instance data with special characters such as greek alphabet has no problems during ingestion but returns a question mark when executing query nodegroups.
Closing this issue as it is SemTK/RACK related
See: ge-high-assurance/RACK#994 for more information