<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Museums Computer Group &#187; Meeting report</title>
	<atom:link href="http://museumscomputergroup.org.uk/category/meetings/meeting-report/feed/" rel="self" type="application/rss+xml" />
	<link>http://museumscomputergroup.org.uk</link>
	<description>Computers + museums = MCG</description>
	<lastBuildDate>Fri, 09 Dec 2011 12:42:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>UK Museums on the Web 2010</title>
		<link>http://museumscomputergroup.org.uk/2010/12/09/uk-museums-on-the-web-2010-2/</link>
		<comments>http://museumscomputergroup.org.uk/2010/12/09/uk-museums-on-the-web-2010-2/#comments</comments>
		<pubDate>Thu, 09 Dec 2010 00:39:41 +0000</pubDate>
		<dc:creator>merel</dc:creator>
				<category><![CDATA[Homepage feature]]></category>
		<category><![CDATA[Meeting report]]></category>
		<category><![CDATA[Meetings]]></category>
		<category><![CDATA[UKMW]]></category>
		<category><![CDATA[ukmw10]]></category>

		<guid isPermaLink="false">http://museumscomputergroup.org.uk/?p=1176</guid>
		<description><![CDATA[Since I’m not a member of the MCG Committee I’m allowed to say this: UK Museums on the Web 2010 was a great success. Not only because it had a record number of attendees in comparison to previous editions, but also because it gave museum professionals the opportunity to be informed and inspired in times [...]]]></description>
			<content:encoded><![CDATA[<p>Since I’m not a member of the MCG Committee I’m allowed to say this: UK Museums on the Web 2010 was a great success. Not only because it had a record number of attendees in comparison to previous editions, but also because it gave museum professionals the opportunity to be informed and inspired in times that are tough and undoubtedly will get tougher still. Around the theme ‘Doing more with less: rising to the digital challenge in difficult times’ speakers and audience discussed four aspects of (digital) museum work that can provide us with the ammunition and resilience we need to overcome the challenges our museums will meet. Funding, collaboration, aggregating our online collections, and the use of open source were the main topics of the day, introduced by a keynote address from Nick Poole, Chief Executive at the Collections Trust.</p>
<p>To summarise an event that was so packed with valuable information, insights and discussions is quite the challenge and I am aware that this blog post is much longer than any blog post should be. So please follow the quick links to the different sections of the post below to get straight to the information you are looking for, or, if you must, read it all.</p>
<p><a href="#keynote">Keynote Address</a><br />
<a href="#fund">Fund Imaginatively</a><br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a><br />
<a href="#mic">Open Mic</a></p>
<h3><strong><a style="text-decoration: none;" name="keynote">Museums in a Digital Nation – Keynote</a></strong></h3>
<p>Nick Poole, Chief Executive of the <a href="http://www.collectionstrust.org.uk">Collections Trust</a></p>
<p>In his keynote address Nick Poole described his vision for museums as institutions that can help society to reconnect with itself. They should be accessible through a wide range of media, but should also provide high quality interaction between real objects and real people. While describing the strength and importance of museums, he also emphasised that it will be necessary to find alternative ways of funding in order to step away from the current situation of government dependency. His speech didn’t hide his strong conviction that museums can make money and should make money with their digital and online activities. These activities, according to Nick Poole should be aimed at satisfying audience needs, rather than provide what we think visitors want. Additionally, the use of technology should no longer be regarded as an ‘add-on’ to our existing programmes and activities. Our audiences are becoming more confident in using technology and this technology becomes easier to use and access at a fast rate. Museums have to adapt themselves to these changes, and develop products that can compete with commercial standards. However, no museums will be able to achieve this alone. Therefore, Nick encouraged us to collaborate within and outside our own field of work, we have to share our experiences and knowledge and be open about our lessons learned and the methods that we used. In his speech he seemed to advocate an all for one and one for all approach, encouraging ‘museum techies’ to fight the necessary battles within their own organisation, but to also look beyond the walls of their own museums in order to join forces and rise to the challenge together.</p>
<p>Nick Poole’s complete speech can be found on the <a href="http://openculture.collectionstrustblogs.org.uk/2010/11/26/museums-in-a-digital-nation-keynote-to-uk-museums-on-the-web-2010"> Open Culture blog</a>.</p>
<p><a href="#fund">Fund Imaginatively</a><br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a><br />
<a href="#mic">Open Mic</a></p>
<h3><strong><a style="text-decoration: none;" name="fund">Fund Imaginatively</a></strong></h3>
<p><strong>Online Fundraising</strong><br />
Alex Morrison (Managing Director, <a href="http://www.cogapp.com">Cogapp</a>)<br />
Alex Morrison talked about the opportunities of online fundraising. With 30.1 million adults in the UK accessing the Internet on an (almost) daily basis there is a very large potential online audience. What is even more interesting is that a large part of this audience is comfortable with making online donations. The UK website <a href="http://www.justgiving.com">Just Giving</a> makes it possible for people to raise funds online for their charity and currently has 12 million personal accounts. On average the charities represented on here raise £77,000 each, although some charities raise much more and others considerably less. Currently very few museums and galleries are represented on Just Giving, and Alex believes that using Just Giving could offer interesting funding opportunities for the museum sector.</p>
<p>Using a case study of the <a href="http://www.paradata.org.uk">online archive and collections</a> related to the Airborne Forces. Alex continued to describe how museums could build successful online donation opportunities into their website. With regards to the design of the donation form, he referred to a <a href="http://www.useit.com/alertbox/nonprofit-donations.html">paper by Jakob Nielsen</a>. When it comes to the content of the form his two tips were: Make it easy for people to engage and make it easy to give. Originally, people who wanted to use the online collections and archive of the airborne forces museum had to pay a registration fee. However, this didn’t prove successful. After changing this to free registration and an optional donation it turned out that 5% of the registered users made a donation with an average of £15 per donation and sometimes even more than one donation per user. Because many people register to use the service, the museum can contact the remaining 95% of its registered users to keep them informed on the work that can be done with the use of donations, encouraging them to make a donation as well. The aim is to make the service, including its staff, self-sufficient through the use of the donation scheme.</p>
<p>The <a href="http://www.slideshare.net/museumscomputergroup/museums-online-fundraising">presentation</a>, as well as a <a href="http://www.delicious.com/cogapp/stats">list of useful statistics</a> and other <a href="http://www.slideshare.net/cogapp">Cogapp presentations</a> are available online.</p>
<p><strong>Tate Online</strong><br />
John Stack (Head of <a href="http://www.tate.org.uk/">Tate Online</a>)<br />
John Stack discussed how various teams worked together on the Gaugain exhibition to create a coherent online experience for their visitors and to raise the revenue generated through the website. Like Alex Morrison, John emphasises the importance of visitor engagement. Visitors that feel engaged with a museum or exhibition are more likely to donate. John described three ways in which Tate’s web presence can generate income. Besides donating money, visitors can also purchase products through the online shop. Additionally, through targeted advertisement people are encouraged to visit the exhibition, which has an entrance fee. The online team, curators and marketing department have worked together to create an online environment in which people are stimulated to use one or more of these opportunities to donate or spend money. The exhibition has its own webpage, but instead of making this a highly designed (and expensive) page, it is kept relatively simple and is backed up by a wider web-presence for the exhibition. For example, people that have visited the Tate website will find banners for the Gaugain exhibition on Google and Facebook and instead of an automatically generated newsletter subscribers will receive a more personal message from a curator. Additionally, the exhibition curator has a blog on which she regularly publishes new posts. Just like the Airborne Forces Museum, Tate stimulates visitors to their website to register. After their physical visit to the museum people will automatically receive a request to review the exhibition, with the aim to keep them engaged after their visit and to stimulate them to be an advocate for the exhibition and the museum in their online communities. Although this wider web presence seems successful, John acknowledged that the curator’s engagement meant that more tasks were added to her workload. It was interesting to see how two museums that were very different seemed to benefit from using the same approach to generating online funding. Encouraging people to register on the website and providing them with an engaging online experience, rather than using more traditional marketing tools seemed to be the key points in both museums’ approach.</p>
<p>John’s presentation can be found on <a href="http://www.slideshare.net/museumscomputergroup/ukmw2010-john-stack-tate">slideshare</a>.</p>
<p><strong>From grant funding to online funding</strong><br />
Martin Bazley (Online Experience Consultant, <a href="http://www.martinbazley.com">Martin Bazley &amp; Associates</a>): &amp; Peter Pavement, (Director, <a href="http://www.surfaceimpression.com/home">Surface Impression</a>)<br />
Martin Bazley &amp; Peter Pavement approached the issue of funding from a slightly different angle. They have developed an online learning resource called <a href="http://www.mylearning.org">MyLearning</a> which makes it possible for content providers, like schools and museums, to create their own online learning resources. It is designed so that teachers can easily grab content from the website and leave again, because studies have shown that this is often how teachers work. A current aim for the project is to make it a national rather than local resource, which means it will be accessible for a wider range of content providers. Additionally searchability and findability of the different types of resources can be made more coherent, with links to <a href="http://www.culture24.org.uk/home">Culture24</a> and <a href="http://www.europeana.eu/portal/">Europeana</a> as a result.  This project was commissioned and funded by <a href="http://www.mla.gov.uk/what/programmes/renaissance/regions/yorkshire">Renaissance Yorkshire</a> and funding will probably be in place for another two years. However, when this runs out another funding model should be in place to fill the gap. In theory, schools could be charged for using the website and research has shown that they would be willing to do so. The bottleneck here lies with the actual process of registration and payment, which is something most teachers are not willing to spend time on. Therefore, in this case Martin and Peter suggested that it would be more effective to find external funding for the project. Securing funding is something that could be done by either a freelancer, an agency or by somebody within the organization.</p>
<p>Because finding and securing funding can be a laborious process with uncertain outcomes, it can be difficult to predict how much money will eventually be available for the project. A way to solve this problem could be the use of the Income Pipeline model. In this model all (possible) funding for the project gets classified based on the various phases of the funding process. Is the funding merely an opportunity, are you in the process of discussing the opportunities with the possible funder, has a proposal been written, are you awaiting a decision or has the funding been awarded? All these phases of the process are then awarded a percentage, representing the likelihood the funding will be received. When a funding opportunity is being discussed with a possible funder, there is a relatively small chance the funding will indeed be awarded. Of all the discussions held with possible funders, maybe one in 10 will prove to be successful. This can be translated to a likelihood of 10% for any funding that is being negotiated. For funding that has been awarded, the likelihood of receiving it is close to 100%. By adding up all the funding in the various categories and multiplying it by the likelihood percentage, it is possible to predict the total amount of funding that can be secured for a project. This process works well if you are trying to secure funding on an ongoing basis and have the opportunity to pursue large numbers of funding opportunities. With a small number of opportunities the percentages are less usable. Possible ways of funding a project like MyLearning are public funding, grant funding, revenue income through a commissioning structure and the use of advertisements through websites like <a href="http://www.adify.com/adify-united-kingdom">Adify</a>.</p>
<p>After this <a href="http://www.slideshare.net/museumscomputergroup/mylearningandfundingukmw10-martin-bazley">presentation</a> questions from the audience focused on the fact that charities already have much more experience in online fundraising than museums and the issue of collaborating in the fundraising process. Is it possible for museums to work together on this point?</p>
<p><a href="#keynote">Keynote Address</a> by Nick Poole (Chief Executive, Collections Trust)<br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a><br />
<a href="#mic">Open Mic</a></p>
<h3><strong><a style="text-decoration: none;" name="collaborate">Collaborate Creatively</a></strong></h3>
<p><strong> </strong></p>
<p><strong>Partnerships between museums and communities</strong><br />
Angelina Russo, Associate Professor, RMIT University, Melbourne and<a href="http://www.museum3.org">www.museum3.org</a>)<br />
Angelina Russo has been working on collaborative projects for several years and in her experience museums today are less anxious to work together than several years ago. Funding models often support collaboration, although they are, according to Joanna, not necessarily designed to support sharing resources and outcomes amongst museums. Angelina was involved in setting up <a href="http://www.museum3.org">Museum3</a>. This online space was originally developed as a space where museum professionals could share knowledge and develop new partnerships. Users can create a profile and join in discussions on the forum and respond to blog posts. Just like MyLearning, Museum3 originally received funding, but when this funding ended a new model to generate income was needed, or it wouldn’t be possible to maintain the website. After positive feedback from the community, the decision was made to reshape Museum3 into a ‘real’ organisation. The constitution was written together with the community. To generate income users are encouraged to become paying associate members and this model seems to be a success. Angelina stressed the importance of finding ways to engage and creating possibilities to participates in ways that are not one-off projects. By stimulating ongoing engagement, museums can demonstrate their value to their community. As an example she mentioned the possibility to work with communities of  ‘makers’, like people involved in arts and crafts, but also movements as <a href="http://diycitizenship.com">DIY Citizenship</a>. Additionally, Angelina encouraged museums to look for unexpected partnerships, like the partnership with the Australian Football League she was involved in and which was funded for entirely by the Football League, without the need of any government funding.</p>
<p><strong>Partnership with BT</strong><br />
Joanna Pollock (Knowledge Transfer Strategy and Development Manager, Arts and Humanities Research Council, John Seton (Head of Regional Strategic Partnerships, <a href="http://www.btplc.com/Thegroup/Ourcompany/Companyprofile/Groupbusinesses/BTInnovateandDesign/index.htm">BT Innovate and Design</a>)<br />
John Seton introduced the work of  BT Innovate and Design. At their offices, which John described as “100 acres of nerds&#8221; BT Innovate and Design are doing research in collaboration with universities, governments and customers. The main strand of research looks at creating faster networks and the uses customers could and would have for them. Where it’s relatively easy for BT to find and approach big organisations, they also want to work together with smaller institutions. BT works together with a wide variety of clients and in the past had worked on digital heritage projects in an EU context. In order to do more research on this subject in the UK, BT has been collaborating with <a href="http://www.ahrc.ac.uk/Pages/default.aspx">AHRC</a>. The AHRC brokered a workshop that enabled BT to get in contact with organisations from the arts and heritage sector. With the use of AHRC funding for collaborative research networks, five of these networks formed a research community around the use of digital media in a museum and heritage context.</p>
<p>Although these five networks each did their own strand of research, they got together regularly and discussed and shared progress, outcomes and information on their projects. One of these projects was <a href="http://museumscomputergroup.org.uk/projects/livemuseum/">LIVE!Museum</a>, which was launched at UKMW09. According to Ross Parry, what was special with these projects was that the research questions rose from within the museum community, rather than from the academic field. It also released the potential of the Museum Computers Group as a place where people can meet and collaborate. This collaboration with AHRC has provided BT with a wealth of new contacts within the arts and heritage sector from <a href="http://www.falmouth.ac.uk/">University College Falmouth</a>, to a number of Welsh Museums and from the <a href="http://www.sciencemuseum.org.uk">Science Museum</a> to <a href="http://www.gold.ac.uk/">Goldsmiths</a>. BT is hoping to continue this kind of collaboration in the future and is hoping to make use of future AHRC calls for funding to further their collaboration with the heritage sector.</p>
<p>John’s presentation can be found on <a href="http://www.slideshare.net/museumscomputergroup/jo-and-john-presentation-ukmw10-5908037">slideshare</a></p>
<p><strong>Variables and must-haves for successful collaboration</strong><br />
Kevin Walker (Research Officer, <a href="http://www.lkl.ac.uk/cms/index.php">London Knowledge Lab</a>)<br />
Kevin Walker discussed various possible models for successful partnerships, but emphasised that a consistent vision was key for any form of collaboration. As an example he mentioned A History of the World in 100 Object, the successful collaboration between the <a href="http://www.bbc.co.uk/ahistoryoftheworld">BBC</a> and the <a href="http://www.britishmuseum.org/ahistoryoftheworld">British Museum</a> which was very much shaped by Neil MacGregor’s vision. He also briefly spoke about projects he worked on at <a href="http://www.kew.org">Kew Gardens</a>, <a href="http://www.centrepompidou.fr/Pompidou/Accueil.nsf/Document/HomePage?OpenDocument&amp;L=2">Centre Pompidou</a> and the <a href="http://www.foundlingmuseum.org.uk/">Foundling Museum</a>. By discussing this wide range of projects, a number of variables became discernible: has the end product one voice, or many voices? Does it involve a large number of objects, a few or just one? And how many stories are being told? For example, can visitors all give their own interpretation of an object or is there one very clear story line? These variables might be useful to create a clear outline of a project from the beginning. Besides these variables, Kevin also discussed a number of elements that he deemed crucial for a successful collaboration. Firstly, the clear single vision can bring consistency and makes clear branding possible. Secondly, working with a commercial partner can guarantee quality of technology and design. And lastly projects that are education-led tend to be more successful that the ones that are led by technology. It avoids the “we should do something with pda’s/tablets/wifi/qr-codes&#8221; trap and allows the museum to question its needs, before deciding what technology to use.</p>
<p>Kevin’s <a href="http://www.slideshare.net/museumscomputergroup/ukmw10-walker-6004117">presentation</a> led to a discussion on the role of story telling in museums. Kevin stressed that story telling should always aim to help visitors connect with the museum and its collections and Angelina drew attention to the fact that Neil MacGregor spoke about museums as cultural broadcasters and curators as cultural publishers. This challenges the way some museums and curators perceive their role.</p>
<p><a href="#keynote">Keynote Address</a> by Nick Poole (Chief Executive, Collections Trust)<br />
<a href="#fund">Fund Imaginatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a><br />
<a href="#mic">Open Mic</a></p>
<h3><strong><a style="text-decoration: none;" name="aggregate">Aggregate Smartly</a> </strong></h3>
<p><strong>Europeana</strong><br />
Jill Cousins (Executive Director, <a href="http://www.europeana.eu/portal/">Europeana</a>)<br />
Jill Cousins talked about how Europeana aims to bring museums, archives, audio and visual collections together in Europe by aggregating the aggregators. In 2008 a prototype was launched and what started with 2 national aggregators has grown out to a database that is being fed by 28 national aggregators with over 1000 participating institutions. So far there has been no marketing campaign for Europeana and instead of actively collecting data, Europeana is trying to convince aggregators to feed into the database. This makes standardisation easier, but it is still challenging to overcome issues relating linked data, data enrichment and multilingualism of the system. To avoid broken links, a persistent identifier is needed. Instead of copying the actual content, Europeana only keeps the metadata on its server and one of the goals for the future is to make this metadata interlinked open data. The current agreement that the content is for non-commercial use only means that it is not possible to share content with Wikipedia. Currently Europeana is working on Collective Licensing and a structure that can provide participating organisations with fair compensation. The goal for Europeana is to distribute, facilitate, aggregate and encourage people to engage with the content, because they believe access to culture nurtures creativity, which can stimulate growth.</p>
<p>The <a href="http://www.slideshare.net/museumscomputergroup/museum-of-london261110">slides</a> for this presentation can be found on Slideshare.</p>
<p><strong>The importance of online collections</strong><br />
Linda Ellis (Project Manager Online Collections, Wolverhampton City Council / <a href="http://blackcountryhistory.org/">Black Country History</a>) and James Grimster (Director, <a href="http://www.orangeleaf.com">Orangeleaf Systems Ltd</a>)<br />
Linda Ellis and James Grimster talked about their project that aimed to open up the collections of the Black Country, but also looked at the challenges museums face when it comes to engaging online communities. As James put it poignantly: More people farm electric sheep in Farmville than use digital collections. Why are people willing to become a mayor of a car park with <a href="http://foursquare.com">foursquare</a>, but are they not consulting our databases as often as they could?</p>
<p><a href="http://blackcountryhistory.org/">Black Country History</a> aims to make collections of institutions in the region accessible to an informed audience in a way that is Google-friendly and cost-efficient. It is trying to reach its audience through a main website, microsites that are all aimed at different target audiences and through social networking tools. The content is being delivered by four museums and four archives and currently +127800 records are available. Besides these eight partners, another eight parties are involved in the project. Because the records are aggregated from different databases issues with regards to terminology, spelling, data quality and missing data had to be overcome. The use of different date formats in the various collection management systems also proved to be a problem. The content that is available on Black Country History is also available through <a href="http://www.culturegrid.org.uk">CultureGrid</a> and <a href="http://www.europeana.eu/portal/">Europeana</a>. It is also part of a wider project called <a href="http://www.digitalmidlands.org.uk">Digital Midlands</a> which provides access to a quarter of a million records.</p>
<p>James drew attention to an issue that is not only of importance for the Black Country History project, but will probably resonate with many museums that are working with online collections: how can we show our importance to the online community? Can we create an environment where people can earn virtual rewards or do location based treasure hunts? Should it be possible to digitally discover your local area during a sponsored pub crawl? James is interested to find out in what ways other museums have tried to engage online audiences with their collections. What are the experiences? What works and what doesn’t?</p>
<p>After this <a href="http://www.slideshare.net/museumscomputergroup/black-country-collections-online-ukmw10-final">presentation</a> there was a discussion on finding new ways to engage users with our collections. Linda Ellis mentioned how they were looking into the possibility of letting people comment on the objects and their information and Jill Cousins described how some museums try to engage people through their passion for a certain subject. Laura Whitton from Collections Trust suggested that maybe museums shouldn’t be suggesting new uses of their collections, but that they should encourage users to be creative. She referred to the hack day that will be hosted in the Midlands. In response to this Jill mentioned how some museums themselves still need to be convinced of the importance of opening up collections online, because they fear loosing income in the future. Any comments or thoughts on this subject (or any others mentioned in this blog post) are more than welcome.</p>
<p><a href="#keynote">Keynote Address</a> by Nick Poole (Chief Executive, Collections Trust)<br />
<a href="#fund">Fund Imaginatively</a><br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#build">Build Openly</a><br />
<a href="#mic">Open Mic</a></p>
<h3><strong><a style="text-decoration: none;" name="build">Build Openly</a></strong></h3>
<p><strong>New Media in the Museum of London</strong><br />
Paul Clifford (Programme Manager (Digital Learning), <a href="http://www.museumoflondon.org.uk/English/Online/">Museum of London</a>)<br />
At the end of a very long day filled with little geek talk, but mainly inspirational examples and useful tips, Paul Clifford talked about the use of digital media in the Museum of London. The Museum of London tries to use open source software where possible, to make it possible for visitors and school groups to use the same software at home or at school. As an example he mentioned easy to use digital cameras (such as<a href="http://www.theflip.com/en-gb/">Flip cameras</a> and <a href="http://www.prezi.com">Prezi</a> as an alternative for Powerpoint. Because there is only a limited amount of time available for a blended learning session in the museum, any software and hardware that is used during these sessions must be easy to use. The Museum of London has an impressive array of gadgets and software available, from digital cameras, interactive whiteboards and QR barcodes to Bluetooth, WIFI and WordPress. However, Paul emphasised that “It is not what you’ve got, it’s how you use it that counts.&#8221; He encouraged us to take time to play with open source software and to “build fast, build cheap and build often.&#8221; With products and services being updated and improved all the time, we have to change the way we work. “Perfect is the enemy of good,&#8221; Paul advised. It seemed like his boundless enthusiasm and energy rubbed off and I wouldn’t be surprised if some of the people present at the conference have since taken up his advice and are testing out new cheap and easy ways of introducing digital media into their museums.</p>
<p><strong>How open source influences our way of working</strong><br />
Mark Polishook (Open Source artist)<br />
After Paul’s enthusiastic talk, Mark Polishook talked about how the use of open source can change the way we work. He described how, when he first started using open source, he felt it was easier to collaborate with a wide range of different people. Everybody was keen to share their knowledge and experience with others using the same open source software. According to Mark, because of this open source seems to foster collaboration much more than conventional software. Because everybody can change and add to open source, we are also more likely to have a deeper sense of ownership. The traditional: “What does it do?&#8221; makes place for a new question: “Can we make it do this?&#8221; This characteristic of open source was described by Mark as <em>potential energy</em>. Where open source can help different departments within an organisation work together, it can also be a battle to convince colleagues of the use of new working methods and software. Introducing open source is often hard work and Mark warned us that we have to seriously consider the risks of stimulating change. Introducing a piece of software that doesn’t work well within the organisation may put colleagues off using open source all together. With this message the presentations of Paul and Mark counterbalanced each other perfectly. Wonderful things can be achieved when using open source, but it will require organisational change, which always bring its own challenges with it.</p>
<p><strong>Open Source and Open University</strong><br />
Trevor Collins (Research Fellow, <a href="http://kmi.open.ac.uk">Knowledge Media Institute, Open University</a>) &amp; John Lea (Open University)<br />
In the last presentation of the day, Trevor Collins and John Lea again emphasised the positive aspects of open source. It is generally quick to install, it is tried and tested, easy to use and reliable. They described a <a href="http://www.slideshare.net/museumscomputergroup/photomarathon-10minsv1">photo competition</a> they organised in a museum during which teams of children had to take three photographs, each of another pre-determined topic, within an hour. These pictures where then shared and discussed. To establish a network in the museum, they used an open source web server on one of their computers. When they were explaining how this server worked, I realised that a certain amount of geekiness is sometimes still required, no matter how user-friendly software has become these last few years. But then again, maybe that’s just me. And I must admit that throughout the day there had been very little ‘geek talk’ indeed. It seems like we have really come to a point where everybody can get involved and I certainly intend to follow Paul Clifford’s advice and <em>play</em> more.</p>
<p><a href="#keynote">Keynote Address</a> by Nick Poole (Chief Executive, Collections Trust)<br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a></p>
<h3><strong><a style="text-decoration: none;" name="mic">Open Mic</a></strong></h3>
<p>It is a UKMW tradition to have an energising session in the day where, through a series of super short ‘micro presentations’, members from the floor have just 4 minutes to update on a project, call for partners, pitch an idea, ask for support, highlight a new initiative, or just contribute to the event and the life of the MCG more widely.</p>
<p>Danny Birchall from the Wellcome Collection talked about <a href= "http://www.wellcomecollection.org/whats-on/exhibitions/things.aspx">Things</a>, a recent participatory event that was held at the Wellcome Collection. Visitors were encouraged to add to the collection by bringing in anything they thought valuable or special during the bring-a-thing-athon. The only rule was: It can’t be bigger than your head. All things were accessioned (either temporary or permanent), displayed and photographed. Volunteers then added the pictures and any additional information to the Wellcome Collection website, using Flickr. Displaying the objects online as well as in the exhibition space gave the objects and the project much more visibility. By using a well-known and free system like Flickr meant little training was needed and the project could be run with limited costs. Finally, working with artists provided a chance to experiment and to work outside the boundaries of normal institutional procedures.</p>
<p>Charlotte Connelly described the Public History of Science, Technology, Engineering and Medicine project at the Science Museum. Since the late 90’s the Science Museum has been rethinking the way it talked about science. A more participatory approach was introduced for developing new exhibitions and with the Public History project the museum wants to introduce this way of working in the more historical galleries. A workshop on co-curation and Social History was held in the museum during which various museums came to share their experience with co-curation. For more information on this workshop, you can visit the <a href= "http://ccphworkshop.pbworks.com"> wiki</a>. With a couple of one-off exhibitions and events the museum wants to investigate how it can give audiences more chances to participate and how it can use the web to encourage visitors to create content and help the museum to improve its knowledge about the collections. The first exhibition will aim to have visitors engage with one iconic object from the museum’s collections: an early music synthesizer, whose samples could me made available online for visitors to remix.</p>
<p>Oliver Vickers-Harris is a consultant who worked on the <a href= "http://www.louisvuittonyoungartsproject.com"> Louis Vuitton Young Arts project</a>. This project is the digital expression of a wide-ranging education programme, which has three key themes: Collaboration, integration and co-creation. Five galleries worked together with Louis Vuitton, which was a partner as well as the sponsor. The online presence was to be integrated in other activities the partner organisations were already undertaking. The young people who worked on the project were seen as the ‘key client’ and their ideas fuelled the project. They also decided on the project name and brand. Crowd sourcing was used to express the project’s identity. Of course, working with multiple partners as well as young people was a challenge, but it was also a great opportunity. Oliver believes that it will become more common in the future to work in this way.</p>
<p>Simon Ford works at <a href= "http://www.prescientsoftware.co.uk">Prescient Software</a> a tech start-up specialising in using linked data. They are working on a project that uses intuitive thinking patterns of users to enhance the flexibility and future proofing of web content. Users will be better able to define their own journeys, which will make it possible to increase the stickiness of content. It gives people the opportunity to search through databases using filters and database queries. It uses the concept that ‘navigation is the data’ in creating a web environment for users. Simon was interested to find out if the delegates thought this could have a useful application in a museum context.</p>
<p>Gemma Sturtridge works at the Museum of Croydon, a local authority museum that is threatened by closure due to government cuts. She was wondering what MCG members could do to assist museums in similar situations. She suggested to create a statement about the importance of digital heritage, which can then be shared by museums as a tool to prove their relevance and importance. It is agreed that members that are interested can develop this statement together. Gemma will write a draft version. After the conference there has been a discussion about this advocacy statement on the <a href= "http://museumscomputergroup.org.uk/2010/12/16/advocacy-statement"> MCG website</a>.</p>
<p><a href="#keynote">Keynote Address</a> by Nick Poole (Chief Executive, Collections Trust)<br />
<a href="#collaborate">Collaborate Creatively</a><br />
<a href="#aggregate">Aggregate Smartly</a><br />
<a href="#build">Build Openly</a></p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/2010/12/09/uk-museums-on-the-web-2010-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spring Meeting &#8211; Museum of London</title>
		<link>http://museumscomputergroup.org.uk/1996/05/16/spring-meeting-museum-of-london-16-may-1996/</link>
		<comments>http://museumscomputergroup.org.uk/1996/05/16/spring-meeting-museum-of-london-16-may-1996/#comments</comments>
		<pubDate>Wed, 15 May 1996 23:32:45 +0000</pubDate>
		<dc:creator>mia</dc:creator>
				<category><![CDATA[Archived Events]]></category>
		<category><![CDATA[Event-Category]]></category>
		<category><![CDATA[Meeting report]]></category>
		<category><![CDATA[Meetings]]></category>

		<guid isPermaLink="false">http://museumsontheweb.org.uk/?p=318</guid>
		<description><![CDATA[The MOL hosted a most useful day out for MCG members, to describe the definition and procurement of a new computer network and collections management software. The morning was taken up with presentations on the development of the museum&#8217;s IT strategy, outsourcing of IT services, and the procurement of Multi-MIMSY. The afternoon included a series [...]]]></description>
			<content:encoded><![CDATA[<p>The MOL hosted a most useful day out for MCG members, to describe the definition and procurement of a new computer network and collections management software. The morning was taken up with presentations on the development of the museum&#8217;s IT strategy, outsourcing of IT services, and the procurement of Multi-MIMSY. The afternoon included a series of demonstrations of aspects of the package followed by a LASSI progress report and a short panel discussion.</p>
<p><strong>Peter James</strong>, IT coordinator at the museum, started the proceedings with an overview of the museum&#8217;s IT strategy. The current process &#8211; which took 2 years to complete &#8211; began with an independent review by CCTA of the museum&#8217;s IT provision which uncovered a familiar story of lack of understanding by the existing IT section of the fundamental requirements of the museum users, no practical service level agreement, and a mish-mash of unrelated software and hardware. The CCTA recommended that the museum acquire and implement:</p>
<ul>
<li>
<ul>
<li>Client-server architecture</li>
<li>LAN and WAN</li>
<li>Image capability</li>
<li>Windows-type software</li>
<li>Industry standard hardware, communications and operating systems</li>
<li>A standard for support and maintenance.</li>
</ul>
</li>
</ul>
<p>The office and collections tools of choice were</p>
<ul>
<li>
<ul>
<li>An office automation suite (e.g. Microsoft Office)</li>
<li>Specialist collections management software</li>
<li>Specialist Library Management software</li>
<li>Internet connection</li>
</ul>
</li>
</ul>
<p>The museum then embarked on three separate procurements:</p>
<ul>
<li>
<ul>
<li>A main service provider to supply project management, up-to-date IT knowledge and IT support.</li>
<li>Collections information and management system</li>
<li>Library and archives management system</li>
</ul>
</li>
</ul>
<p>The project team was composed of members from all business areas and issued a definition of service requirements in November 1994. There were 75 responses to the <em>European Journal</em> advertisement for a service provider and 33 serious follow-ups. Data Sciences UK was finally chosen from a shortlist of 6. They recommended Netware, Windows for Workgroups (&#8220;since Microsoft were not being entirely honest about the future of Windows 95&#8243;), and Microsoft Office. Hardware was supplied by Data Sciences on a lease-lend basis over three years. The service contract is for 3 years after which a review will result either in a new contract or a new procurement.</p>
<p>The software requirements were sent to 9 possible suppliers, with the final choice of collections information and management software being Willoughby Systems&#8217; Multi-MIMSY (MM) via their UK agent Lusis (which has grown from the Heritage Services section of the Welsh Water Board&#8217;s IT department). Agreement was reached only 2 weeks prior to the MCG meeting. The Library and Archive system (of which the choice was Oracle Library) had to be postponed following budget cuts and the library will be catalogued using the bibliographical capability of MM instead.</p>
<p>Expected benefits of the new systems include:</p>
<ul>
<li>
<ul>
<li>Improved communications and document transfer (e-mail, fax, Internet)</li>
<li>Common training programs</li>
<li>Improved information handling</li>
<li>Help desk on site</li>
<li>Access to trained experienced IT professionals</li>
<li>A monitored service level agreement</li>
</ul>
</li>
</ul>
<p>IT is now managed by a centralized <em>IT Steering Committee</em> which ensures that business needs are met; that value for money is obtained (via a newly-centralized IT budget); agrees priorities and a common policy framework; and monitors development work. Future plans include an image archive, Internet and Intranet (a web page is to be launched in 2-3 months), public access facilities in galleries (including touch screen access), multimedia publishing, and data-voice integration.</p>
<p><strong>Richard Avery</strong> of Data Sciences (a subsidiary of IBM) presented the case for outsourcing &#8211; a term they had invented. Major benefits are considered to include cost saving, allowing existing resources to focus on core business needs, and access to emerging technologies and knowledge of existing ones. (For more information on the company see http://www.DataSci.co.uk.) <strong>Paul Duggan</strong>, the Data Sciences MOL account manager, commented on the basics of a successful procurement: a good statement of requirements, and a thorough audit of the existing system. It is also essential to get high-level support for the project.</p>
<p>It was too early to say yet what major benefits the procurement had brought. E-mail was an instant hit, but users were still getting to grips with the other software. A questionnaire had been circulated to gauge user satisfaction. In answer to queries from the floor, Richard affirmed that out-sourcing was not to be feared and that the presence of the CCTA analysis was vital to the success of the project, however, those going down this path must be prepared to pay accordingly for such detailed analysis.</p>
<p><strong>Andrew Roberts</strong> described the background and planning required for the project. The MOL is looking to catalogue and manage some 185,000 objects in its core collections, a large archaeological archive, the Docklands Museum Project, nearly 400,000 photographs and ephemera items and the museum library of over 25,0000 books. The MOL&#8217;s information systems and documentation procedures were reviewed in 1989 and 1992. Some of the latter shortcomings were addressed by the installation of a Documentation Officer and Registrar in 1993, but problems with the existing IT solutions continued to grow. The in-house system did not offer a long-term solution; furthermore the development of a new in-house system was seen as too expensive and risky. A review by the CCTA recommended separate collection and library applications, and standardised hardware and office software. In June-November 1994 a detailed Operational Requirement (OR) was drawn up by a working group of lead users who examined the museum&#8217;s documentation and collection management objectives in the light of the experience of other museums, the LASSI proposals, and national documentation standards. Of the final list of functional requirements, 111 were flagged as mandatory, 104 highly desirable, and 127 medium to low desirable. The available packages were reviewed and a preliminary assessment made. The resulting shortlist of 9 vendors were sent the OR in November 1994. The responses were carefully analysed and evaluated. Only two products unequivocally provided the mandatory requirements, 4 failed. The final shortlist included Multi MIMSY and Advanced Argus. After a full analysis and detailed demonstrations the former emerged as the option of choice. It is an Oracle-based client-server application running under Microsoft Windows.</p>
<p>A major part of the process was data migration. Not only were there the object records to transfer, but many thousands of collections care, management and conservation records needed to be converted. Terminology standards needed to be decided upon and data cleaned to match the new requirements. Syntax and terms had to be standardised, and errors reduced. For example the 8,000 object names latterly in use have been reduced to 4-5,000 names, all matched to the Art and Architecture Thesaurus. The process took over 18 months. Rationalization of the names of places and persons offer even more of a challenge. During the transfer process some data had to be reassigned to new fields, and coded entries were expanded to full text. A great deal of customization has been found necessary to accommodate MOL data fields. MIMSY has many more fields than are actually required and care is necessary to ensure that different fields are not being used for what is essentially the same data.</p>
<p>Training for lead-users and initial training of end-users was still going on and it is anticipated that 6-9 months will be required to get to grips with the software. Target date for live use of the museum MIMSY database was July 1996.</p>
<h3>Afternoon Sessions</h3>
<p>After lunch, delegates were shown various aspects of the package by different members of staff. Delays in formalising the contract meant that the system had only been installed at the MOL the day before the MCG visit (!) and, owing to the so recent implementation of the package, and the staff&#8217;s understandable unfamiliarity with the software, these demonstrations often asked more questions than they answered. Nevertheless, the day was a very successful and interesting one, the venue and hospitality excellent, and MCG members will be very interested to hear more of this major development.</p>
<p>The final presentation was an <strong>update of the LASSI project by Alice Grant</strong>, Head of Collections Information at the Science Museum. The complexities of the LASSI Framework and Enabling Agreements were described, whereby the MGC and Willoughby contract together to provide an umbrella for consortium members who contract with the MCG to become an Authorized Demander and then contract direct with Willoughby via LUSIS, their UK agents, to acquire the product and arrange installs, data migration and training. Readers will not be surprised to learn that the development of these contacts took a long time and engaged the attentions of 8 museum services (each with their own legal departments), hosts of acronyms â€“ including MGC, DNH and CCTA â€“ Willoughby, Lusis, 16 solicitors, lots of money, time, and effort. This long-drawn-out process was illuminated by a wonderful edited photograph of the &#8220;other&#8221; Lassie with a gun to her head and the caption &#8220;Sign the contract or the dog gets it.&#8221; How we laughed&#8230;</p>
<p>Much work remained to be done on upgrading the product to the LASSI standard. The LASSI-compliant version of Multi MIMSY (version 2) will be available in the summer of this year.</p>
<p>Future plans at the NMSI were outlined, including exciting projects on public access for both real and virtual visitors with the aim of producing a multiple-use knowledge base, a £14m &#8220;imaging frontiers&#8221; project at the National Museum of Photography, Film and Television, the &#8220;Challenge of Materials&#8221; gallery, database and CD-ROM and virtual exhibition on the World Wide Web. Less sexy, but vital, background work included revised collections management procedures (with cross-fertilisation to Spectrum), and the development of a thorough names authority file.</p>
<h4>User Friendly Terminology Control</h4>
<p>You will be familiar with the term GIGO: garbage in &#8211; garbage out. A database will only be useful if its content is accurate, coherent and consistent. Sometimes non-specialists may enter information which leaves something to be desired. Even among period specialists, there can be a variety of terms used to denote the same object type. It is hardly surprising that confusion and frustration can ensue. The logic of the approach given below is intended to provide an example where terminology control can be helpful, rather than ogreish. Any implementation of terminology control that its worth its salt should not require detailed knowledge of the system or of its codes. Users should be able to enter natural language terms which enable searches.</p>
<p>Having inherited and laundered a <em>stream of consciousness</em> database of some 10,000 archaeological objects (described in ACN 34 and 36), it made sense to ensure that some form of checking at source was introduced wherever feasible. This task was facilitated (for specific item names) by the Bedfordshire Artefacts Typology (BAT) and generally (e.g. for period) by the National Archaeological Record (NAR) compiled by the Royal Commission on the Historical Monuments in England (RCHME).</p>
<p>An example BAT record from Luton Museum is shown below. The underlines show &#8220;Symbolic Data.&#8221;</p>
<table border="1" cellspacing="0" cellpadding="0" width="500">
<tbody>
<tr>
<td valign="top"></td>
</tr>
<tr>
<td valign="top"><em>Prehistoric Flint Tools</em></td>
</tr>
<tr>
<td valign="top"><em>15.14 axe (stone)</em></td>
</tr>
<tr>
<td valign="top"><strong>Usage</strong></td>
</tr>
<tr>
<td valign="top"><em>Use for hafted axes only, not handaxes, see also adze (flint)</em></td>
</tr>
<tr>
<td valign="top">Full name(s) <strong>Note</strong></td>
</tr>
<tr>
<td valign="top"><em>celt ne</em></td>
</tr>
<tr>
<td valign="top"><em>concave-sided ln</em></td>
</tr>
<tr>
<td valign="top"><em>edge-ground chisel lne</em></td>
</tr>
<tr>
<td valign="top">thick-butted <em>ne</em></td>
</tr>
<tr>
<td valign="top">thin-butted <em>lne</em></td>
</tr>
<tr>
<td valign="top"><strong>Related BAT records Function</strong></td>
</tr>
<tr>
<td valign="top">15.31 <span style="text-decoration: underline;">adze (flint)</span></td>
</tr>
<tr>
<td valign="top"></td>
</tr>
</tbody>
</table>
<p align="right">&#8220;Symbolic data&#8221; is provided by the system rather than keyed in. For example<em> Prehistoric Flint Tools</em> is derived from the first element of the BAT code (15); <em>adze (flint)</em> is culled from a related record. In this example, the note field is used to remind users of period (using NAR abbreviations). With use, the BAT continues to expand as more objects are categorised and added. In time, objects may be listed under more than one category.</p>
<p>Every archaeological artefact on Luton Museum&#8217;s database is cross-checked by a BAT record. Data entry is both more structured and simplified. Use of standard terms, expansion of approved (NAR) and user-defined abbreviations have also been implemented. Thus if a user enters <em>ne</em> or <em>neo</em> into the Period field, it is automatically expanded to <em>neolithic</em>. If required the process can be reversed. If we need to target or group together types of artefact, the BAT makes it much simpler to do so. The BAT is implemented using Microsoft Access at Bedfordshire County Council, and Advanced Revelation (version 2.12) at Luton Museum.</p>
<p>Having implemented a synthesis of the BAT with the NAR at Luton, it was considered worthwhile to put into effect some form of consistency checking. To avoid anachronisms, a program was written to check period against simple and full name entries. As the BAT is a developing system, it was thought unwise to make the period checking mandatory. The program advises the user, rather than changing any information. It should be relatively straightforward to apply the same logic using any other programming language. Copies of the code are available upon request.</p>
<h4>Listing of BAT for flint artefacts</h4>
<table border="1" cellspacing="0" cellpadding="0" width="500">
<tbody>
<tr>
<td width="18%" valign="top"><strong>Key</strong></td>
<td width="29%" valign="top">Simple name</td>
<td width="53%" valign="top">Full name</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.1</td>
<td width="29%" valign="top">arrowhead (flint)</td>
<td width="53%" valign="top">barbed and tanged</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">chisel</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">leaf shaped</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">oblique</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">petit tranchet</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">tanged</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">transverse</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">triangular</td>
</tr>
<tr>
<td width="18%" valign="top">15.2</td>
<td width="29%" valign="top">blade</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.3</td>
<td width="29%" valign="top">shouldered point</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.4</td>
<td width="29%" valign="top">burin</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.5</td>
<td width="29%" valign="top">core</td>
<td width="53%" valign="top">levallois</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">refitted core</td>
</tr>
<tr>
<td width="18%" valign="top">15.6</td>
<td width="29%" valign="top">flake (flint)</td>
<td width="53%" valign="top">debitage</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">refitted flake</td>
</tr>
<tr>
<td width="18%" valign="top">15.7</td>
<td width="29%" valign="top">hammerstone</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.8</td>
<td width="29%" valign="top">handaxe</td>
<td width="53%" valign="top">biface</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">cordate</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">ovate</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">pointed</td>
</tr>
<tr>
<td width="18%" valign="top">15.9</td>
<td width="29%" valign="top">macehead</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.10</td>
<td width="29%" valign="top">microlith</td>
<td width="53%" valign="top">geometric</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">hollow based point</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">obliquely blunted</td>
</tr>
<tr>
<td width="18%" valign="top">15.11</td>
<td width="29%" valign="top">piercer</td>
<td width="53%" valign="top">awl</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">borer</td>
</tr>
<tr>
<td width="18%" valign="top">15.12</td>
<td width="29%" valign="top">scraper (1)</td>
<td width="53%" valign="top">button</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">discoidal</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">hollow</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">end</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">side</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">side/end</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">thumbnail</td>
</tr>
<tr>
<td width="18%" valign="top">15.13</td>
<td width="29%" valign="top">fire fractured flint</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.14</td>
<td width="29%" valign="top">axe (stone)</td>
<td width="53%" valign="top">celt</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">concave-sided</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">edge-ground chisel</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">thick-butted</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">thin-butted</td>
</tr>
<tr>
<td width="18%" valign="top">15.15</td>
<td width="29%" valign="top">burin spall</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.16</td>
<td width="29%" valign="top">core rejuvenation flake</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.17</td>
<td width="29%" valign="top">core tablet</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.18</td>
<td width="29%" valign="top">crested blade</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.19</td>
<td width="29%" valign="top">cutting flake</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.20</td>
<td width="29%" valign="top">fabricator</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.21</td>
<td width="29%" valign="top">knife (flint)</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.22</td>
<td width="29%" valign="top">microburin</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.23</td>
<td width="29%" valign="top">microdenticulate</td>
<td width="53%" valign="top">serrated blade</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">serrated flake</td>
</tr>
<tr>
<td width="18%" valign="top">15.24</td>
<td width="29%" valign="top">notched flake</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.25</td>
<td width="29%" valign="top">ovate</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.26</td>
<td width="29%" valign="top">pick (flint)</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.27</td>
<td width="29%" valign="top">tranchet axe-sharpening</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.28</td>
<td width="29%" valign="top">retouched flake</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.29</td>
<td width="29%" valign="top">rod (flint)</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.30</td>
<td width="29%" valign="top">chopper (flint)</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.31</td>
<td width="29%" valign="top">adze (flint)</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.32</td>
<td width="29%" valign="top">roughout</td>
<td width="53%" valign="top">unfinished axe</td>
</tr>
<tr>
<td width="18%" valign="top"></td>
<td width="29%" valign="top"></td>
<td width="53%" valign="top">unfinished handaxe</td>
</tr>
<tr>
<td width="18%" valign="top">15.33</td>
<td width="29%" valign="top">cutting blade</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.34</td>
<td width="29%" valign="top">denticulate</td>
<td width="53%" valign="top"></td>
</tr>
<tr>
<td width="18%" valign="top">15.35</td>
<td width="29%" valign="top">combination tool</td>
<td width="53%" valign="top">scraper/knife</td>
</tr>
<tr>
<td width="18%" valign="top">15.36</td>
<td width="29%" valign="top">preform</td>
<td width="53%" valign="top">unfinished axe</td>
</tr>
</tbody>
</table>
<h4>References</h4>
<p>Bedfordshire County Council Archaeology Service<em>, The Bedfordshire Artefacts Typology</em>, (unpublished paper).</p>
<p>Royal Commission on the Historical Monuments in England, <em>Recording England&#8217;s Past,</em> <em>A Data Standard for the Extended National Archaeological Record</em>, 1993.</p>
<h4>Acknowledgements</h4>
<p>Thanks are due to Holly Duncan (Bedfordshire County Council Archaeology Service) for proof reading (and half rewriting) this article. The implementation of the program (to check names against period) is based upon information compiled by Dr Robin Holgate (Curator, Luton Museum Service), Holly Duncan and Carolyn Wingfield (formerly of Bedford Museum, now at Doncaster Museum). Any errors remain the responsibility of the author.</p>
<p align="right">Mark M<sup>c</sup>Call, Documentation Office, Luton Museum Service<br />
Wardown Park, Luton LU2 7HA<br />
(01582) 746750, Facsimile (01582) 746763</p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/1996/05/16/spring-meeting-museum-of-london-16-may-1996/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MCG Autumn Meeting 1995 report</title>
		<link>http://museumscomputergroup.org.uk/1995/11/10/mcg-autumn-meeting-1995-report/</link>
		<comments>http://museumscomputergroup.org.uk/1995/11/10/mcg-autumn-meeting-1995-report/#comments</comments>
		<pubDate>Thu, 09 Nov 1995 23:28:22 +0000</pubDate>
		<dc:creator>mia</dc:creator>
				<category><![CDATA[Archived Events]]></category>
		<category><![CDATA[Meeting report]]></category>
		<category><![CDATA[Meetings]]></category>

		<guid isPermaLink="false">http://museumsontheweb.org.uk/?p=313</guid>
		<description><![CDATA[Royal Botanic Gardens, Kew
The autumn 1995 meeting of the group took place at the Royal Botanic Gardens in Kew. We were treated to a very broad range of talks and demonstrations covering a wide selection of Kew&#8217;s operations.
First up, Ken Bailey explained the networking and hardware strategy at Kew, describing a dizzy range of impressive [...]]]></description>
			<content:encoded><![CDATA[<p>Royal Botanic Gardens, Kew</p>
<p>The autumn 1995 meeting of the group took place at the Royal Botanic Gardens in Kew. We were treated to a very broad range of talks and demonstrations covering a wide selection of Kew&#8217;s operations.</p>
<p>First up, Ken Bailey explained the networking and hardware strategy at Kew, describing a dizzy range of impressive hardware (8 Novell servers, more than 800 PCs, 24 Macs, Data General Aviion server, 4 Unix workstations, fibre optic cabling etc etc). This is supported by a team of 4 programmers and 4 support staff. PACE and VMark Universe are used for most system development.</p>
<p>Mark Jackson then described the development of a multimedia system for visitors. Multimedia Toolkit software has been used to develop this system which it is to be networked around the gardens.</p>
<p>Steve Ruddy demonstrated the KewScape mapping system which provides a graphic representation of the gardens and collections. Data is taken from Kew&#8217;s Living Collections Database of 89,000 accessions held on the DG and displayed on a site map on a portable screen-based data collection unit (Gridpad). The Gridpad is used in the gardens, the AutoLisp software allowing plant records to be updated. AutoCAD is used to record 30 layers of information, including services, buildings and vegetation.</p>
<p>Milan Svanderlik of the Media Resources department explained how Kew is using Kodak PhotoCD to archive and access images. A database of images is being created using Kodak&#8217;s Shoebox software.</p>
<p>After lunch, Ken Bailey and Steve Ruddy reported on Kew&#8217;s World Wide Web pages and how these have been authored. The present trial system has been compiled largely from existing publicity and promotional material, but longterm aims are to distribute scientific information and to give outside access to Kew&#8217;s databases. (Kew&#8217;s Home page is at http://www.rbgkew.org.uk).</p>
<p>Francis Cook then talked about terminology standards, including the Dictionary of Plant Names and Genera and the taxonomic standards working group.</p>
<p>The last speaker, Liz Dauncey, gave an excellent presentation on Kew&#8217;s prize-winning identification system for poisonous plants, PLATO. This expert system has been developed in conjunction with the National Poisons Unit for use by medical professionals in hospitals. Your Chairperson was nominated (thanks guys) to prise apart an evil-looking specimen and use the system to identify deadly nightshade (A. belladonna). She also lived to see another day . . .</p>
<p>After tea (and frantic handwashing), a panel discussion ranged widely over the publication and sale of information and training. Internet and the production of Web pages (inevitably?) featured strongly. Thank you to the panel members, most of whom were persuaded into action at very short notice.</p>
<p>Many thanks to Bill Loader and the staff at Kew for organising such a fascinating and wide-ranging day &#8211; and an excellent meal the night before.</p>
<p>Fiona Marshall</p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/1995/11/10/mcg-autumn-meeting-1995-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ask Sepasal!</title>
		<link>http://museumscomputergroup.org.uk/1986/11/20/ask-sepasal/</link>
		<comments>http://museumscomputergroup.org.uk/1986/11/20/ask-sepasal/#comments</comments>
		<pubDate>Thu, 20 Nov 1986 13:31:38 +0000</pubDate>
		<dc:creator>mia</dc:creator>
				<category><![CDATA[Archived Events]]></category>
		<category><![CDATA[Meeting report]]></category>
		<category><![CDATA[1986]]></category>
		<category><![CDATA[archive]]></category>
		<category><![CDATA[sepasal]]></category>
		<category><![CDATA[spring 1986]]></category>

		<guid isPermaLink="false">http://museumsontheweb.org.uk/?p=392</guid>
		<description><![CDATA[From &#8216;Archive 1996 &#8211; what were we up to 20 years ago?&#8217;, the Spring 1986 meeting item &#8216;Visit to Computer Section and demonstration of database systems (Sepasal)&#8217;.
ASK SEPASAL!
For the past three years the SEPASAL unit has been collating information about plants from the dry tropics that have been reported to be useful (in any way) [...]]]></description>
			<content:encoded><![CDATA[<p><strong>From &#8216;Archive 1996 &#8211; what were we up to 20 years ago?&#8217;, the Spring 1986 meeting item &#8216;Visit to Computer Section and demonstration of database systems (Sepasal)&#8217;.</strong></p>
<h2>ASK SEPASAL!</h2>
<p>For the past three years the SEPASAL unit has been collating information about plants from the dry tropics that have been reported to be useful (in any way) but that have not been commercially exploited on a large scale. Information regarding life forms habit, life span, toxicity, economic importance, uses, environmental requirements (soil pH, salinity, moisture, altitude, frost tolerance and rainfall range) and distribution have been obtained where possible, and the information has been computerised so that SEPASAL can operate as an enquiry unit.</p>
<p>So what kind of questions can you ask the SEPASAL database? The computer can display:-</p>
<p>1) a list of all the useful plants in a particular geographical region</p>
<p>2) a list of all the plants in the dry tropics that have been found to be reportedly useful for sand dune stabilisation (or famine foods or thatching or any of the 600 or so other uses recognised)</p>
<p>3) a list of plants that are found in a particular geographical region that also have a specified use or uses</p>
<p>4) a list of plants that we have recorded that are in a particular plant family or genus</p>
<p>5) questions regarding habitat requirements can also be formulated eg lists of plants which occur in dry, wet or aquatic habitats or plants which are frost or salt tolerant or plants with preference for alkaline soils may be obtained</p>
<p>6) similarly it displays lists of plants with particular life form characteristics eg epiphyte, climbing shrubs, etc.</p>
<p>7) more complex questions can also be posed which combine life form, habitat requirements, uses and distribution eg lists of unarmed, evergreen, non-toxic shrubs that are useful for browse and which occur in Somalia can be provided.</p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/1986/11/20/ask-sepasal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>1986 Autumn meeting</title>
		<link>http://museumscomputergroup.org.uk/1986/09/26/1986-autumn-meeting/</link>
		<comments>http://museumscomputergroup.org.uk/1986/09/26/1986-autumn-meeting/#comments</comments>
		<pubDate>Fri, 26 Sep 1986 09:30:00 +0000</pubDate>
		<dc:creator>mia</dc:creator>
				<category><![CDATA[Archived Events]]></category>
		<category><![CDATA[Event-Category]]></category>
		<category><![CDATA[Meeting report]]></category>

		<guid isPermaLink="false">http://museumsontheweb.org.uk/?p=310</guid>
		<description><![CDATA[Bristol Museum and Art Gallery
Agenda

[The c1996 (?) note on the original MCG site said: 'This is only a partial record: an initial paper plus certain figures. If any members have retained more from the day please let us know. Figures are linked where present.']
Documentation and computerisation in the Museum

Documentation&#8230;continued

General documentation procedures

Documentation project 1977-1981

Documentation project 1977-1981 [...]]]></description>
			<content:encoded><![CDATA[<p>Bristol Museum and Art Gallery</p>
<p>Agenda</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/1mcgtimetable.gif" alt="Timetable" /></p>
<p>[The c1996 (?) note on the original MCG site said: 'This is only a partial record: an initial paper plus certain figures. If any members have retained more from the day please let us know. Figures are linked where present.']</p>
<p>Documentation and computerisation in the Museum</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/2coppmcg.gif" alt="Report" /></p>
<p>Documentation&#8230;continued<br />
<img src="http://museumscomputergroup.org.uk/wp-content/uploads/3coppmcg.gif" alt="Report" /></p>
<p>General documentation procedures<br />
<img src="http://museumscomputergroup.org.uk/wp-content/uploads/4coppmcg.gif" alt="Documentation" /></p>
<p>Documentation project 1977-1981</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/5coppmcg600.jpg" alt="Documentation" /></p>
<p>Documentation project 1977-1981 continued&#8230;</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/6coppmcg.gif" alt="Documentation" /></p>
<p>Documentation project staffing and finance</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/7coppmcg.gif" alt="Documentation" /></p>
<p>Documentation project developments</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/8coppmcg.gif" alt="Documentation" /></p>
<p>Documentation project developments cont&#8230;</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/9coppmcg1.gif" alt="Documentation" /></p>
<p>Documentation project conclusions</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/10coppmcg.gif" alt="Documentation" /></p>
<p>References</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/11coppmcg.gif" alt="References" /></p>
<p>Figure 1 &#8211; Equipment</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/1siriusmcg.gif" alt="Equipment" /></p>
<p>Figure 2 &#8211; Software in use at Bristol</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/2siriusmcg.gif" alt="Software in use at Bristol" /></p>
<p>Figure 3 &#8211; Network plan for SIRIUS</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/3siriusmcg.gif" alt="Network" /></p>
<p>Figure 1 &#8211; Acquisition documentation flow</p>
<p><img src="http://museumscomputergroup.org.uk/wp-content/uploads/4siriusmcg.gif" alt="Documentation flow" /></p>
<p>NB 2009: if you find yourself transcribing this content, please consider copying and pasting it into a comment below so that everyone can benefit!</p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/1986/09/26/1986-autumn-meeting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A very brief guide to status</title>
		<link>http://museumscomputergroup.org.uk/1986/04/11/a-very-brief-guide-to-status/</link>
		<comments>http://museumscomputergroup.org.uk/1986/04/11/a-very-brief-guide-to-status/#comments</comments>
		<pubDate>Fri, 11 Apr 1986 15:06:33 +0000</pubDate>
		<dc:creator>mia</dc:creator>
				<category><![CDATA[Meeting report]]></category>

		<guid isPermaLink="false">http://museumsontheweb.org.uk/?p=420</guid>
		<description><![CDATA[From &#8216;Archive 1996 &#8211; what were we up to 20 years ago?&#8217;, the Spring 1986 meeting item &#8216;Use of Status package on system so far developed&#8217;.
Spring 1986 meeting
Databases: STATUS, GENUS INDEX 
A VERY BRIEF GUIDE TO STATUS
STATUS is an Information storage and retrieval package called by typing ISR on the computer. Within Status there are [...]]]></description>
			<content:encoded><![CDATA[<p><strong>From &#8216;Archive 1996 &#8211; what were we up to 20 years ago?&#8217;, the Spring 1986 meeting item &#8216;Use of Status package on system so far developed&#8217;.</strong></p>
<h1>Spring 1986 meeting</h1>
<p><strong>Databases: STATUS, <a href="http://www.museumscomputergroup.org.uk/meetings/archive/archive1986-05-genusindexl.shtml">GENUS INDEX</a> </strong></p>
<h3>A VERY BRIEF GUIDE TO <strong><span>S</span>TATUS</strong></h3>
<p>STATUS is an Information storage and retrieval package called by typing ISR on the computer. Within Status there are a number of different databases, which can all be accessed from any terminal.</p>
<p>Each database is divided into chapters. In Status each record is called an article. Each article is divided into Named Sections which may contain free text and/or Keyed Fields, and has an area designated as the title. Within a database, you can see the chapters by typing INDEX and the Named Sections and Keyed Fields by typing STRUCT (for structure).</p>
<p>Help on any command may be obtained from within Status by typing HELP command, eg HELP DISPLAY.</p>
<h3>SEARCHING</h3>
<p>1 . Status does not recognise any difference between capitals and lowercase letters; when searching you may use either.</p>
<p>2. To find an article or articles you want the basic commands are Q word? or SUBQ word?, where word is any word or phrase which will occur in the required articles. Q searches the Whole database while SUBQ dearths through articles already found by a prior Q or SUBQ command.</p>
<p>Examples:</p>
<ul>
<li>Q Quercus?</li>
<li>SUBQ Mexico ?</li>
</ul>
<p>3. More complicated searches may be done by using the characters &#8216; + &#8216; ( and ) &#8216;-&#8217; (but not) or &#8216;,&#8217; (or)</p>
<p>Examples:</p>
<ul>
<li>Q Australia + New Zealand ?</li>
<li>Q Australia &#8211; New Zealand ?</li>
<li>Q Australia , New Zealand ?</li>
</ul>
<h3>DISPLAYING</h3>
<p>4. To see the articles retrieved type D n, where n is a list of the articles to be displayed. Omitting n will display the current article (usually the first on the retrieved list). ALL will display them all.</p>
<p>Examples:</p>
<ul>
<li>D</li>
<li>D ALL</li>
</ul>
<p>5. The command T will display the title only; it is used in the same way as D.</p>
]]></content:encoded>
			<wfw:commentRss>http://museumscomputergroup.org.uk/1986/04/11/a-very-brief-guide-to-status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

