iredpath / excel-data-extractor Goto Github PK

As an end user, I would like the look zone numbers displayed to correspond to the correct look zone data from the inputted sheet. Right now, look zone data is stored assuming an ascending look zone ordering. This is not always true

Dod:

• look zone number obtained from look zone title

blocked by #4

As someone reviewing the quality of the code, I would like each module to have a comprehensive set of unit tests to catch errors and improve quality.

Dod:

• all data code (FourDimArray, DataType, SheetConfiguration) has relevant testable code tested

TODO:

• refactor of FourDimArray
• ENUM for lookZone/slideMetric
• match file.remove to file.add
• right most panel functionality
• make the gui look not awful (use Teddy's layout stuff)
• implement delete on the data side (possibly rethink implementation)
  • remove from four dim array
  • rebuild list of parts
• add file name/(location)? dialog after export (do we need to enforce .xlsx?)
• add bar after export to show progress
• fix weird ordering in output (probably a hashmap thing) (should be fine now)
• move up/down for stats/subs/stims
• investigate how to change focus? weird behavior with CheckboxListItem
• figure out correct focus with file list buttons
• logically organize the GuiView class
• BUG - switching datagrouptype before uploading files stops active pane from being displayed (temp fix in place but why the fuck does this happen in the first place) THIS MIGHT BE FIXED
• buttons for (de)select all, reset order?

As an end user, I would like the ability to export an output file with all the data I am interested in. Initially, each sheet in the output book should be a statistic, with stimuli on the x-axis and subject on the y-axis

DoD:

• application writes output file as specified above

blocked by #5 and #3

Write acceptance tests for the gui by end of project.

Blocked by: Needs DoD

We have decided to add the settings folder, along with the .project and .classpath files to the .gitignore as these files are generated by Eclipse and are not always necessary.
Done when:
The above files are no longer being tracked by git

As an end-user, I would like the application to store all the relevant excel data in some internal data structure. This data will then be used to populate the output file. Should have the ability to set and get data

DoD:

• data structure implemented
• getters/setters added for data access

As a developer, I would like a quick and easy automated way to create the jar we will be shipping to our client. This jar should include all our MAIN java classes as well as the attached POI libraries. Test files and JUnit imports should not be included

DoD:

• maven profile (e.g. mvn package) produces the desired jar
• ExcelDataExtractor.java serves as the main class of the jar

As an end-user, I need the application to read in one or more excel files. These files will be in the .xlsx format. All relevant data from these files should be stored internally in the app.

DoD:

• multi-file upload supported
• only .xlsx files read
• data extracted and stored

As someone reviewing the quality of the code, I would like all the IO related code to be fully unit tested. This will help catch errors and improve code quality.

DoD:

• IO unit test suite enhanced to cover all relevant testable code

As a developer, I would like an initial project setup that is easy to access and setup locally. This should include pulling in current dependencies (POI, JUnit)

DoD:

• initial project setup complete
• initial known dependencies pulled in