JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MCG Archives


MCG Archives

MCG Archives


MCG@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MCG Home

MCG Home

MCG  August 2011

MCG August 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: What would an open source museum CMS look like?

From:

"Bonewell, Perry" <[log in to unmask]>

Reply-To:

Museums Computer Group <[log in to unmask]>

Date:

Thu, 18 Aug 2011 09:48:27 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (219 lines)

> Thinking that I might put together a "Wordpress for Culture"
hackday....
Anyone in?

Sounds good to me!

I completely agree on the point about the community aspect of WordPress
being a major advantage. My feeling is that museums could only benefit
from an eco-system on this kind of scale (even if it the platform may
never be considered to be "perfect", whatever that means). 

I am also keen on developing stuff that others can use but in the spirit
of what I would like to achieve I know that I can't do this alone (my
developer skills are almost non-existent for starters). 

Perry

-----Original Message-----
From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of
Mike Ellis
Sent: 18 August 2011 09:07
To: [log in to unmask]
Subject: Re: What would an open source museum CMS look like?

Blimey, you turn your back for five minutes and a thread the size of the
BM explodes on the MCG... :-)

Brilliant posts - thanks everyone. Couple of misc thoughts:

> The thing that always seems to be missing in CMS conversations (or
represented far too low down in order of importance) is usability. And
by that I mean usability for the editors, not the front-end. One of the
whole points about CMS is to enable non-technical people to edit
content, and yet it is here for these non-technical types that many
CMS's fail..

> The perennially awful thing about almost all of them is the rich text
editing. I found it totally astounding for example that Sitecore - the
incumbent CMS at NMSI - has a mindblowingly flexible API that do and
talk to pretty much anything. Try and actually *edit* some text or
*gasp* paste from Word? Result: horrible markup and frustrated users...

> The reasons for choosing O/S are as much about the community that sit
around the product as anything else. Wordpress is a blinding platform
because you can always find answers to questions. The community is
enormous, and growing. This isn't me saying WP is the right platform for
museum sites (although I think WP is a damn good answer for many sites
*up to a certain
scale*) - but that the "bespoke vs open" thing isn't just about the
licensing.

> I don't think Drupal can ever be presented as a "plug and play" 
> solution
:-)

Personally I think Nick and Danny nailed it - there is no single
solution, and the best response to this is surely building plugins,
modules and connectors.

Thinking that I might put together a "Wordpress for Culture" hackday....
Anyone in?

Mike

_____________________________


*Mike Ellis *

I've gone freelance! Find out more about our new digital agency:
http://thirty8.co.uk

...and I wrote a book - all about digital heritage strategy:
http://heritageweb.co.uk



On Wed, Aug 17, 2011 at 2:36 PM, Cristiano Bianchi | Keepthinking <
[log in to unmask]> wrote:

> Or maybe to have one system that does it all, in terms of (extended) 
> content management.
>
> Website, collection (both internal information, the 'real; collection 
> management, as well as the web display of collections), exhibition and

> events. And everything else that a museum or gallery needs. Plus the 
> shop (e-commerce for tickets, donations, merchandise, membership, 
> etc), all integrated into one, single database, and managed using one 
> integrated, web based software. With no compromises in terms of 
> quantity and quality of meta-data you can have, flexibility to adapt 
> to individual and changing needs, access to external resources and 
> vocabularies (e.g. Getty), mapping to ontologies (e.g. CIDOC-CRM, Lido

> or Dublin Core), integrated rights and digital asset management (local

> as well as online), production of reports in PDF as well as XML, APIs 
> (that can easily  This would cover most of the needs of any small of 
> large museum, leaving out (thanks to Nick Poole for his excellent
analysis):
>
> - School Group Bookings Systems
> - Office/productivity systems (including Contacts systems)
> - Customer Relationship Management Systems
>
> The problem we have with Drupal and the likes is that... we already
have 
> such a system, which has been built from scratch over the last ten 
> years following our work with museums and galleries. In time (next 
> year) will integrate what is outstanding. Should that system be open 
> source? It can be, if we find a compelling reason for it: in any case 
> we do not charge a license fee for it, only implementation (i.e. we do

> not make money from selling it, at this stage).
>
> And regarding what Tim Trent said:
>
> > I think the most important WCMS element is WYSIWYG.
>
> With similar vigour I would say this is not what's important, quite 
> the opposite. What you get depends on where you get it and when you 
> get it and changes all the time, with new browsers, new technologies,
new platforms.
> Stick to WYSIWYG and your content is out-of-date as soon as you have 
> created it. What you want to see is the web of logical connections 
> between content objects, the network of relationships that define 
> meaning for content according to contextual environments, in an 
> abstract way. This goes back to the point I was trying to make 
> earlier: content is one thing and presentation another. They should
talk to each other as little as possible.
>
> Best, Cristiano
>
>
>
> > I think the difficulty comes when you want to use a Content 
> > management
> system (like Drupal and WordPress) to exhibit collections.
> > Then the webCMS has to have many of the attributes of a musCMS.
> >
> > I think the answer, as has been suggested, is a three part system.
> > * Collections management
> > * Exhibition Data management
> > * Presentation system (web or otherwise)
> >
> > I think I now understand the original question to relate to the
> specification of a presentation system for web use that would 
> integrate exhibition data with the other important elements of museum
website.
> >
> > However, it seems to me that the missing part that needs to be 
> > built, is
> something that can import data from a wide variety of collections 
> management systems and export it for use in a wide variety of off the 
> shelf open source Content Management Systems?
> >
> > e.g. Import objects, output articles (with rich metadata)
>
>
> --
>
> Cristiano Bianchi
> Keepthinking
>
> 43 Clerkenwell Road
> London EC1M 5RS
>
> t. +44 20 7490 5337
> m. +44 7939 041169 (uk)
> m. +39 329 533 4469 (it)
>
> [log in to unmask]
>
> ---
>
> UK
> Registration no. 04905582
> VAT 831132962
>
> Italy
> Registrazione no. BO-475686
> Codice Fiscale 91304630378
> Partita Iva 02893681201
>
>
>
> ****************************************************************
>        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/
****************************************************************


This e-mail and any attached files are confidential and may also be legally privileged. They are intended solely for the intended addressee. If you are not the addressee please e-mail it back to the sender and then immediately, permanently delete it. Do not read, print, re-transmit, store or act in reliance on it. This e-mail may be monitored by Bolton Council in accordance with current regulations. 


This footnote also confirms that this e-mail message has been swept for the presence of computer viruses currently known to Bolton Council. However, the recipient is responsible for virus-checking before opening this message and any attachment. 


Unless expressly stated to the contrary, any views expressed in this message are those of the individual sender and may not necessarily reflect the views of Bolton Council. 


http://www.bolton.gov.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/
****************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager