[future] Majora 3.0

[SamStudio8]

• All ArtifactGroups (Artifacts?) have a JSON field on their model for storing a cache of themselves, for fast serialisation (but not querying)
• Determine whether to abolish ProcessRecords and instead duplicate Process-level information in each record
• Remove as many n+1 query situations as possible
• Reimplement the tree-based record structure with django-mptt
• OAuth API only
• Baked-in permissions system (specifying user privs on an object level)
• current_path should be a core Artifact property
• Break apart the monolith. Perhaps each artifact type can be its own "app" and inherit from a core Majora app.
• Developer docs (beyond advanced API usage)
• Make better use of pre and post_save signals to catch things for Tatl
• group_path doesn't seem to be used so get_mag never works
• There should be a util for getting DRA
• Fix all the naive timezone errors
• api_views should be entirely abstracted and give the same interface to ocarina
• coreapi in ocarina could read spec from majora?
• Extend the audit API to keep records of field changes (who, when, why?) possibly before/after (or blank them if sensitive) for all models, rather than manually doing it from the forms models
• update to celery5

---

• graduate function based views to class based views
• unify crud model stuff in api.py, then hook it to api_views.py and views.py, with a view to unifying api_views.py and views.py