Kia ora DigitalNZ API Developers,
We are currently working on a Commercial Use API Pilot and we'd love your feedback on the draft terms of use.
The pilot will be a new API that will make some participating content partners' metadata available for use in commercial endeavours. This means that you would be able to use the API to make apps that can be sold in the app stores. It also means that the metadata can be included in library subscription services (such as Primo, Summon and EBSCO Discovery Services). There may also be other commercial uses that we just haven't thought of yet.
Three organisations have signed up for the pilot, University of Auckland, NZ Electronic Text Collection and the Ministry of Culture and Heritage. We'd love to have a few more content partners joining them, so we're doing a bit more of a push at the moment to get more on board.
I've attached the draft Commercial Use Developers' API Terms. We are keen for feedback on them. Are they workable for you? We know there's a couple of areas that need tweaking, but we're interested in hearing what you think so we can ensure we've got everything covered.
*Are you going to the National Digital Forum? Come see us*
The DigitalNZ Team will again be at the National Digital Forum ( http://www.ndf.org.nz ). We'll have a stand, so do come and visit. But also we’d love to see you all for breakfast on Day 2, (7.45 – 8.50am, Wed, 21 Nov). We’ll give you an update on what we’ve been up to and what we’d like to do next. We also want to hear what you think we should be doing! We need to gather up RSVPs so we can make sure there is enough coffee, juice, bagels and pastries for you all. So if you can make it please RSVP here:http://digitalnz.wufoo.com/forms/digitalnz-breakfast-at-ndf/
Chris McDowall
Hi Paul,
Thanks for this… some good questions. A couple of quick points which may help any discussion:
Firstly, we see this licensing option as a stepping stone. We haven't suggested a traditional creative commons licence because pilot partners wanted the option of requiring data users to refresh the metadata on request. CC licences are irrevocable, and don't provide that option. The approach we are piloting means that partners can help us set requirements, can opt in to share their metadata commercially via their DigitalNZ agreement, and then opt out again later if they change their mind. We see it as a safe option that people can try. I certainly would still encourage organisations to think about permanently licensing data for commercial reuse… but we recognise that everyone will have different views on this. We didn't want to force people to adopt CC or ODC unnecessarily if they weren't ready… and this allows us to support both those who want try this out (through a DigitalNZ agreement) or make a permanent release of their metadata (through licensing something on their own).
Secondly, you are totally right in saying that the large aggregation services may want big chunks of data, as opposed to just API access. The licensing agreement above will apply to the data, regardless of the delivery mechanism. We plan to roll out the API version first because we already have that in play, but the intention is to also develop a large data download feature that would better fit other needs. Possibly enabling OAI-PMH as a delivery mechanism, but we still have to figure this out. Keep in mind also that our defacto standard is Dublin Core because the DigitalNZ material comes not just from libraries but museums, websites, and all manner of non-standardised environments.
I think it is fair to say we have some way to go before figuring this all out. This small scale pilot should help us learn about what works and what doesn't. I'd certainly encourage others to get involved in the pilot if they want to know more, or help us figure this out. Behind this is the idea that we can encourage more use of NZ collections by letting commercial entities use the metadata… and that is also something we are trying to test here.
Cheers,
Andy
Manager, DigitalNZ
National Library of New Zealand