Mike
Here's something vaguely connected to your query, a rather good post from
Neiman Labs about the Daily Telegraph's new publishing CMS. Have a look at
the workflow diagrams and read about the way they appraised the legacy
systems. Worth thinking about when Museums replace clunky old publishing
CMS.
http://www.niemanlab.org/2016/03/how-the-telegraph-built-its-new-cms-by-focusing-on-simplicity/
One or two worrying points stand out, namely that they hadn't considered
remote access enough, and that they were still allowing some depts at the
paper to keep their old systems.
Any CMS fiends left awake might also wish to search out the various BBC R&D
blogs about web CMS they have switched on recently and Martin Belam's
Guardian posts about tagging systems.
My point? Look outside the museum world occasionally to see how others do
it.
Jon
On 31 Mar 2016 9:23 p.m., "Mike Ellis" <[log in to unmask]> wrote:
> Thanks Tony, and Robert - really useful. Robert, totally agree re
> checkboxes, I think you’re absolutely right.
>
> cheers
>
> Mike
>
> _____________________________
>
> Mike Ellis
>
> Thirty8 Digital: a small but perfectly formed digital agency:
> http://thirty8.co.uk
>
> * My book: http://heritageweb.co.uk *
> * New: Workshops, courses and free downloads:
> http://trainingdigital.co.uk/ *
>
> On 30 March 2016 at 17:23:27, Tony Harris ([log in to unmask])
> wrote:
>
> Hi Mike, I don't have a very long list, but our new CMS has the following,
> a fully featured IPTC ready DAMS and workflow capabilities for new displays
> and loans etc. Both are new departures for us.
> Regards
> Tony
>
>
>
>
> [image: cid:image001.png@01CF86F9.22C2BC80]
>
> *Tony Harris*
> Digital Media & Photography Officer
> Government Art Collection
> tony.harris @culture.gov.uk <[log in to unmask]>* |* 020 7211
> 2426
> [image: cid:image002.jpg@01CF86F9.22C2BC80]@govartcol [image:
> cid:image003.jpg@01CF86F9.22C2BC80] /governmentartcollection |
> www.gac.culture.gov.uk
>
>
>
> On 29 March 2016 at 13:22, Mike Ellis <[log in to unmask]> wrote:
>
> > Does anyone have a handy “features our (museum) content management system
> > should support” type checklist they can point me at, other than just
> > suggesting I Google it…?
> >
> > Thanks in advance
> >
> > Mike
> >
> >
> >
> >
> > _____________________________
> >
> > Mike Ellis
> >
> > Thirty8 Digital: a small but perfectly formed digital agency:
> > http://thirty8.co.uk
> >
> > * My book: http://heritageweb.co.uk *
> >
> > ****************************************************************
> > 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/
> > ****************************************************************
> >
>
> ****************************************************************
> 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/
> ****************************************************************
>
> ****************************************************************
> 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/
> ****************************************************************
>
****************************************************************
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/
****************************************************************
|