CatalogEntry API

[akihikokuroda]

Summary

Fix #1170

Details and comments

This PR adds ModelView APIs for CatalogEntry.

The list method will be enhanced to handle the query string for title, description and tags.

[IceKhan13]

Can we review it @akihikokuroda ?

[akihikokuroda]

@IceKhan13 Yes, please. I'll have follow up PR. Please take a look at this comment, too. #1170 (comment)

[psschwei]

This is probably my ignorance of django, but where/how do these APIs get specified? Or do they just get created automatically?

POST:api/v1/catalog_entries/ - create
GET:api/v1/catalog_entries/ - list
GET:api/v1/catalog_entries/{id}/ - get
UPDATE:api/v1/catalog_entries/{id}/ - update
PATCH:api/v1/catalog_entries/{id}/ - partial update
DELETE:api/v1/catalog_entries/{id}/ - delete

[Tansito]

I didn't look at the PR yet so I'm going to talk in general. Using the ViewSet the class generates automatically the end-points for you taking into account the methods that you declare:

https://www.django-rest-framework.org/api-guide/viewsets/

[akihikokuroda]

@psschwei Yes, It is created by using ModelViewSet

[akihikokuroda]

The second commit has

POST:api/v1/programs/to_catalog 

and query string support for

GET:api/v1/catalog_entries/?{field}={included string}

[psschwei]

LGTM - API works fine on a local cluster
I would get another review before merging though, just to be sure (I'm not a django expert, so I may have missed something)