Decapod 0.7 Planning

Decapod 0.7 "final release" features

Decapod's Three Servers

1. capture and calibration server
2. dewarp server
3. export server (already exists)
   • should be separate instances so they can run independently or simultaneously
   • should be able to run all the servers on the same machine
     • need a better way to access via url (not just localhost:8080)

Iteration 1 (Sep 10 - Oct 5)

Notes
Develop capture server with basic UI

• single camera capture
• dual camera capture (simultaneous)
• error handling
  • can't detect supported cameras
  • mismatched supported cameras
  • etc.
• Image Storage
  • naming scheme (capture001_1.jpeg)
  • caputure001 can be configurable as long as it's unique to a pair.
  • _1 is required for stereo capture to indicate image pairs.
  • the image format may vary
• Image + calibration info export
  • zip file (possibly with a custom extension like .deca)

Iteration 2 (Oct 9 - Oct 19)

Oct 8 is Thanksgiving holiday in Canada.

Iteration 3 (Oct 22 - Nov 2)

Notes

Stereo dewarp server development

• consume capture archive
• single file upload (only 1 capture archive)
• export zip containing all the dewarped images
• image naming scheme (capture001_left.jpeg, capture001_right.jpeg)
  • capture001 can be configurable as long as it's unique to a pair
  • _left, _right are required to distinguish the left and right pages of a spread
  • the image format may vary
• error handling
  • missing images (i.e. the images aren't paired)
  • invalid calibration data
  • etc.

Iteration 4 (Nov 5 - Nov 16)

• 10 business days available
• 22 single person days development
• 5 single person days days design

Alternatives:

1. Add more developers
2. Become more efficient (do more in less time)
3. Work longer

Notes

Export

• genpdf needs to report fallbacks (i.e. type4 -> type3)
  • could change the "done" stage to the type of export type#
• upgrade to ocropus 0.6

Notes
Export

• code cleanup
• bug fixes
• error handling
  • import errors
  • server errors

Iteration 5 (Nov 19 - Nov 30)

Release, documentation, report writing.

Future Consideration

DECA-198@JIRA Create a Decapod installer that only downloads and installs the required dependencies
DECA-197@JIRA Create a standalone Decapod installer capable of being distributed without Internet connectivity
DECA-296@JIRA Design and implement OCR text file download
DECA-323@JIRA genpdf needs to report fallbacks
DECA-287@JIRA genpdf omits large sections of human-readable text when generating Type 3 or 4 PDF
DECA-211@JIRA Generating a pdf from certain png or jpeg files will produce an colour inverted image in the pdf
DECA-188@JIRA Type 2 output quality is poor for well photographed and scanned documents
DECA-58@JIRA Export to PDF skips over pages that do not have detected characters
DECA-307@JIRA 99MB tiff file fails at TIFF conversion
DECA-306@JIRA 100MB file fails during upload (POST)
DECA-168@JIRA Implement client side filter of imported images
DECA-289@JIRA "Browse File" button is not a string in exporter.js
DECA-241@JIRA The server returns URLs that are relative to the server root, but doesn't include the server's domain
DECA-299@JIRA Orca screen reader re-reads disabled form fields just prior to Export process
DECA-119@JIRA The user should be able to recalibrate the cameras
DECA-295@JIRA The colour setting is missing from genpdf
DECA-286@JIRA Add JPEG export support to the server
DECA-212@JIRA Implement the Library, Book, and Page models
DECA-210@JIRA Configure a server that can automate testing of genpdf and Decapod
DECA-204@JIRA Create a design to allow the input of Metadata
DECA-24@JIRA Port decapod server from CherryPy to Kettle
DECA-205@JIRA Save metadata to plain text file during export
DECA-203@JIRA Research DPI calculation and its usefulness in Decapod
DECA-93@JIRA Add ability to show current version of Decapod components
DECA-293@JIRA UI colour swatch changes with selection
DECA-292@JIRA Unit selector for UI
DECA-326@JIRA Combine utils.server.getURL and resourcesource.url
DECA-305@JIRA The positioning for the output is slightly off from the custom output settings and the Start export button

• configuration ui
  • UI config
    • strings
    • size limits
      • needs validation
    • units? may not have time for this. If implemented should limit the options with a select box or similar
    • timing delays (e.g. unresponsive cameras, server polls)
      • needs validation
  • Server config
    • text area where the user can freely modify the config file
    • need to back up original config
  • If the user configuration causes errors (e.g. the server won't start), the user will have to manually recover.