Closed cjhendrix closed 9 years ago
@cjhendrix Im happy with the solution suggested !
Until this is fixed we may want to make the resource format a required field, since it is not being generated automatically from the file name.
@cjhendrix the process will be:
Caveat: The name of the resource might not be exactly the same as the file that the user would download. Currently CKAN removes characters like '-', '_' and others from the filename stored in db.
I like the approach. Pinging @yumiendo in case there are design changes to make.
CKAN renaming the files is a bit problematic. OCHA has been pushing a standard file naming convention (primarily for the COD/FODs) for years and this will break that. I think we can live with it for now. But how deep into ckan core would we have to dig to change that. And why did they do that? Seems unecessary. Just to make the URLs nicer?
Dev team may already be looking at this, but we need to consider how the name field behaves in 2.3. Before, once the file was uploaded, the file name would be used for the resource name. Now, this isn't happening (because the actual upload doesn't happen until the form is submitted).
For consistency most existing resources, I'd suggest we capture the file name and populate the resource name field when the file is selected. Tagging @amcguire62 @yumiendo for opinions/approval.