Technical issues with game log imports will arise, namely for each session, it will refer to a game and players at elast which may or may not already exists in the database. If so we need to identify so, if not we need a neat way to create these on the fly. Games via a BGG ID probably and players will need a basic metadata set defined, what do we minimally need to know.
Finally we then need a tool to eliminate inadvertent dupes. I envisage one for games, and one for players, in each case selecting two items in a DAL widget and one of them as the master, it would copy from the slave to the master any non-conflicting data and delete the slave. To do so, would need a summary fo what in the slave would be lost.
Also be great to be able to do this for lost of dupes, and have a way of identifying candidate dupes.
This looks the best approach:
https://django-import-export.readthedocs.io/en/latest/getting_started.html
Technical issues with game log imports will arise, namely for each session, it will refer to a game and players at elast which may or may not already exists in the database. If so we need to identify so, if not we need a neat way to create these on the fly. Games via a BGG ID probably and players will need a basic metadata set defined, what do we minimally need to know.
Finally we then need a tool to eliminate inadvertent dupes. I envisage one for games, and one for players, in each case selecting two items in a DAL widget and one of them as the master, it would copy from the slave to the master any non-conflicting data and delete the slave. To do so, would need a summary fo what in the slave would be lost.
Also be great to be able to do this for lost of dupes, and have a way of identifying candidate dupes.
Oh, the bells and whistles.