Hey everyone! I’ve got a pipeline which runs to turn a mediaset into an object everytime the mediaset changes… this allows me to upload from my OSDK frontend into a mediaset and then provide some metadata around that upload.
However, the latency on my pipeline build is like a minute! This is too long for the user to get feedback from the upload. Is there anyway to speed this up? I’ve uploaded an image of my pipeline.
Just for reference, here’s how I did the mediaset stuff in the end!
Basically I maintain two things on Palantir’s system:
Mediaset in a given project.
A dataset in the same project pointing to an object which essentially “tracks” the mediaset
When uploading a document I use the following three step process:
Upload the file and get a mediaItemRid
Get a media reference to the mediaItemRid
Create an entry in the object tracking the mediaset
Some important things to watchout for:
Don’t use a regular OSDK app for the token to use the mediaset APIs, rather create a non-ODSK app, giving it the appropriate permissions, namely: “api:mediasets-write” and “api:mediasets-read”.
The media reference is for later use. It’s important to set the string formatting of this correctly, and use the manipulation code I have in step 3 as what is returned from the endpoint does not line up with the way media references are interpreted on other parts of the platform!
How would you do this with restricted views? (I haven’t yet done this, but will soon! Also Boaz Francis is the real genius here for figuring it out)
Start by putting the mediaset in a different project where users only have view access and can only upload (they can’t read from the mediaset).
Then create an entry in the object tracking the mediaset (which is in a different project) with the media reference and mediaset rid.
Update the object with the media reference by using an automate on platform which calls a typescript function.