Cool Tools for Easy Rich Collections Descriptions - getExRif API

Video thumbnail (Frame 0) Video thumbnail (Frame 2138) Video thumbnail (Frame 2203) Video thumbnail (Frame 2305) Video thumbnail (Frame 2383) Video thumbnail (Frame 2541) Video thumbnail (Frame 2705) Video thumbnail (Frame 2870) Video thumbnail (Frame 3445) Video thumbnail (Frame 3789) Video thumbnail (Frame 3967) Video thumbnail (Frame 4024)
Video in TIB AV-Portal: Cool Tools for Easy Rich Collections Descriptions - getExRif API

Formal Metadata

Cool Tools for Easy Rich Collections Descriptions - getExRif API
ANDS Developers Toolbox
Title of Series
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.
Release Date

Content Metadata

Subject Area
A spotlight on the ANDS Developer Tool Box -- getExtRif API The getExtRif API provides powerful access to the contents of the ANDS Collections Registry, much like the getRIFCS API. The important difference is that getExtRif includes an additional non-RIFCS element called -extRif:extendedMetadata-. During the processing of new records in the ANDS Registry, this element is populated with additional metadata about the record content and its context. This video gives a brief introduction to Extended RIF-CS (ExtRif) and the getExtRif API.
Windows Registry Context awareness Service (economics) Key (cryptography) Information Image resolution Transformation (genetics) Digitizing Data storage device Content (media) Code Windows Registry Connected space Uniform resource locator Inclusion map String (computer science) Google Maps Information Extension (kinesiology) Row (database) Geometry
Execution unit Web service Blog Software developer GUI widget Windows Registry Address space
Service (economics) Open Archives Initiative Debugger Internet service provider Menu (computing) Coma Berenices Hill differential equation Diagram Windows Registry
Point (geometry) Service (economics) Personal digital assistant Descriptive statistics
Windows Registry Web page Service (economics) Email Service (economics) Link (knot theory) Key (cryptography) Software developer Self-organization Menu (computing) Windows Registry
Root Service (economics) Software developer Computer cluster Videoconferencing YouTube System call God
Inheritance (object-oriented programming) Hypermedia Strategy game Exception handling
thanks everybody for turning up y'all been here business analyst in the services team they get X roof API again it's another one which pulls information out of the registry it's very similar to the get roofs es api but it differs in a way that it pulls back extended riff and the extended roof is basically when records are ingested into the registry we do some transformations and enriching to those records too for example when things come in with the aims at SRC fo our codes which is the six digit codes we actually convert them to the string literal and store that in the X roof spatial that loans and things like that coordinates we actually convert them to a geometry that's compatible with google maps and the connections themselves when we get a key in the roof CS and the relationship we actually go and resolve that to a person's name I think the status is well title and also we store up to the information about when the record came in and out of the registry which we can use later on in searches and this is this information is obviously really useful for other people that don't necessarily completely understand what's in the roof CS itself's of the data within the roof CS I mean if you picked up a piece of roof CS and your didn't quite know what I said if I was you wouldn't know what that six digit was going to convert to so the extended roof CS is going to be useful to some people so again just the
address research data Australia that I
answered all today 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 and 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 development 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 log onto 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 basically right there and then generate your key to pass with the
service course and a couple of example uses of working service calls and that's
pretty much all of God