Changes between Version 1 and Version 2 of Ticket #2732


Ignore:
Timestamp:
07/24/12 09:00:44 (22 months ago)
Author:
ross
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2732 – Description

    v1 v2  
    11We should simplify upload and storage of files, initially only to local storage with archiver eventually being fixed to archive data externally. WIP pad is http://ckan.okfnpad.org/uploads   
    22 
    3 _Simplifying uploads_ 
     3'''Simplifying uploads''' 
    44 
    55Currently uploads are too painful/difficult/fiddly to use and/or configure.  We want to simplify uploads so that they are done directly to the CKAN server, without support for remote services (S3 etc) and/or the dependencies it introduces. 
    … …  
    1212  
    1313  
    14 _File uploads_ 
     14'''File uploads''' 
    1515 
    1616Things file upload should do: 
    … …  
    2828    
    2929    
    30 _File storage_ 
     30'''File storage''' 
    3131 
    3232File storage should be local to the CKAN install, and not a remote service.  Any archiving to remove storage providers should be outside of the main request. 
    … …  
    4444Somewhere in the DB we should store ... 
    4545 
    46 |Column|Notes| 
    47 |id|An identifier| 
    48 |owner|The owning user, who uploaded the file| 
    49 |path|The path (from the 'storage root') to the file| 
    50 |size|The size in bytes of the file on disk| 
    51 |mimetype|The mimetype of the file, as provided by the uploader| 
    52 |upload_date|When the data was uploaded| 
    53 |resource|The ID of the resource it belongs to. A unidirectional relationship.| 
     46||Column||Notes|| 
     47||id||An identifier|| 
     48||owner||The owning user, who uploaded the file|| 
     49||path||The path (from the 'storage root') to the file|| 
     50||size||The size in bytes of the file on disk|| 
     51||mimetype||The mimetype of the file, as provided by the uploader|| 
     52||upload_date||When the data was uploaded|| 
     53||resource||The ID of the resource it belongs to. A unidirectional relationship.|| 
    5454 
    5555Generating paths should try and separate the files, perhaps based on username of the owner, or some other mechanism to avoid a single folder full of files. 
    5656 
    5757 
    58 _Notifications_ 
     58'''Notifications''' 
    5959 
    6060We need to make sure that it is possible to notify other components within the system that an upload has taken place, or at least make it easy for them to be notified.  The primary use case for this is to notify the component that will translate/upload certain formats to the data store. 
    … …  
    6363 
    6464 
    65