[Bugs] #1591 UNSP: Make keep value retrieval in Journal more robust

[Sugar Labs Bugs]

#1591: Make keep value retrieval in Journal more robust
------------------------------------------+---------------------------------
    Reporter:  sayamindu                  |          Owner:  alsroot                    
        Type:  defect                     |         Status:  assigned                   
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:  r!                         
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------

Comment(by sascha_silbe):

 Replying to [comment:3 alsroot]:
 > oops, sorry
 >
 > what about making such checks(and #1590) on ds level(could be also in
 place where shell writes ds entries, but I guess ds is enough) and do not
 place check code to intermediate code?
 I would prefer the data store to stay as generic and metadata-agnostic as
 possible and let the UI handle unexpected data. It should also be in the
 read path, not the write one to provide robustness in cases of filesystem
 (or hardware) failures and misbehaving DS clients (i.e. activities), as
 has been argued on some other ticket as well.

 We might decide to store special entries for the actions view (this has
 been discussed on the ML several months ago IIRC), so I'd prefer the
 generic data store access code to not enforce a certain set of properties
 to be present. Besides, there is no single place were this could be done
 (see #1197, #1198).

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1591#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system