Create {function_uid}/jobCollections endpoint

[JavierGOrdonnez]

SImilar to case : #1883 ; would be great to have a call that yields the JobCollections associated to a function (rather than performing the filtering in the frontend)

[wvangeit]

This one I'm a bit more reluctant. You have a use case for this atm?
For functionjobs it was rather intuitive since a functionjob is related to exactly one function.

For collections it's different though. Nothing is preventing to have multiple functions (functionjobs of...) inside the same collection.
It could return 'all the collections where this function is 'part' of ', but i find it slightly artificial.

[JavierGOrdonnez]

The use case is at the JobSelector, Jobs are grouped into toggable JobCollections - thus I would like to retrieve JobCollections associated to that function (can I even do that from the individual Jobs, to which JobCollection they are associated?). Right now I am retrieving ALL JobCollections (for demonstration purposes), not those associated to the selected function. I would need to go through all contained jobs, check whether they are associated to the right functionUid, and only include those JobCollections which are not empty after this filtering. This seems a hell of a lot of API calls.

I would advocate for enforcing homogeneous JobCollections (i.e. not allowing the registration of JobCollections with FunctionJobs from different Functions, and raise an error if that is attempted). Or can you think of a use-case where this would be useful? This does not come to mind. So far, the only place where a JobCollection is created is at a "map_function(function_uid)" call - which is function-homogeneous.

[wvangeit]

Well, for me JobCollections were for me a way for user to bring order in the chaos of functionjobs. I.e. to pool them together and store that info in the system. Like e.g. 'all the functionjobs used for project x'. It could be important to for example prevent deletion etc.
I just used the JobCollection for the map function since it was a convenient way to return functionjobs there too.

But I could do the following for now do, I can make a search endpoint that has an argument 'has_functionjobid=...', and then it would return the jobcollections you are asking for. The search would happen deep in the db, which should be good at this sort of query.

[wvangeit]

It is now implemented as an has_function_id input of the list_function_job_collections endpoint: