Cool Tools In the Developers Toolbox - getRIF-CS API

Video thumbnail (Frame 0) Video thumbnail (Frame 275) Video thumbnail (Frame 710) Video thumbnail (Frame 1763) Video thumbnail (Frame 3024) Video thumbnail (Frame 3153) Video thumbnail (Frame 3266) Video thumbnail (Frame 3353) Video thumbnail (Frame 3574) Video thumbnail (Frame 3753) Video thumbnail (Frame 4270) Video thumbnail (Frame 4608) Video thumbnail (Frame 5304)
Video in TIB AV-Portal: Cool Tools In the Developers Toolbox - getRIF-CS API

Formal Metadata

Title
Cool Tools In the Developers Toolbox - getRIF-CS API
Title of Series
Author
License
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.
Identifiers
Publisher
Release Date
2014
Language
English

Content Metadata

Subject Area
Abstract
A spotlight on the ANDS Developer Tool Box -- getRIF-CS API Gain powerful access to the data in the ANDS Collection Registry. This short video provides a brief overview of the useful search and retrieval capabilities of the getRIFCS API.
Service (economics) Process (computing) Software developer Software developer Computer architecture
Windows Registry Addition Service (economics) GUI widget Open source Information Software developer Software developer Connectivity (graph theory) 1 (number) Limit (category theory) Repository (publishing) Personal digital assistant Software Order (biology) Cuboid Quicksort Functional (mathematics)
Windows Registry Group action Service (economics) Software developer GUI widget Electronic mailing list Content (media) Windows Registry Area Web 2.0 Subset Latent heat Repository (publishing) Address space Row (database)
Number Service (economics) Service (economics) Software developer Debugger Maxima and minima Internet service provider Convex hull Diagram Windows Registry
Point (geometry) Metropolitan area network Service (economics) Execution unit Raw image format Service (economics) Software developer Maxima and minima Menu (computing) Personal digital assistant Maß <Mathematik> Descriptive statistics Linear map Flag
Windows Registry Web page Service (economics) Execution unit Email Service (economics) Link (knot theory) Key (cryptography) Software developer Maxima and minima Windows Registry Uniform resource locator Self-organization
Execution unit Inheritance (object-oriented programming) Service (economics) Hoax GUI widget Dependent and independent variables Software developer Software developer Programmable read-only memory File format Bit Parameter (computer programming) System call Hypermedia Internet forum Set (mathematics) Strategy game Quicksort Videoconferencing Table (information) YouTube Exception handling Formal grammar God
thanks everybody for turning up y'all been here business analyst in the
services team so the developers did a great job over six months of plug-and-play architecture that we can extend quite easily and quite quickly
one of the outcomes of that was really these plug-and-play widgets and services that we can offer through this developer tool box and also going forward we cannot offer additional ones as open source tools that people can extend and also feed back into our repository as well and the services themselves sort of
expose a lot of the powerful components behind the registry and research data Australia to external developers so these are things like searches and vocabulary services to pull information out about vocabularies that we've got published obviously external users can use them to tap in to explore the israelian research data Commons or research data Australia and the services themselves are used in a lot of the case to underpin Nan's widgets so as I said before to developer as sort of get the limits of a widget where they'd like to extend it they can actually look at these services themselves and either extend that which it order fulfilled their own widgets by these services physically zar quite well-documented the
first service is the get Bruce es api and this is just a way to really get access to the contents of the collections registry itself via the service you can perform quite complex searches of the registry to pull back specific records or records in a specific group based on specific subjects and things like that now this service itself pulls out riff CS XML so it's useful to people that understand roofs es XML or using it in their own repository it's also one of the uses is obviously to populate a pick lists or a lookup service so there may be um again in a repository people are doing the relationships to roof co2 records and they can basically do a populated peak list of say collections or parties from a certain institution or all grants from a specific year or something similar to that so again just the address research
data Australia that I answered all that a you fought / 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 dashon's book how they work there's obviously the
description in the use cases for each of the services how people might want to implement them in the useful points breath 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 a a pik that they pass when they call them services and that's just the way of us knowing and identifying who's actually using the services you don't have to be a user with a lock on to the registry you can just click the link and it will
take you to a publicly accessible page where you fill out the organization contact email and why you want to basically use the API key and you click register and it will write down 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 can be passed to the services themselves and again the developers will understand that if they don't they can get in contact by the community forum there's a couple in some of the services they're a little bit trickier there's some sort of a fake use 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 of god
Feedback