[API] Model and Serializer Changes in Support of Taggit.

[BethanyG]

Resource model and serializer changes needed to support taggit.

• Remove JSONB field from Resources model
• Alter Resource model to include taggit manager as show here & here
• Customize through model to support the non-int (UUID) PK for Resources now using an int for pk in addition to the UUID4 as a guid.
• Alter Admin interface to properly display taglist as shown here
• Add https://github.com/glemmaPaul/django-taggit-serializer or something similar to installed packages for tag serialization Lib only returns a list, wrote custom serializer to return a list of slug:name pairs.
• Alter the ResourceSerializer as needed to support tags
• Alter the ResourceView as needed to support tags as nested elements.
• Change any settings needed to support tags
• Update test cases as needed
• Add new tests as needed to support tags
• Add/alter fixtures to support tags (remove extra fields and other cleanup)
• Create fixture/load db with initial set of tags to "tag" resources with as POC.
• Tag existing resources so that they can be used in dev.

Additional related SO posts and others for reference/tips:

• https://stackoverflow.com/questions/52695298/using-django-taggit-and-django-taggit-serializer-with-issue
• https://stackoverflow.com/questions/57068139/cant-get-queryset-to-return-list-of-objects-that-is-descending-by-tag-matches
• https://stackoverflow.com/questions/57120364/django-taggit-how-to-record-id-of-user-that-added-tag
• https://stackoverflow.com/questions/21563726/using-django-taggit-with-django-rest-framework-im-not-able-to-save-my-tags

[BethanyG]

Will related tags be returned as part of a request for resources? If yes, will they be in the same format as noted elsewhere, or is the spec for that changing?

Current spec for the JSON response from `/api/v1/resources/{guid}:

{
      "model":"resources.resource",
      "guid":"02ef2aaa-da96-11e9-8a1f-d20089b01401",
      "fields":{
         "title":"The Life of a File (in Elm)",
         "author":"Evan Czaplicki",
         "description":"Elm Europe 2017 -- Evan Czaplicki, the life of a file",
         "url":"https://www.youtube.com/watch?v=XpDsk374LDE",
         "referring_url":"https://www.youtube.com/watch?v=kEitFAY7Gc8",
         "referring_user":"Gina Aspey (gaspeyl@unicef.org)",
         "user":10,
         "date_published":"2019-09-19T04:29:04Z",
         "created":"2019-09-19T04:29:04.069Z",
         "modified":"2019-09-19T04:29:04Z",
         "media_type":"TALK",
         "paid":true,
         "tags":[
            {
               "id":"44929775-9bb4-4840-af64-c6b0649d6677",
               "name":"Elm"
            },
            {
               "id":"0d325a30-7262-4914-90fe-6c90ac725fc2",
               "name":"FrontEnd"
            },
            {
               "id":"a1167632-abb8-4ce1-b090-b84e79c94c7f",
               "name":"JavaScript"
            }
         ]
      }

[lpatmo]

In React, I expect each tag to be a link -- e.g.

javascript. To that end, maybe we'd want this structure returned in the JSON:

 "tags":[
            {
               "slug":"elm",
               "name":"Elm"
            },
            {
               "slug":"frontend",
               "name":"Front-End"
            },
            {
               "slug":"javascript",
               "name":"JavaScript"
            }
         ]

[BethanyG]

Is slug intended to be a unique name or other identifier?

[lpatmo]

Slug should be a unique identifier. It might be easier for it to be a number since that's what taggit gives us naturally, right?

[BethanyG]

Going to assign this to myself as a think-through of changes, but would welcome other approaches. Also would welcome more tests!

[BethanyG]

oof. accidentally deleted comment above when I meant to edit it! Taggit is assigning numeric ids internally, but the slug field in the admin interface is populating with a lower-cased version of whatever is typed in. Leaving it for now. Would need to do a little work to see what other options we have for slug, and if we'd want to use them.

[BethanyG]

Current Resource Model below. Did not use https://github.com/glemmaPaul/django-taggit-serializer because it would only return a tag list and not a list of slug:tag pairs. Leaving the library there in case we do want to use it in the future in another context.

{
            "guid": "ea3946be-073a-437e-9001-84378ac68f7d",
            "author": "Katie and Ben",
            "title": "Linear Digressions",
            "description": "Linear Digressions is a podcast about Machine Learning and Data Science",
            "url": "http://lineardigressions.com/",
            "referring_url": "",
            "other_referring_source": "Henry Melan (hmelanc@blog.com)",
            "user": 10,
            "date_published": "2019-09-18T20:35:18-07:00",
            "created": "2019-09-18T20:35:18.309000-07:00",
            "modified": "2019-09-18T20:35:18-07:00",
            "media_type": "Podcast",
            "paid": false,
            "tags": [
                {
                    "slug": "data-science",
                    "name": "data science"
                },
                {
                    "slug": "machine-learning",
                    "name": "machine learning"
                },
                {
                    "slug": "ml",
                    "name": "ML"
                },
                {
                    "slug": "programming",
                    "name": "programming"
                },
                {
                    "slug": "python",
                    "name": "python"
                },
                {
                    "slug": "statistics",
                    "name": "statistics"
                }
            ]
}

[lpatmo]

Got it, thanks for looking into django-taggit-serializer! That JSON structure looks 💯; I'm excited to get back into doing some cleanup for react-concept next...