Delta processing - how to know what's changes to integrate

Is there a call that could be made to the API to retrieve a list of changes made from a given date?

When changes are made to Aristotle, are these deltas sent to a queue of some sort that can be accessed?

I really would like a simple way of integrating Aristotle with other tools making use of metadata definitions. When something of interest is updated, I’d like a way of finding out without needing to interrogate the entire content of Aristotle and sorting out the wheat from the chaff.

Whoops… I wrote the title of that post in a rush. Apologies for the grammar crimes :roll_eyes:

There’s no edit capability to fix poorly worded titles once they’re posted :crazy_face:

Hey @Michael this is a great suggestion.

At the moment we don’t have an API endpoint for only getting recently changed metadata items. We are constantly improving the API and this is an easy suggestion for us to add to Aristotle.

We’re currently on track with the Quarter 3 roadmap features and are already ahead on Quarter 4, so I’ll see if we can squeeze his feature in an upcoming release.

2 Likes

That would be awesome. It would help a lot with integration efforts. Much thanks @sam and Team.

2 Likes

Hi @Michael, just letting you know that a delta endpoint has been released today. You’ll be able to find it at /metadata_info/latest_action.

Let me know how it goes!

@silke, is that ?

  • https://server_name/metadata_info/latest_action
  • https://server_name/api/metadata_info/latest_action
  • https://server_name/home/metadata_info/latest_action

None of these work for me. Although maybe I don’t have sufficient credentials…

@Michael you can access it at:

  • https://server_name/api/v4/metadata_info/latest_action/

And if you go to https://server_name/api/v4 you’ll also see all of the necessary documentation.

Looks nice.

So I run an API call like “https://dss.aristotlecloud.io/api/v4/metadata_info/latest_action/” and everything is sorted in order of date created. The results (just the first two results out of 50K+ here) look like this:

So I know the UUID, date and action type.

I don’t know what entity type the UUID is… but I can run another graphQL to work that out. Something like:

So it takes an extra query to know that it was a distribution that was modified. Now that I know the UUID and the entity type (distribution), I can follow up with an additional query to find out what it looks like now and refresh any mirrors I might have set up. Actually, I can probably just widen the graphQL query above and hopefully get the information I need anyway in one go.

I’ll run with this and see what I can get out of it, thanks again.

We can certainly look at adding in an extra field into this API to return the item type as well.