Seshat research tools and practices action plan and project roadmap discussion

[edwardchalstrey1]

TODO

• Write up a document that justifies this use of Ed/Kalle and is a plan for the final months and work for others to take on beyond that time. This should hopefully be a plan of action that Pieter can refer to in future when requesting funding/RSE time.
• Meet with Pieter F (or the whole of Seshat "Senior Leadership") to discuss this and to also populate docs pages:
  • 📚 [Documentation] - Resources #116
  • 📚 [Documentation] - Team page #115
  • Comms promotion of Seshat project and maps pages #95
  • Possible entire Seshat project Roadmap

Ideas

This obviously links in with the documentation #101 - but this issue is more about planning the tools and practices that are required to make the most of Seshat.

• Collecting all the code in a place that can be found
• Seeing what is and what isn't reproducible
• Separating data cleaning parts that can be re-used from analysis
• What parts should be part of the db, api, or post-processing Python scripts
• Matilida has reproduced the R code for social complexity paper in Python which re-creates a dataset used for that paper
  • we should make this code reproducible, findable, documented - see 📚 [Documentation] - Data cleaning/wrangling methods for creating [Replication] datasets #110
• Database sanity checks should be implemented Create tests for data sensibleness edwardchalstrey1/seshat#92

[edwardchalstrey1]

I'm not sure this needs to be written up formally as I have presented #101 to Pieter and the group and they are on board. However, perhaps is worth having written as a paragraph on the docs site

[edwardchalstrey1]

It might be easier to write something like this up after there is more of a clear roadmap for the Seshat project