Changes between Version 6 and Version 7 of UseCasesResources

Timestamp:

01/31/11 17:32:47 (3 years ago)

Author:

kindly

Comment:

--

UseCasesResources

@@ -9 +9 @@
 
 
- * Data should be able to be grouped same file of different formats, so you do not get duplicates 
+ * Data should be able to be grouped for the same information in different formats, so you do not get duplicated data. 
 
  * There needs to be a mechanism to timeseries 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.
@@ -17 +17 @@
  * There needs to more information stored against the data, beyond just its format and a description.
 
- * Users should be able to refashion the data and post a whole new set of this refashioned data.
+ * Users should be able to refashion the data and post a whole new set of this derived data.
 
  * Groups of data should be able to be synced across packages/instances.  In order for derived data set to be associated with existing packages.
@@ -23 +23 @@
  * When new versions of the data arrive it should be easy to copy an old one and change versions/dates as required.
 
- * A user may want to upload a resource separately from the package and decide later on where its the best place for it is.
+ * A user may want to upload a resource separately from the package and decide later on where the best place for it is.
 
- * We need time-to-release data. 
+ * A place to put a time-to-release date against a piece of potential data. 
 
  * We need a marker to show that the certain data sets are missing.
 
- * Dashboard of what data has been released, and is going to be released.
+ * Dashboard of what data has been released, when is going to be released.
 
 ''' Possible solutions '''