Cool Tools In the Developers Toolbox - Research Grants API
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Australian National Data Service (ANDS)
Facilitate richer data connections through the ANDS open source Research Grants API. This video will give you a brief overview of the API and how it could be used to provide your users with the ability to link their data directly to metadata records for published grants.
 Thanks everybody for turning up. Joel Ben here, business analyst in the services team. The research grants API, which is one that's sort of been in the making for a little while, that obviously to encourage users to really link their data to activities or grants themselves to create that mesh in the data commons. We've been working with the NHMRC to get brand information in Research Data Australia for the last 12 months or so. That has been, moving, we've actually got information up into 2011. And this API is a way of actually searching those grants within Research Data Australia and pulling back information about them. So again, in data capture tools or in description tools, when people are recording their data collections, they can actually provide users with a pick list to go and say, yes, this is related to this research grant. Another use case for it would be to say finding all the grants that have been given to specific institutions or related to specific individuals themselves. So again, just the address, researchdataaustralia.au.au for slash developers. The web services themselves, they're not as pretty because there's no real fancy front end to them. There are little explanation diagrams for each, I think nearly all of the services that we have just showing sort of how they work. There's obviously the description and the use cases for each of the services, how people might want to implement them and the use of the points about them. As you can see here, before you start, the one thing to note about the services themselves is that any developer that wants to use them actually has to register for an API key that they pass when they call them the services. And that's just a way of us knowing and identifying who's actually using the services. You don't have to be a user with a log onto the registry. You can just click the link and it'll take you to a publicly accessible page where you fill out the organization, the contact email and why you want to basically use the API key. And you click register and it will basically right there and then generate your key to pass with the service calls. In much the same way as the widgets, we have tables containing all the parameters that could be passed to the services themselves. And again, the developers will understand that and if they don't, they can get in contact via the community forum. There's a couple of, in some of the services, they're a little bit tricky. There's some FAQs or common questions about the services just to help out. And a couple of example uses of working service calls. And that's pretty much all I've got.
 Thanks everybody for turning up. Joel Ben here, business analyst in the services team.  The research grants API, which is one that's sort of been in the making for a little while,  that obviously to encourage users to really link their data to activities or grants themselves  to create that mesh in the data commons. We've been working with the NHMRC to get  brand information in Research Data Australia for the last 12 months or so. That has been,  moving, we've actually got information up into 2011. And this API is a way of actually  searching those grants within Research Data Australia and pulling back information about them.  So again, in data capture tools or in description tools, when people are recording their data  collections, they can actually provide users with a pick list to go and say, yes, this is related to  this research grant. Another use case for it would be to say finding all the grants that have been  given to specific institutions or related to specific individuals themselves. So again,  just the address, researchdataaustralia.au.au for slash developers. The web services themselves,  they're not as pretty because there's no real fancy front end to them. There are little explanation  diagrams for each, I think nearly all of the services that we have just showing sort of how  they work. There's obviously the description and the use cases for each of the services,  how people might want to implement them and the use of the points about them. As you can see here,  before you start, the one thing to note about the services themselves is that any developer that  wants to use them actually has to register for an API key that they pass when they call them  the services. And that's just a way of us knowing and identifying who's actually using the services.  You don't have to be a user with a log onto the registry. You can just click the link and it'll  take you to a publicly accessible page where you fill out the organization, the contact email and  why you want to basically use the API key. And you click register and it will basically  right there and then generate your key to pass with the service calls. In much the same way as  the widgets, we have tables containing all the parameters that could be passed to the services  themselves. And again, the developers will understand that and if they don't, they can get in contact  via the community forum. There's a couple of, in some of the services, they're a little bit  tricky. There's some FAQs or common questions about the services just to help out. And a couple  of example uses of working service calls. And that's pretty much all I've got.
Research_Grants_API_-_Cool_Tools_in_the_Developers_Toolbox_2_0_2939.png Research_Grants_API_-_Cool_Tools_in_the_Developers_Toolbox_2_2940_3155.png Research_Grants_API_-_Cool_Tools_in_the_Developers_Toolbox_2_3156_4224.png