Changes between Version 4 and Version 5 of Ticket #1574


Ignore:
Timestamp:
01/06/12 10:53:50 (2 years ago)
Author:
ross
Comment:

Some issues to be addressed

  • What about existing content stored on google/s3?
  • Metadata for OFS should use username/userid? If user changes username we could just change the pairtree metadata json file, it should not be automated or easy for users to change username though.
  • OFS Metadata should contain the form data from CKAN upload
  • Remove _owner from OFS metadata (unnecessary)

Some issues to still consider

  • Allow .sqlite upload?
  • Allow .sql upload?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1574 – Description

    v4 v5  
    773. The archiver's update task will check configuration to determine if it should upload some mime-types (tabular formats) to webstore. Configuration should also determine where webstore is. (see #1609) 
    88 
    9         3a. It should be stored in webstore using {username}/{resource-id} where {username} is the name of the user uploading    
    10             the original file. 
     9        3a. It should be stored in webstore using {username}/{resource-id} where {username} is the name of the user uploading the original file. 
    1110 
    12114. The archiver will continue to move the file into permanent storage as per current practice.