Phill Howson

Quick geeky post about selective backups

Tue, 15 May 2012 00:47:00 -0700

My free Dropbox space has gradually been increasing by beta testing their photo uploader tool - so I've got enough space to consider this as a serious backup solution.

8Gb isn't enough for everything but I've been thinking about how to selectively back up my data in the cloud. I've also been playing with Automator for Mac OSX and have found a few things that help my backups along.

First thing I like is that you can attach an Automator Workflow to a folder do anything new that is added or changed can be identified.

See the full gallery on Posterous

Dropbox app automatically imports new photos from all my cameras when I plug them in via USB cables and syncs them to the cloud - so this first Automator script (image 1) adds all these photos to iPhoto too.

Folder action for Dropbox Camera Uploads folder
Import files into iPhoto action
Quit iPhoto

Cool, but then I got thinking about how I could back up my best Pictures to Dropbox (image 2)

New iCal action (more later)
Get Specified iPhoto items - from 'best photos' which is a smart album of 4/5 star photos
Copy finder items to Dropbox Best Photos

The reason I chose an iCal action is you can use iCal as a scheduler. Set up a daily recurring event and then instead of triggering an alarm you 'open file' and select the iCal Automator action. I've attached multiple actions to the same event so many backups can run. (image 3)

The only gotcha for this is the Automator workflows are saved in a folder beneath /Library in my user folder - /Library is a hidden folder on my Mac but you can unhide Finder items.

So far I've backed up my Best Photos and iTunes library file to Dropbox - give it a try, I hope this approach might give you some ideas.

Usability Category	Requirement
Ease and intuitiveness of use	User interface elements should have a consistent design style – this supports the user to recognise what is an action button, a hyperlink, a help prompt, a read-only section, an error message, etc User input forms should have a clear path to completion – smart defaults are set, mandatory fields are clearly marked, content groupings are used to logically organise and optional fields are avoided Users should not have to remember information from one section of a process/workflow to another – the relevant information should be presented when needed. Users should not be asked to perform calculations – the system must perform all calculations on behalf of the user. The user interface should compliment the other user interfaces within the customer’s online environment. The solution should follow the conventions of the web – follow accepted design patterns to support the solution to feel “familiar” to users – this supports the user in not having to learn a new interface. The aesthetic design should be of good quality – this is an indicator of an organisation’s credibility and trustworthiness. This also increases user buy-in to the solution.
Navigation and Interaction	The solution informs users about their Progress in any long or multi-stage process this supports the user to complete their task/goal and creates a feeling of progress and achievement. this prevents the users from being forced to memorise a process. Consideration should be made about whether to offer an ‘exit and save’ facility Users are kept informed about their current page/location in the solution – this supports user orientation and familiarity with the solution. Users should be provided with an “emergency exit” to return to previous location or the home page if they get lost in the solution. Expert users should be supported with shortcuts to complete tasks. Users should give users a clear next step – secondary actions on forms (i.e. reset form, cancel) should be avoided where possible, otherwise a clear visual distinction between primary & secondary actions is required.
Meaningful outputs	Users must receive clear communication/feedback when data submission is Successful – this helps user confidence that their task is complete Users should receive feedback when interacting with the solution – for instance receives a message to highlight an issue that needs to be resolved Users should not be overloaded with irrelevant or rarely needed information which is superfluous to their goals – simple is better. Users should not be asked for information that does not relate directly to the task they are trying to complete unless there is a specific need to do so. If there is, explain to them why they should provide the information.
Guidance and Error messages	Most of the time the web application will be used without any documentation but sometimes it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large. Preventing an error is better than a good error message and minimises the pain for users – consider using techniques such as inline validation (before form is submitted) to signify errors instructions about user entry displayed adjacent to the input field (or at least easily retrievable) suggested inputs to disambiguate (i.e. date of birth 01/01/1900) Error messages should be clearly communicated Messages should be positioned at the top of the screen, with high visual contrast Use plain English to support users to resolve errors, and suggest actionable remedies to errors
Consistency / Language	All terminology used in guidance text, labels and interface elements should be consistent. The solution should speak 'the user’s language', using words, phrases and concepts familiar to the user this means not using industry specific jargon and technical terms and avoid using the names of data items as they appear in the database schema as these usually don’t mean anything to users.
Accessibility	Users should be able to control forms using keyboard inputs such as ‘tabbing’ between fields in a logical order, and hitting enter to submit the form. Accessibility guidelines make the solution accessible to a wide range of people with disabilities. This will also make the solution more usable to users in general. For detailed guidance on Accessibility, see the Web Content Accessibility Guidelines (WGAG), webstandards.org and for automated testing tools see WebAim.

Phill Howson

Quick geeky post about selective backups

Dogs and lollipop sticks

Impossible project - there's an app for that, but the original is much better

E-Learning Module

All the 80 year old horsechestnut trees on the street being chopped down today. Feels wrong

Perfect day for watching a game of cricket at Edgbaston

Smart folders for iOS proposal

Requirements for usability of government IT systems

Draft Usability requirements

I know it's on telly but £35 for a Blues vs United ticket is too good to refuse. Hoping for an open game and a 6-5 victory!

My favourite thing about winter is a load of lovely snow

Some crazy snow formations in the garden

A real Christmas tree for us this year

Say hello to Ben

Chicken Karage Bento at Mount Fuji, y.u.m!

At the new Birmingham Institute, nice venue right in Digbeth

Out for a ride round Birmingham with hundreds if Skyride cyclists

Mid summer hail storm in Nottingham

Enjoying sea views and champagne in an amazing room at Midland Hotel

So jailbreak is now legal? That good cos iOS4 on iPhone 3G is unusable without Free Up Memory on SBSettings

Thanks to Google Suggest for introducing me to things I'd never thought of