Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OLD ISSUE REOPENED ON MAIN REPO - Scope workshop content for November 2024 Seshat get together in Vienna #141

Closed
2 tasks
edwardchalstrey1 opened this issue May 16, 2024 · 1 comment

Comments

@edwardchalstrey1
Copy link
Owner

edwardchalstrey1 commented May 16, 2024

The main aim of the workshop should be to decide upon and document (or write up issues with plans to document) the full Seshat project ways of working.

High priority

Discuss, determine, improve, document...

  1. The process for "Seshat Expert" data entry - i.e. how the experts use the comment system on the Seshat website, which currently is only used by the RAs, plus whether any general improvements to how this currently works for RAs is needed
  2. How Ed's suggestion for 📚 [Documentation] - How to edit "Cliopatria" borders shape dataset Seshat-Global-History-Databank/seshat#32 fits into item 1 ^
    • Ed should present this complete workflow including making Cliopatria releases
  3. How to bulk-add data to the database in the various data formats the RA's see as important: Add ability to bulk upload/update data to Seshat database Seshat-Global-History-Databank/seshat#70
  4. How RAs can/should work with the database API going forward and collating suggestions for how to improve the associated Python package

Lower priority

  1. Any final suggestions for the maps pages/ interface
  2. Teach Seshat RAs GitHub skills as per 4th July Edinburgh workshop - see Upcoming talks (workshop 5th July) #111
  3. Legacy issues with fragile non-reproducible Wiki/CSV -> database transfer issue.
    • Though this may be something Majid and Enrico just need to work though separately from the workshop.
  4. Semi-automated process for handling mismatches between Cliopatria and other Seshat data Seshat-Global-History-Databank/seshat#1 (this may be something to simply highlight and make the RAs aware of rather than to discuss in this workshop)

TODO

  • @edwardchalstrey1 Find a time that everyone can do a 2 day workshop in Vienna
  • Pieter Francois or CSH people to handle booking everything there
@edwardchalstrey1 edwardchalstrey1 moved this from Backlog to TODO in Seshat - DEPRECATED Jun 25, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title Develop training workshop for October/November Seshat get together Develop training and other workshop for October/November Seshat get together Jul 23, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title Develop training and other workshop for October/November Seshat get together Develop training and other workshop content for October/November Seshat get together in Vienna Jul 23, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title Develop training and other workshop content for October/November Seshat get together in Vienna Workshop content for November 2024 Seshat get together in Vienna Sep 17, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title Workshop content for November 2024 Seshat get together in Vienna Scope workshop content for November 2024 Seshat get together in Vienna Sep 17, 2024
@edwardchalstrey1
Copy link
Owner Author

Reopening on the main repo Seshat-Global-History-Databank#94

@github-project-automation github-project-automation bot moved this from TODO to Done in Seshat - DEPRECATED Sep 17, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title Scope workshop content for November 2024 Seshat get together in Vienna OLD ISSUE Sep 17, 2024
@edwardchalstrey1 edwardchalstrey1 changed the title OLD ISSUE OLD ISSUE REOPENED ON MAIN REPO - Scope workshop content for November 2024 Seshat get together in Vienna Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants