The Stingray Reader tackles three fundamental issues in processing a file:
The problem we have is that the schema is not always bound to a given file nor is the schema clearly bound to an application program.
One goal of good software is to cope reasonably well with variability of user-supplied inputs. Providing data by spreadsheet is often the most desirable choice for users. In some cases, it’s the only acceptable choice. Since spreadsheets are tweaked manually, they may not have a simple, fixed schema or logical layout.
A workbook (the container of individual “spread sheets”) can be encoded in any of a number of physical formats: XLS, CSV, XLSX, ODS to name a few. We would like our applications to be independent of these physical formats. We’d like to focus on the logical layout.
Data supplied in the form of a workbook can suffer from numerous data quality issues. We need to be assured that a file actually conforms to a required schema.
What has been done about it?
What can we do in Python?
How can we handle various kinds of spreadsheets transparently?
Can we handle fixed-format files (those without delimiters)? If we can do that, can we handle legacy COBOL files? Can we handle EBCDIC?
Test hashable interface of Cell
(The original entry is located in /Users/slott/Documents/Projects/Stingray-3.1/source/cell.rst, line 190.)
88-level items could create boolean-valued properties as a fluency feature.
(The original entry is located in /Users/slott/Documents/Projects/Stingray-3.1/source/testing/cobol_2.rst, line 151.)
Test EXTERNAL, GLOBAL as Skipped Words, too.
(The original entry is located in /Users/slott/Documents/Projects/Stingray-3.1/source/testing/cobol_loader.rst, line 863.)