1155 add a column to track the reindexing curator

[Kirandawadi]

Changes made:

• Added "Reindexing Curator" column to the homepage.
• Added functionality to automatically clear the reindexing curator when reindexing status is set to "Not Needed".
• This is implemented both in the frontend through postReindexingStatus() and in the backend via the CollectionSerializer.
• Made minor refactors to improve variable naming consistency

[Kirandawadi]

Demo

Reindexing_Curator.mov

[bishwaspraveen]

Can we maintain the history of changes on this field?

[Kirandawadi]

History is now maintained.

[CarsonDavis]

Let's add a test file for the new features. Cover everything that makes sense, but also specifically I want to see that the ReindexingHistory logs are being maintained as we add additional reindexing curators.

[bishwaspraveen]

Can you also take a look at this part of the code:

if instance.reindexing_status != instance.old_reindexing_status:
        ReindexingHistory.objects.create(
            collection=instance,
            reindexing_status=instance.reindexing_status,
            curated_by=instance.curated_by,
            old_status=instance.old_reindexing_status,
        )

[bishwaspraveen]

Make this code dry and reuse code that we already have for CuratorSelect

[Kirandawadi]

Tried to modularize the handleReindexingCuratorSelect() and handleCuratorSelect() functions into one, but ended up with too much if-else statements. So leaving as it is for better understandability.

[CarsonDavis]

Ok, slight design change. Lets only maintain one curator column, and populate the frontend based on the history. The original curator will be populated based on the first entry in the history table, and the reindexing curator will be populated based on the latest curator.

[CarsonDavis]

The recurator doesn't get depopulated until curation in progress or recuration in progress.

[bishwaspraveen]

Take a look at the post_save method in collection.py and refactor it based on standards.

[Kirandawadi]

write tests as well.