[jira] Updated: (PHOTARK-66) Improve the album storage structure in photark (trunk) local jcr

["Subash Chaturanga (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOTARK-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Subash Chaturanga updated PHOTARK-66:
-------------------------------------

    Attachment: changedJCRStructureUpdate_1.patch

A new JCRAlbumAggregator class added to photark-jcr and build successfully. Please try this patch and inform what need to be improved or any pros or cons of this patch. 

> Improve the album storage structure in photark (trunk) local jcr
> ----------------------------------------------------------------
>
>                 Key: PHOTARK-66
>                 URL: https://issues.apache.org/jira/browse/PHOTARK-66
>             Project: PhotArk
>          Issue Type: Improvement
>         Environment: Linux
>            Reporter: Subash Chaturanga
>         Attachments: changedJCRStructure.patch, changedJCRStructureUpdate_1.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Currently in photark trunk, all albums are directly put under the root of local jcr regardless of the album type. Currently photark has basically two main album types, local and remote (flicker and picasa). So If the local jcr structure is much more organized in trunk such that it stores each album type under the relevant category. Hence  in future when some more other album types introduces it won't be too complex in the jcr level also. And it is efficient and fast, when we do jcr operations where we don't need to go through the whole album list each time, when we want to acquire all albums of one particular type.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.