Government Websites I Can Upload Files to
@gavinwye commented on 31 January 2017
#Drag and drop file upload#
Select file - file upload
Other links
GOV.UK elements: http://govuk-elements.herokuapp.com/course-elements/#grade-file-upload
@elizabethbartram commented on iii February 2017
@gavinwye commented on 4 May 2017
New screenshots of the employment intermediaries service provided by @stevenaproctor
@jennifer-hodgson commented on 29 Jan 2018
Following our discussions in the working group last week - is file upload (and file download), in fact, a service pattern rather than a pattern?
@adamliptrot-oc commented on 29 Jan 2018
@jennifer-hodgson my view is that if the component parts can be extracted into re-usable patterns, that is fine and those can be documented. There is besides a departure in requirements between multiple file upload and single file upload.
@jennifer-hodgson commented on 29 January 2018
Thanks for this @adamliptrot-oc. Service patterns are reusable too (they currently exist on a separate backlog, we're discussing how to about usefully business firm them and make them visible). It seemed to a few of us on the WG call, if I remember correctly, that this was a more complex, multi-pace process fulfilling a task which stands as a service pattern. That doesn't preclude, of class, its constituent parts existence broken downwardly into useful components and patterns.
@JamesPBoyle commented on 29 January 2018
Tin I claw you guys into #consequence-upscan? UpScan is going to replace File-Upload-as-a-Service. Nosotros are still in the process of edifice the service, but it would exist useful to make sure the design is consistent with the capabilities of the backend organisation
@adamliptrot-oc commented on 29 Jan 2018
@jennifer-hodgson yep, I raised that, just keen not to rule out the gamble for other services to benefit from the findings of a service congenital purely to handle this blazon of interaction. Other services look to be finding their own solutions (outside of a service-based one) then it would be useful to detect some common basis between them and document a pattern.
@jennifer-hodgson commented on 29 Jan 2018
Thanks for that, @JamesPBoyle, yeah that would exist useful. I wonder is this also of interest to @benwakefield?
And thanks for your comments also, @adamliptrot-oc. I call back yous raise an interesting issue almost the relationships between components, design patterns and service patterns, and how to organise and brandish them within the design system in such a way that everyone who needs a sure thing can discover it. Peradventure we could discuss this broader outcome at the next working group, @stevenaproctor?
@stevenaproctor commented on 29 January 2018
@jennifer-hodgson It is definitely something that needs to be discussed, especially because technical reasons may mean a service-design pattern cannot be implemented every bit designed. Besides, in that location could exist conflicting user enquiry from different services.
@lfritzsche commented on 8 February
Large file upload with elevate and drop and progress bar
@lfritzsche commented on eight Feb 2018
Description
This pattern allows users to upload large files to HMRC and understand its status, before during and after transfer.
Draw when to use this pattern/component
Is it a blueprint or component?
Blueprint as it uses a combination of different components
What demand does it help you meet?
Allows users to securely send big files to the intended recipient with a record of what happened.
When is it appropriate to use?
When there is a need to send documents to a user where alternatives such equally email are not appropriate. Non tested with users who upload lots (due east.yard. 20+ files daily) of small files
@lfritzsche commented on 8 Feb 2018
How information technology works
Total description
This upload design has been designed to handle the secure transfer of large files from third parties and other government departments to HMRC. It is different to File Upload As A Service (FUUAS) as there are few restrictions on the type and size of files for intended transfer.
Users tin send individual files up to the size of 10GB and any format, excluding executable files (.exe). The pattern allows users to select either private or multiple files at a time via the principal CTA or elevate and drop. Once the user has selected the files they wish to upload, there is the opportunity for them to remove (if any take been selected in fault) or add together new files. Basic checks to ensure selected files are not over 10GB individually or .exe format are washed in the backend get-go and then that nosotros can provide appropriate erroring. This allows users to correct any issues with file size and also to mitigate files sent in error.
Errors accept been dealt with in a unique way and crave further testing from an accessibility and usability perspective within Private Beta. Users must prepare the issue earlier they tin can go along to upload by removing the file selected with the effect. This allows users to record the file with the upshot in case they need to investigate further.
The error box at the pinnacle of the screen allows users to remove all files with issues, however this may cause usability issues for users with screen readers as they are unable to link to the individual files. They can then continue to upload, which will and then launch the uploading functionality.
Uploads in progress is a new component which uses a progress bar in addition to a percentage indicator with the opportunity to abolish any in flight uploads. If users send files that are larger than average, we establish that it was important to give the user more visual feedback for the stats of that upload. A like erroring pattern is used for files with connectedness errors as previously described. If any errors occur, the user is still able to proceed with the successful files.
Coded examples
Speak to David Birchall.
Why it works
This pattern works because it is a single page awarding that gives dynamic inline mistake messaging when something goes incorrect, giving user feedback as to the progress of the upload and individual file control at all stages of the upload process. User research has establish that users notice this pattern piece of cake to follow with minimal errors encountered.
@lfritzsche commented on viii Feb 2018
Research on this pattern
SDES has just moved into Private Beta from January 29th 2018. Further research is required to understand how users deal with the transfer of large files (2GB and upwards)
All Alpha inquiry is available in confluence.
Feature specific enquiry summary:
Real time feedback such as fault messages and condition (failed, cancelled, complete) -
Dynamic components - The upload journey uses a single page which uses JS to dynamically modify components based on the scenario. This tested very well with users and they found the additional info, inline errors and individual control very intuitive. Further testing is required for large batches of files uploaded at one time.
User control earlier and during upload - This tested well in alpha, although users didn't accept actual reasons to abolish and retry as they were using dummy files with the prototype. More than extensive contextual research is required in Private Beta.
Multi file uploads - Most of our users selected unmarried files to upload. Multi file uploads were useful for those uploading on behalf of their organisation, withal within that grouping only those with a higher technical proficiency used the drag and drib functionality. This is why the pattern reflects elevate and drop every bit a secondary action.
10GB per individual files - this needs to be extensively tested via contextual research within Private beta. The paradigm and the machines nosotros tested on were super efficient and potentially don't give an authentic reflection of the time it actually takes to upload files. Best practice stipulates around 1GB per file for efficient browser uploading.
Source: https://github.com/alphagov/govuk-design-system-backlog/issues/49
0 Response to "Government Websites I Can Upload Files to"
Post a Comment