The :Project Journal“ (journal) is a new feature for the Agtek Access server. The journal will record events related to the project. This enabled applications to timeline of events related to the project. Here are some example of data items to be stored:

• Photos
• Notes
• Measure Areas
• User Tracks
• Machine Tracks
• Files added / modified

The end state of this implementation will be expressed in the following apps:

• The project summary page in the Access Web appliction
  • Web app can create summary of events directly to a new KMZ / display
• Mobile applications adding data directly to the journal.
  • Done when the local data store is uploaded

A bridge strategy will be required until mobile applications are enabled.

• The server will extract project events from saved KMZ files generated by the mobile apps.

Each data item has the following attributes:

• project link
• date-time
• User id (handle) of author
• LLA of data element.
• Reference to the data element itself (files?)
• Journal must allow for multiple entry paths per project (different clients)

Questions:

• Desktop apps to participate in project journal? How?
• Photos and Notes make sense from a standalone data perspective, what about tracks/measures?
  • What is the implemention of the backing store
• What other data elements are missing?
• Journal will archive and restore with the project
• Journal will delete when the project deletes.
• Does journal ever time out? Or kept as long as the project?