> On 22 May 2016, at 16:18, Dave Wade <[log in to unmask]> wrote:
>
> Whilst this might seem like a "Me Too" I sometimes wonder if Drupal might be better for a Museum Site where you want to store details of objects. There are some plug-ins that allow the creation of custom Objects which can have many attributes, and which can be listed on highly customizable view grids. I haven't used it for a museum but I did use it for a Radio Club on-line library catalogue. Each Library Item had a number of custom fields e.g. "Title", "Author" , "ISBN", "Date Published" etc. The can also contain links to items. A plug-in allows the tables containing these items to be uploaded from a CSV file.
The same features are generally available in many Content Management systems.
The criteria for choosing a platform should involve more than a personal preference.
IME Drupal development is significantly more expensive than WordPress and you’re more likely to need a Drupal developer for help extending the system than WordPress.
See:
http://alistapart.com/article/choosing-a-cms-your-organization-will-love
Which identifies the main pitfalls of CMS choice.
The one everyone seems to ignore is that you need to create content before you think about managing it.
Does every object in your collection have a set of digital archive photographs and a number of interpretations already written? if not, start there - Word processor, File system and Spreadsheet are all you need to create and track content.
Your discovered content. image and metadata requirements will then better inform your choice of content management platform.
Put your story first, or you’ll always be constrained by your system of choice…
: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/
****************************************************************
|