I'll pitch in on the API fanclub..
At the BFI we make extensive use of our Adlib API, which I can configure and extend myself (it's reasonably simple to do with reference to the documentation and some advice from Adlib), to deliver our collections data and associated descriptive data to a broad range of platforms and operational points:
- the BFI Collections Search interface which is a straightforward search interface against the collections data
- the BFI website's Explore Film area, offering a non-collection dataset with editorial enrichment, posters, stills, etc
- the BFI Player VOD platform: all data about the films is delivered from our collections management system via API (although not the moving image assets I should emphasise)
- EIDR: I achieve registration of moving image records by setting up workflows to retrieve data from our API and deliver to EIDR's submissions API, in semi-automation models
- commercial customers: I achieve delivery of data to consumers by API
- staff application development: our most engaged curatorial staff actually develop their own VBA processes to call our API and retrieve data for workflow management / reporting - the efficiencies to be gained are substantial, as the API enables automation and a programmatic approach
I can't really imagine how these could be scaled using static data exports, it would certainly increase the overheads dramatically. So API functionality allows them to be automated, and scaled, with minimal labour overheads.
Finally, regarding the skills requirement: although it's true that skills are required, I believe APIs could be demystified with a very quick practical demonstration of how to set them up and maintain them, by the suppliers of the major systems. As a day-to-day user of the Adlib API, I'd be happy to help in any way I can, for anyone interested in learning more about that.
Stephen McConnachie
BFI Collections Information Data Manager
> On 12 Feb 2014, at 16:47, "Bleck, Helen" <[log in to unmask]> wrote:
>
> Hi,
>
> Helen
> Helen Bleck
> Heritage Resources Development Officer (John Gray Centre, Haddington)
> www.johngraycentre.org; www.facebook.com/JohnGrayCentre; @JohnGrayCentre
>
> -----Original Message-----
> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Kevin Bacon
> Sent: 12 February 2014 13:52
> To: [log in to unmask]
> Subject: Re: [MCG] Cross-organisation collaborations around digital collections
>
> Hello Jude,
>
> We're also going down the API route, working with Orangeleaf to deliver this. As a partner in The Keep, a new historical resource centre that's opened in East Sussex (http://www.thekeep.info/), some of our local history collections data is already available via their API: http://www.thekeep.info/api/. A lot more of our data from across our other collections will be available very soon.
>
> We also use Mimsy XG. Very simply, we export the selected data as XML and upload that to Orangeleaf's Collections Base system which provides the API.
>
> Cheers,
>
> Kevin
>
> Kevin Bacon
> Digital Development Officer
> Royal Pavilion and Museums
> 01273 292817
> [log in to unmask]
> http://www.brighton-hove-rpml.org.uk
>
> Twitter: @brightonmuseums
> Facebook:www.facebook.com/royalpavilionandbrightonmuseums
> -----Original Message-----
> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Dicken, Jude
> Sent: 12 February 2014 09:45
> To: [log in to unmask]
> Subject: Re: [MCG] Cross-organisation collaborations around digital collections
>
> Hello Andrew,
>
> Your API-approach at V&A I find really interesting - thanks for explaining it so clearly.
>
> I'm in the process here of designing a project for 2014/15 on how we improve delivery of our own 'collections online' through iMuseum (www.imuseum.im), key to this is making our data & images more nimble in terms of web delivery - we don't want to spend money on a re-design only to want to reconfigure it in 2yrs time as audience demand, web-style changes. API-approach sounds like it would put us in the driving seat. Did V&A develop their API in-house or did you (are there) developers already doing this for museums/heritage?
>
> We use MimsyXG as our collections management system - the API just draws data from it? (We currently use a bespoke CMS.)
>
> Are other museums already using API to deliver their collections online? I'd be keen to hear of them.
>
> Our challenge is to make our collections data not only feasible through a home 'collections online' site but ready for all other online channels - we already export data to Historypin, Magnolia Box, Your Paintings, but as data extractions. My aim is to get our collections data appearing on Wikimedia, etc, and able to respond as quick digital pop-up themed exhibitions (fully searchable) in support of actual exhibitions. Is API the way forward?
>
> Cheers again Andrew - illuminating.
>
> Jude.
>
> Jude Dicken (Miss)
> Documentation Officer
> Manx National Heritage
> Eiraght Ashoonagh Vannin
>
> Manx Museum, Douglas, Isle of Man, IM1 3LY
> t: +44 (0) 1624 648071
> e: [log in to unmask]
> w: manxnationalheritage.im
> manxheritageshop.com
>
> facebook.com/manxnationalheritage
> twitter.com/manxheritage
> flickr.com/groups/_mnh
> vimeo.com/manxheritage
>
> -----Original Message-----
> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of Andrew Lewis
> Sent: 11 February 2014 09:55
> To: [log in to unmask]
> Subject: Re: [MCG] Cross-organisation collaborations around digital collections
>
> Hi Owen,
>
> interesting work.
>
> Here at the V&A, we have an API-based approach. This assumes that for digital services, the first thing you should do with content is convert it into web-portable data. Then you build services from the data. Our main use of this is to build our web features (although not the only one, we have some digital gallery labels based on it too).
> Our collections API was launched in 2008 and in 2009 we relaunched Search the Collections based on this. Although that service is not collaborative in itself, the important principle is that the front end service (managed by Digital Media) is decoupled from the back end asset management process (in this case, the collections management system updated by expert museum staff) - if you like, our collections data is "plugged in" to Search the Collections. The API is the enabling thing.
> However because web service and internal data management are decoupled, the same data can be plugged into any other service as required (and we do this is in at least 5 of our own services)
>
> So, open API exist, collaboration is, in principle fairly easy and can be rapid. Starting with an identifiable audience need, collaboration can be simply about designing a front end service to meet that need, and that plugs in data from more than one organisation. As the Meerkat says
> - simples!
>
> This model is similar to the interesting stuff British Museum are looking at with Linked Open data in RDF. They both use a data standard (Spectrum or CIDOC CRM) and make it web accessible (in our case a structured API, in their case a SPARQL end point)
>
> This model is good. Where a new user need is identified, you don't change the internal process or data service, just develop a new front end service. This is the model Twitter and Facebook and loads of others use.
>
> This differs from models that require organisations to upload all their data to a central CMS. This is double entry and creates a new resource data management cost per collaboration.
>
> So if you put all your data into collaborations such as Google Art Project or MyPaintings and so on, the decision to be made is whether you can afford to update each additional extra resource. If the end service makes it worthwhile, then it can be worth it, but the risk is that if the service is not what is required by users, then changing it means migrating data.
>
> As usual, other musings on this strategy and other such things are on the Digital Media blog. The Digital Explorer map is the best example of a new service built on two existing data sources. In that case to address changes in user uptake of tablets and mobile devices.
> http://www.vam.ac.uk/b/blog/digital-media/tablet-optimised-digital-map
>
> Good luck. sound very interesting
>
>
> Andrew Lewis
> Digital Content Delivery Manager
>
> Digital Media department
> Victoria and Albert Museum
> South Kensington
> London SW7 2RL
>
> 020 7942 2373
> [log in to unmask]
> Digital Media blog: www.vam.ac.uk/digital http://linkd.in/andrewlewis @rosemarybeetle ( https://twitter.com/rosemarybeetle )
>
> Andrew Lewis
> Digital Content Delivery Manager
>
> Digital Media department
> Victoria and Albert Museum
> South Kensington
> London SW7 2RL
>
> 020 7942 2373
> [log in to unmask]
> Digital Media blog: www.vam.ac.uk/digital http://linkd.in/andrewlewis @rosemarybeetle ( https://twitter.com/rosemarybeetle )
>
>
>
>>>> MCG automatic digest system <[log in to unmask]> 11/02/2014
> 00:00 >>>
> There are 24 messages totaling 5180 lines in this issue.
>
> Topics of the day:
>
> 1. MCG Digest - 7 Feb 2014 to 9 Feb 2014 (#2014-30)
> 2. Seeking sound walk advice (2)
> 3. Cross-organisation collaborations around digital collections (17)
> 4. Open access Wi-fi in Museum (3)
> 5. Invitation to Darwin or Bust
>
> ****************************************************************
> 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/
> ****************************************************************
>
> ----------------------------------------------------------------------
>
> Date: Sun, 9 Feb 2014 21:17:08 -0800
> From: Rich Cherry <[log in to unmask]>
> Subject: Re: MCG Digest - 7 Feb 2014 to 9 Feb 2014 (#2014-30)
>
> Owen,
>
> You might want to chck this out:
> http://www.balboapark.org/bpoc/blog/balboa-park-commons-launches-more-20000-digitized-materials-seven-san-diego-museums#.UvhglfldWSo
>
>
> Rich
>
>
>> On Sun, Feb 9, 2014 at 4:01 PM, MCG automatic digest system < [log in to unmask]> wrote:
>>
>> There are 2 messages totaling 100 lines in this issue.
>>
>> Topics of the day:
>>
>> 1. Cross-organisation collaborations around digital collections
>> 2. Seeking sound walk advice
>>
>> ****************************************************************
>> 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/
>> ****************************************************************
> ----------------------------------------------------------------------
>>
>> Date: Sun, 9 Feb 2014 11:02:31 +0000
>> From: Owen Stephens <[log in to unmask]>
>> Subject: Cross-organisation collaborations around digital
> collections
>>
>> I'm currently writing a web resource about improving
> 'discoverability' of
>> digital collections as part of a Jisc project. The resource is meant
> to
>> give small pieces of 'actionable' advice looking at a wide range of
> aspects
>> - SEO, UX, metadata schemas, data formats, APIs, collaboration with
> others
>> etc. etc. The things being recommended are based on looking at a
> range of
>> digitisation/digital collection projects have done successfully.
>>
>> For each thing recommended I try to include:
>>
>> How it can help improve discoverability A broad idea of cost
>> Skills/knowledge required What relevant measures of success might be
>> Real life examples Links to more information
>>
>> I'm looking for some help on one of the recommendations, which is to
>> "Collaborate with partner organisations (e.g. schools, museums, other
> HE
>> institutions) to exploit your digitised content". An example of this
> is how
>> the Royal Maritime Museum and the University of Cambridge have
> collaborated
>> on the Board of Longitude Archive - with Cambridge hosting the
> archive, and
>> the Royal Maritime Museum contributing material, expertise and
>> building/promoting classroom resource packs which draw on the
> archive
>> materials.
>>
>> I'd be interested in other examples of collaborations around digital
>> collections if anyone can supply them. However, what I'm really
> struggling
>> to find is any more information I can link to that might guide
> institutions
>> interested in embarking on collaborations of this type. If anyone
> has
>> pointers on examples, or guides to, or papers/articles on, starting
> and
>> making a success of such collaborations then I'd be very interested.
>> Generally I'm trying to link to freely available online resources
> for
>> further information.
>>
>> Thanks
>>
>> Owen
>>
>>
>> Owen Stephens
>> Owen Stephens Consulting
>> Web: http://www.ostephens.com
>> Email: [log in to unmask]
>> Telephone: 0121 288 6936
>
> Club to Catwalk: London Fashion in the 1980s Until 16 February 2014 at V&A South Kensington
>
> FINAL WEEKS
> Book now on www.vam.ac.uk/clubtocatwalk
>
> See the exhibition for free if you join as a V&A Member www.vam.ac.uk/members
>
> War Games
> Until 9 March 2014 at V&A Museum of Childhood Admission free
>
> Keep in touch
> Sign up for V&A e-newsletters www.vam.ac.uk/signup Become a fan on Facebook.com/VictoriaandAlbertMuseum (http://www.facebook.com/VictoriaandAlbertMuseum ) Follow us on Twitter.com/V_and_A ( http://www.twitter.com/V_and_A )
>
> ****************************************************************
> 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/
> ****************************************************************
>
>
>
> Isle of Man. Giving you freedom to flourish
>
>
> WARNING: This email message and any files transmitted with it are confidential and may be subject to legal privilege. You must not copy or deliver it to any other person or use the contents in any unauthorised manner without the express permission of the sender. If you are not the intended addressee of this e-mail, please delete it and notify the sender as soon as possible.
>
> No employee or agent is authorised to conclude any binding agreement on behalf of any of the Departments or Statutory Boards of the Isle of Man Government with any party by e-mail without express written confirmation by a Manager of the relevant Department or Statutory Board.
>
> RAAUE: S'preevaadjagh yn çhaghteraght post-l shoh chammah's coadanyn erbee currit marish as ta shoh coadit ec y leigh. Cha nhegin diu coipal ny cur eh da peiagh erbee elley ny ymmydey yn chooid t'ayn er aght erbee dyn kied leayr veih'n choyrtagh. Mannagh nee shiu yn enmyssagh kiarit jeh'n phost-l shoh, doll-shiu magh eh, my sailliu, as cur-shiu fys da'n choyrtagh cha leah as oddys shiu.
>
> Cha nel kied currit da failleydagh ny jantagh erbee conaant y yannoo rish peiagh ny possan erbee lesh post-l er son Rheynn ny Boayrd Slattyssagh erbee jeh Reiltys Ellan Vannin dyn co-niartaghey scruit leayr veih Reireyder y Rheynn ny Boayrd Slattyssagh t'eh bentyn rish.
>
> ****************************************************************
> 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/
> ****************************************************************
>
> Notice to recipient:
> The information contained in this electronic mail message is intended only for the use of the individual to whom it is addressed and may contain information which is privileged and confidential, the disclosure of which is prohibited by law.
> If the reader of this message is not the intended recipient, please note that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please notify the sender immediately.
> Thank you in anticipation of your co-operation.
>
> You can visit our website at http://www.brighton-hove.gov.uk
>
> Please consider the environment, only print out this email if absolutely necessary.
>
> Please Note: Both incoming and outgoing Emails may be monitored and/or recorded in line with current legislation.
>
> ****************************************************************
> 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/
> ****************************************************************
>
> Growing Our Economy – our plan to build a more prosperous East Lothian
> Visit: www.eastlothian.gov.uk/workingtogether
> **********************************************************************
> Email Disclaimer - East Lothian Council
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the sender and ensure it is deleted and not read copied or disclosed
> to anyone else. It is your responsibility to scan this email and any
> attachments for computer viruses or other defects. East Lothian
> Council do not accept liability for any loss or damage which may
> result from this email or any files attached. Email is not secure and
> can be intercepted, corrupted or amended without the knowledge of the
> sender. East Lothian Council do not accept liability for errors or
> omissions arising as a result of interrupted or defective transmission.
> **********************************************************************
>
> ****************************************************************
> 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/
****************************************************************
|
