Giter Club home page Giter Club logo

debaterjson's Introduction

DebaterJSON

DebateJSON allows you to easily keep track of your performance in debating by providing a schema for the storage of this data.

Why DebaterJSON?

  • Analysis: DebaterJSON provides an easy interface to perform analysis on your data so you can tell how much you're actually improving. To make this task easier debater.py offers a small library of functions and classes to interact with DebaterJSON.
  • Centralisation: DebaterJSON keeps your data in one central location so you don't end up having to keep open dozens of tab links, each of which made with different tab software.
  • Persistence: As the recent ending of the Heroku free tier sadly demonstrated, data that is not on a drive you own can disappear at any time for any reason. DebaterJSON solves this by ensuring that you will always have a permanent record of how you did. (Note that this tool is intended to store individual debater's records, if you want to archive an entire tournament, have a look at DebateXML.)

Contributing

Please feel free to help out by having a look at some of the currently open issues. From there you can either:

  • Join the discussion at any currently open discussion.
  • Submit a pull request adressing any of the issues or.
  • Open a new issue if you have a question, new idea, or found a bug.

debaterjson's People

Contributors

daankoning avatar

Watchers

 avatar

debaterjson's Issues

Distinguish between different break categories

Currently the schema only allows a binary choice between having broken or not. This isn't representative of real tournaments that often have a whole scale of break categories. There needs to be a way to store this information.

Further complications are introduced by tournaments such as EUDC allowing double breaking. This runs into a similar problem as in #2 (comment).

Include possible break categories as well

Currently the schema only allows recording of the categories the speaker did break in, not those they could have broken in.

Including this information might provide some useful data to compare, for example, the rates of breaking in ESL vs open.

Consider disallowing additional (not in schema) properties

I can see some clear merits to either side. The main argument in favour seems to me to be that it would greatly improve ease of parsing if all the attributes can be known ahead of time. On the other hand, different people might have use cases that currently are not covered by the schema, such as different formats or additional data on speeches.

Implementing it would be as trivial as adding some "additionalProperties": false attributes.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.