Implement GetMyDataCollectionItems use case

[ekraffmiller]

What this PR does / why we need it:

Implements a use case for calling the MyData API endpoint, used in the SPA Accounts Page -> My Data section.
Returns a collection of CollectionItems, similar to the GetCollectionItems use case.

Which issue(s) this PR closes:

• Closes Implement use case for getting My Data section data #283

Suggestions on how to test this:

Review code and tests

[g-saracca]

Hi @ekraffmiller, should we already create a js-dataverse use case for this endpoint?
Doesn't it still have a lot of bugs to solve and things that might change because of them?
IMO it may be too early to try to make a Use Case and a frontend integration.

[ekraffmiller]

Hi @ekraffmiller, should we already create a js-dataverse use case for this endpoint? Doesn't it still have a lot of bugs to solve and things that might change because of them? IMO it may be too early to try to make a Use Case and a frontend integration.

That's true there are bug fixes to wait for, I just wasn't sure if we needed to work with what we have since I'm not sure when they will be fixed. But I can put a waiting tag on this and work on other things until we decide what to do.

[g-saracca]

That's true there are bug fixes to wait for, I just wasn't sure if we needed to work with what we have since I'm not sure when they will be fixed. But I can put a waiting tag on this and work on other things until we decide what to do.

Ok, so if you did any temporary patch/fix to avoid the bugs please mention it in the PR. If you believe that there are no big patches to do to make it work it's ok otherwise I would wait but prioritising the API bug fixes to be fixed as soon as possible.

[ekraffmiller]

That's true there are bug fixes to wait for, I just wasn't sure if we needed to work with what we have since I'm not sure when they will be fixed. But I can put a waiting tag on this and work on other things until we decide what to do.

Ok, so if you did any temporary patch/fix to avoid the bugs please mention it in the PR. If you believe that there are no big patches to do to make it work it's ok otherwise I would wait but prioritising the API bug fixes to be fixed as soon as possible.

Ok, to summarize the issues on the API -

1. The per-page param doesn't work, it always returns 10 items. #10528
2. The empty results are thrown as an error from the API. #11447
3. There is no permissions check for using the otherIdentifier param. #11451
4. The datasets in harvested dataverses are not being returned. #11083

These errors don't affect the logic of the use case, just the testing. When 2 and 3 are fixed, we need to update the tests. Number 2 affects the SPA handling empty results. So I think we can set it to waiting until 2 is fixed, as you said, it shouldn't be a big change.

[g-saracca]

@ekraffmiller ok, it doesn't sound too bad right?
So I believe we can continue with this Use Case 👍🏼, and it should be a temporary workaround in the SPA integration regarding the 2nd item.
Thanks! I will review this PR

[g-saracca]

Nice job, looks great! 🎉 Just some minor comments.
It's awesome that MyData endpoint returns the same properties(different naming) as the Search endpoint so we can share Collection, Dataset and File Previews models between these two use cases!
One more thing, could you add integration tests regarding filtering in the GetMyDataCollectionItems use case as we have with the GetCollectionItems use case?

[ekraffmiller]

Hi @g-saracca I finally fixed the tests! when I used createCollectionViaApi, the collection didn't appear in the results, but when I used the use case instead (createCollection.execute()) it works. I don't know why, since the collection seems to be created correctly in both instances. Also, when I create the new user, I have to give it superuser privileges in order to have the permission to create a subcollection within the test collection.

[g-saracca]

Approving!

[ofahimIQSS]

Tests are passing - merging.