Changes between Version 3 and Version 4 of UseCasesResources


Ignore:
Timestamp:
01/31/11 13:51:54 (3 years ago)
Author:
kindly
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • UseCasesResources

    v3 v4  
    1111 * Data should be able to be grouped by various different factors (type, date). 
    1212 
    13  * There needs to be a mechanism to timeline information the user puts in, so that search results only display the latest package. This needs to be done in a way that the older data is still easily accessible. This should be done with the minimum of user effort. 
     13 * There needs to be a mechanism to timeline data, so that search results only display the latest package. This needs to be done in a way that the older data is still easily accessible. This should be done with the minimum of user effort. 
    1414 
    1515 * The ordering of the data should be presented without the need for user input. 
    … …  
    2121 * Groups of data should be able to be synced across packages/instances. 
    2222 
    23  * When new versions of the data arrive it should be easy to copy an old one and change versions as required. 
     23 * When new versions of the data arrive it should be easy to copy an old one and change versions/dates as required. 
    2424 
    2525 * A user may want to upload a resource separately from the package and decide later on where its the best place for it is. 
     26 
     27''' Possible solutions ''' 
     28 
     29 1 Make the data model for resources richer.  The suggested model would be      
     30{{{ 
     31Package  <m2m>  data_group <o2m> data <o2m>  resource 
     32}}} 
     33data_group now becomes a first class entity. 
     34 
     35The data group would be a holder for a timeseries of "data" 
     36 
     37Each bit of data can have many resources of different types. 
     38 
     39 2. Improve package relationships.  This will involve giving package relationships more informations such as the date of the relationship in order to make a time series. (this date information could also be against the package) 
     40 
     41 3. Add a package group table.  All current packages get a package_group and then we will have a way to add packages in a time-line.  Packages will have time series data information. 
     42