 |
 |
Nick, or anyone else. We are looking at the XML publication of Museum catalogues, and are interested in any existing schema out there. I have seen the CIMI/Spectrum schema, but MIDAS is new to me. Can anyone point me to some more information about MIDAS (pref. in a non-XML format, which is all I can find at the moment). Many thanks, Matthew -------------------------------- New Media Content Manager Department of Learning and Information The British Museum www.thebritishmuseum.ac.uk direct line: +44 (0)20 7323 8169 -----Original Message----- From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Nick Case Sent: 04 May 2005 10:38 To: [log in to unmask] Subject: Re: Is anyone using OAI with exports from collections databases? Hi Mia Oxford ArchDigital (OAD) is currently involved in a large-scale EU initiative called BRICKS that has OAI-PMH at its core for distributing and harvesting metadata above collections. The UK team leader is the MLA. In addition to this, the advent and adoption of the MIDAS XML standard for archaeological heritage means that our primary HER/SMR software suite must have so-called 'XML-connectors' that allow admins to import and export XML data to and from relational databases. All collections and content management systems will have these in the next year or two. The good news is that there are existing tools to help you do this. If the application is in .NET, Microsoft has a suite of XML-based tools; if you are based on open source, or vendor-neutral, technologies (as OAD is), there is a freely available application called XMLDBMS [http://www.rpbourret.com/xmldbms/] that allows you to transform data between a variety of database back-ends and XML. You can also use a range of freely-available tools that dump content straight to OAI, but their usability depends on your infrastructure and collections database. The fist place to look is http://www.openarchives.org/tools/tools.html which list a range of tools for building OAI connectors, many of them free. The bad news is that the process of translating this data between XML and DBMS cannot be done with a few clicks of the mouse, and therefore you usually always have to get a developer on board to help you build a connector, if your application does not support it natively. Hope that helps Nick Case Managing Director Oxford ArchDigital 27 Park End Street Oxford OX1 1HU Tel: ++44-1865-793043 Web: http://oxarchdigital.com Ridge, Mia wrote: > Dear all, > > We are involved in a major digitisation project titled Exploring 20th Century London. This is an attempt to integrate the collections databases of four museums across London, and then make this aggregated data available to search on a website. > > We have looked at different methods of sharing data - Z39.50, OAI etc and have decided to go with the OAI-PMH (Open Archives Initiative - Protocol for metadata harvesting - http://www.openarchives.org/). > > In order for the Museum of London to contribute records to the project, we need to export data out of Multi MIMSY, using an agreed schema. At the moment we intend to use an extension of the DC.Culture schema. > > We also need to be able to export records from AdLib, MUSIMS and CALM. > > Does anyone have any experience working with OAI or other XML-based exports from collections databases? > > Best regards, > > Mia > > > Mia Ridge > Database Developer, Museum Systems Team Museum of London Group > Mortimer Wheeler House > 46 Eagle Wharf Road > London. N1 7ED > Tel: 020 7410 2205 > Fax: 020 7410 2201 > Email: [log in to unmask] > www.museumoflondon.org.uk > > The London Look: Fashion from street to catwalk. Extended until 10 > July 2005 Special web feature: www.museumoflondon.org.uk/londonlook > _____________________________________ Africa at the British Museum throughout 2005 http://www.thebritishmuseum.ac.uk/africa05 > Ground Force: the last garden ever > Views from Africa: encounters with Europe Music, trails and half-term > events > Mummy: the inside story history uncovered, in 3 dimensions Tree of > Life sculpture, from decommissioned guns _____________________________________