Improve performance and consider rate limits

[BenitoMatischen]

The API has a rate limit of 50 calls per second before 429 errors.
What improvements that could be made to reduce the number of API calls this tool makes?

[BenitoMatischen]

The API has a rate limit of 50 calls per second before 429 errors.

Suggestions for general improvements to reduce rate limiting errors and load on the API:

• Use embeddings to get data needed in just one API call (e.g. for licenses one project will have just one license so can embed that data when getting project data)

[BenitoMatischen]

Suggestion from COS team:

Here is an example of one you may be able to use where I've embedded the license, parent , root, and bibliographic_contributors relationships. This project doesn't have a license set and doesn't have a parent project, so those properties will come back with an errors array instead of the data object that you may expect, so just be mindful of that. And it looks like for the embedded bibliographic_contributor relationship, it comes with the meta object that should give you the total number of bibliographic contributors. I know I had voiced some uncertainty about using the embed qp for has-many relationships, but it looks like we can expect that meta object for has-many relationships.
https://api.test.osf.io/v2/nodes/axm36/?embed[]=parent&embed[]=root&embed[]=license&embed[]=bibliographic_contributors