Change Details

The API endpoint is pretty nice, but let's wrap it in a UI. What we want to get out of this reference UI: * Demonstrate what information we're making available. * Educational tool to explain what all the numbers mean. * Example implementation to serve as a starting point for other projects. * Debugging aid for us and others. Potential views: * Scores from all models for a given revision. * Evolution of article quality over time. * Model metadata. * List of models. == Implementation == A simple but maybe inelegant way to do this would be for the ores server to provide additional routes which emit an HTML template plus revscoring data object, and populate the template using JavaScript. Reusability would be a big plus, whatever we do should be easy to adapt using new templates or architectures.

What we want to get out of this extended reference UI: * Demonstrate what information we're making available. * Educational tool to explain what all the numbers mean. * Example implementation to serve as a starting point for other projects. * Debugging aid for us and others. Potential views: * Scores from all models for a given revision. * Evolution of article quality over time. * Model metadata. * List of models. == Implementation == Provide additional routes which emit an HTML template plus revscoring data object, and populate the template using JavaScript. Reusability would be a big plus, whatever we do should be easy to adapt using new templates or architectures.

The API endpoint is pretty nice, but let's wrap it in a UI. What we want to get out of this extended reference UI: * Demonstrate what information we're making available. * Educational tool to explain what all the numbers mean. * Example implementation to serve as a starting point for other projects. * Debugging aid for us and others. Potential views: * Scores from all models for a given revision. * Evolution of article quality over time. * Model metadata. * List of models. == Implementation == A simple but maybe inelegant way to do this would be for the ores server to pProvide additional routes which emit an HTML template plus revscoring data object, and populate the template using JavaScript. Reusability would be a big plus, whatever we do should be easy to adapt using new templates or architectures.