Series

[j1g5awi]

relate: #296

TODO

• Edition can only be link to one Work( and automerge Work when Edition merged) move to Work migration #888
• [=] Series page ui ( will more like Collection )
• [=] tests
  - [ ] if possible, implate Series of Edition

[j1g5awi]

@alphatownsman maybe GitHub Codespace have no enough spaces to load all data and test migration, so I need help for testing it.

[alphatownsman]

this current migration code will be a few hours if not longer for neodb.social, and memory intensive. I suggest we do the following:

• split this to two PR, Work refactor, then new Series
• in Work PR, do not drop any table, migration code should be skippable with a configuration (on neodb.social, I will set the configuration to ON, so django migration can finish in seconds, and then run the actual data migration separately), btw your code should assume user may make changes while migration is running.

I'll help test too but Codespace has 8~16GB RAM which should be more than enough I think, on neodb.social:

$ free -g
              total        used        free      shared  buff/cache   available
Mem:             23          12           0           0          10          10

And size of catalog data is much smaller than posts/etc