• Reports work as a separate parcel now using Phil's quickentry patch.
• Improved test suite.
  • Needs to be extended further
  • segmentation fault by the end of the test suite run - Investigate and talk to Andi
• Unclear points about work with repository clarified.
  • by using store.getCommit() information about timestamp of a version of a view or an item can be retrieved
  • Deleted items are returned as stale, and accessing any attributes in them raises Stale Item Error - Talk to Andi, perhaps it is possible to create a readOnly item in such cases instead
  • For items that createdOn is earlier than the date when they were first received. There is no attribute that stores information on date received, but there is dateSent
• view.itsVersion = -1 causes Chandler to freeze - Talk to Andi about this matter
• version goes up after triageStatus change? - _yes, but only if "Triage" button is pushed by the user. Occassional, or sequential clicks may be not recorded.
• report command parsing is complete. Description of available commands in ReportAsAParcel

Next Week

• Make the Reports parcel fully independent by updating the quickentry point in the Chandler-ReportPlugin setup.py, and not in chandler/setup.py
  • make the code public in http://code.google.com/hosting/createProject
• Discuss presentation about the reports project to OSAF. How? When?
  • play with recording scripts in chandler for that purpose.
• Turn Report into a Stamp
  • use the information from Ed
• Stale Item Error
  • use a dictionary with attributes from the stale items to store.
• Implement reports for non-trivial cases, that require historical information from the repository.
  • Example: items that were LATER at start time, then NOW, and LATER again by the end of report time are not supposed to be in transition out.

-- VeraSheinman - 20 Jul 2007