Difference between revisions of "Talk:Multilingual files uploader"

From PKP Wiki
Jump to: navigation, search
(Enter comments already made via email)
(Removed multilingual proposal comments and add revision to the proposal)
 
(4 intermediate revisions by one user not shown)
Line 3: Line 3:
 
Some ideas for multilingual file uploads:
 
Some ideas for multilingual file uploads:
 
1 - Use a modal for all multilingual file uploads. Have each possible language appear as a tab within the modal.
 
1 - Use a modal for all multilingual file uploads. Have each possible language appear as a tab within the modal.
 +
 
2 - Use a minimalist upload tool (less real estate) instead of plupload and use the same popover approach as we use for other multilingual inputs.
 
2 - Use a minimalist upload tool (less real estate) instead of plupload and use the same popover approach as we use for other multilingual inputs.
3 - Use the batch upload capabilities of plupload and then add a subsequent interface to associate images with languages. (OK, just for the sake of a 3rd option.)
 
  
 +
3 - Use the batch upload capabilities of plupload and then add a subsequent interface to associate images with languages.
  
Comments from Juan about Alec's ideas:
+
Comments from Juan:
  
 
1 - This will get clunky, I think.  
 
1 - This will get clunky, I think.  
 
2 - This would be my preferred approach, but we need to identify a good widget. I suggest this is a good time to scour the internet for alternatives to plupload.
 
2 - This would be my preferred approach, but we need to identify a good widget. I suggest this is a good time to scour the internet for alternatives to plupload.
 
3 - This one is likely significantly more complicated and problematic from the implementation point of view.
 
3 - This one is likely significantly more complicated and problematic from the implementation point of view.
 +
 +
Comments from Jason:
 +
 +
3 - How would that work?  If a user is uploading a directory full of files, they're going to need to edit each one either during that process or afterwards, in order to add metadata.  In the former case, its not really batch.  In the latter, we're allowing files to exist at least temporarily with no metadata assigned to them other than what we can glean during upload.
 +
 +
----
 +
 +
Discussions below consider option 2 only.
 +
--[[User:Beghelli|Beghelli]] ([[User talk:Beghelli|talk]]) 10:13, 5 July 2013 (PDT)
 +
 +
----
 +
 +
 +
[http://pkp.sfu.ca/wiki/index.php?title=Multilingual_files_uploader&oldid=3595 Comment's revision]
 +
 +
From Alec about the other file types widget mode:
 +
 +
We don't have a good pattern for the following common set of elements:
 +
 +
1 - File upload field/widget to replace existing file, or upload initial version if creating new content
 +
 +
2 - Link or preview to allow download of current version, if any
 +
 +
3 - Indication of data re: existing file (name, MIME type, size...)
 +
 +
4 - Delete action, for situations where the file upload is optional (e.g. issue covers)
 +
 +
The differences between image uploads and non-image uploads are...
 +
5 - Image uploads need to present an "alt text" field
 +
 +
6 - Image uploads can contain image previews, potentially with a download link; other types just have a download link
 +
 +
There is enough overlap here that there's still a good case for a single widget to handle both.
 +
--[[User:Beghelli|Beghelli]] ([[User talk:Beghelli|talk]]) 09:57, 5 July 2013 (PDT)
 +
 +
 +
----
 +
 +
 +
Related to Alec's last comments:
 +
 +
1 - The replace action can be added to this widget. If user clicks on it, then it has just to upload a file, the other extra information about the file will remain (alternate text, for example). Initial file upload can be done by clicking into the upload action. I will create more images to show this.
 +
 +
2 - User can download the file by clicking on the filename (it's a link) or clicking on the image.
 +
 +
3 - This can be accessed clicking on the info action. We can present all the information related to the file inside an information modal.
 +
 +
4 - We already have a delete action in the proposal.
 +
 +
5 - That's already covered by the proposal.
 +
 +
6 - I am not sure if we need a download link for images. I think it will only add more noise.
 +
--[[User:Beghelli|Beghelli]] ([[User talk:Beghelli|talk]]) 10:13, 5 July 2013 (PDT)
 +
 +
 +
----
 +
 +
[http://pkp.sfu.ca/wiki/index.php?title=Multilingual_files_uploader&oldid=3834 Proposal revision]
 +
 +
Added propose to use grids with multilingual rows.
 +
 +
--[[User:Beghelli|Beghelli]] ([[User talk:Beghelli|talk]]) 07:13, 8 July 2013 (PDT)

Latest revision as of 11:19, 29 July 2013

Ideas from Alec:

Some ideas for multilingual file uploads: 1 - Use a modal for all multilingual file uploads. Have each possible language appear as a tab within the modal.

2 - Use a minimalist upload tool (less real estate) instead of plupload and use the same popover approach as we use for other multilingual inputs.

3 - Use the batch upload capabilities of plupload and then add a subsequent interface to associate images with languages.

Comments from Juan:

1 - This will get clunky, I think. 2 - This would be my preferred approach, but we need to identify a good widget. I suggest this is a good time to scour the internet for alternatives to plupload. 3 - This one is likely significantly more complicated and problematic from the implementation point of view.

Comments from Jason:

3 - How would that work? If a user is uploading a directory full of files, they're going to need to edit each one either during that process or afterwards, in order to add metadata. In the former case, its not really batch. In the latter, we're allowing files to exist at least temporarily with no metadata assigned to them other than what we can glean during upload.


Discussions below consider option 2 only. --Beghelli (talk) 10:13, 5 July 2013 (PDT)



Comment's revision

From Alec about the other file types widget mode:

We don't have a good pattern for the following common set of elements:

1 - File upload field/widget to replace existing file, or upload initial version if creating new content

2 - Link or preview to allow download of current version, if any

3 - Indication of data re: existing file (name, MIME type, size...)

4 - Delete action, for situations where the file upload is optional (e.g. issue covers)

The differences between image uploads and non-image uploads are... 5 - Image uploads need to present an "alt text" field

6 - Image uploads can contain image previews, potentially with a download link; other types just have a download link

There is enough overlap here that there's still a good case for a single widget to handle both. --Beghelli (talk) 09:57, 5 July 2013 (PDT)




Related to Alec's last comments:

1 - The replace action can be added to this widget. If user clicks on it, then it has just to upload a file, the other extra information about the file will remain (alternate text, for example). Initial file upload can be done by clicking into the upload action. I will create more images to show this.

2 - User can download the file by clicking on the filename (it's a link) or clicking on the image.

3 - This can be accessed clicking on the info action. We can present all the information related to the file inside an information modal.

4 - We already have a delete action in the proposal.

5 - That's already covered by the proposal.

6 - I am not sure if we need a download link for images. I think it will only add more noise. --Beghelli (talk) 10:13, 5 July 2013 (PDT)



Proposal revision

Added propose to use grids with multilingual rows.

--Beghelli (talk) 07:13, 8 July 2013 (PDT)