Thanks Tony,
It is precisely the challenge of our books (well, mostly illustrated manuscripts and photo albums) that has prompted this. Interesting to hear that you dislike the page turning style of presentation (more than slow loading!). I'm not sure that in most cases we'd want to create individual pages for each leaf/folio, but we realise that we also want people to be able to locate (and download) individual images...
Definitely food for thought, there...
Andrew
Andrew Davis, Collection Online Content Manager
Royal Collection Trust
Stable Yard House, St James's Palace, London SW1A 1DH
Subscribe to our e-Newsletter at www.royalcollection.org.uk/newsletter
The Royal Collection Trust, company no. 2713536, charity nos. 1016972 (England and Wales) and SC039772 (Scotland)
Royal Collection Enterprises Ltd, Company no. 2778486 (England and Wales)
Registered office: York House, St James's Palace, London SW1A 1BQ
-----Original Message-----
From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Tony Crockford
Sent: 13 February 2015 16:46
To: [log in to unmask]
Subject: Re: Presenting Multiple images of objects
> On 13 Feb 2015, at 16:09, Andrew Davis <[log in to unmask]> wrote:
>
> Are we missing something obvious? As always, there's budgetary constraints at work, and we need to have something that we can make available in the near future, but we'd need the solution to be scalable and ideally one that will last us for the lifetime of this iteration of our online collection.
>
> Any comments and suggestions gratefully received!
As a user I really don’t like slow loading pages with huge galleries of images and I really, really don’t like page turning presentations.
As a developer I can see why your developers might suggest limiting the number per record, but I’d be suggesting going further and presenting each record with a *single* image initially, but create a series of linked pages for every other image you have for that record (a user will only download them until they get bored - storage space is then your consideration - 450 images sounds like a whole book!
A list of links to images is one way, a link to the first image that links to the next is another. The web is good at hyperlinking and loading images, it breaks when you try and load all the images at once and display them one by one (like most javascript galleries do)
Your developer should be able to prepare html files for each image that links to the next - if you wish to add a page turning paradigm to that, just have the next and previous links at the corners…
If you keep the web simple it will be fast and enjoyable.
Just my Friday 2p worth of opinion.
:o)
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
Royal Household Legal Disclaimer - This message and any attachments should only be read by those persons to whom it is addressed and be used by them for its intended purpose. The Royal Household cannot accept liability for statements made which are clearly the sender's own and not made on behalf of the Royal Household. Replies to this email address may be subject to interception or monitoring for operational reasons or for lawful business purposes.
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|