Change Details

One of the ways the Community will access the Commons Impact Metrics data is via public API (AQS2). A first step to achieve this goal is to design the endpoints of the Commons Impact Metrics AQS service. We should do this after we reviewed the feedback from the Commuinity in T358688. Tasks: [] Review the different documents to have a good idea of what the users need/want, in which format, granularity and dimensions they would like to receive the data. Also it is important that the endpoints are compatible with the existing data (if an endpoint requires small modifications of the data model, that's fine). * [[ https://docs.google.com/document/d/1AyorlFViHL2hj_6Sss4NRmKeqkk6XiV-EFb8uqyhla0/edit#heading=h.6po6vstr0mm5 | Data model and implementation plan ]] * [[ https://docs.google.com/document/d/1oWMH9p_XaZr7i-MywK0gG0fW2RIO11rXVBmzRspLJS4/edit | Commons Analytics Product Needs research ]] * Feedback from the Community on the prototype data model (no link yet T358688). [] Design a list of endpoints. Each endpoint should respond to 1 question (or a family of similar questions) from the users. Each endpoint design should specify: * URL format * Metric name * Granularity * List of dimensions (for each dimension: type, format, possible values, semantics) * List of metric values * Format of the JSON results Deliverables: [] A document with the design of the endpoints

One of the ways the Community will access the Commons Impact Metrics data is via public API (AQS2). A first step to achieve this goal is to design the endpoints of the Commons Impact Metrics AQS service. We should do this after we reviewed the feedback from the Commuinity in T358688. We should take into account that the source dataset should either be in Cassandra or Druid, and design the endpoints with a feasible Druid/Cassandra source in mind. Tasks: [] Review the different documents to have a good idea of what the users need/want, in which format, granularity and dimensions they would like to receive the data. Also it is important that the endpoints are compatible with the existing data (if an endpoint requires small modifications of the data model, that's fine). * [[ https://docs.google.com/document/d/1AyorlFViHL2hj_6Sss4NRmKeqkk6XiV-EFb8uqyhla0/edit#heading=h.6po6vstr0mm5 | Data model and implementation plan ]] * [[ https://docs.google.com/document/d/1oWMH9p_XaZr7i-MywK0gG0fW2RIO11rXVBmzRspLJS4/edit | Commons Analytics Product Needs research ]] * Feedback from the Community on the prototype data model (no link yet T358688). [] Design a list of endpoints. Each endpoint should respond to 1 question (or a family of similar questions) from the users. Each endpoint design should specify: * URL format * Metric name * Granularity * List of dimensions (for each dimension: type, format, possible values, semantics) * List of metric values * Format of the JSON results Deliverables: [] A document with the design of the endpoints

One of the ways the Community will access the Commons Impact Metrics data is via public API (AQS2). A first step to achieve this goal is to design the endpoints of the Commons Impact Metrics AQS service. We should do this after we reviewed the feedback from the Commuinity in T358688. We should take into account that the source dataset should either be in Cassandra or Druid, and design the endpoints with a feasible Druid/Cassandra source in mind. Tasks: [] Review the different documents to have a good idea of what the users need/want, in which format, granularity and dimensions they would like to receive the data. Also it is important that the endpoints are compatible with the existing data (if an endpoint requires small modifications of the data model, that's fine). * [[ https://docs.google.com/document/d/1AyorlFViHL2hj_6Sss4NRmKeqkk6XiV-EFb8uqyhla0/edit#heading=h.6po6vstr0mm5 | Data model and implementation plan ]] * [[ https://docs.google.com/document/d/1oWMH9p_XaZr7i-MywK0gG0fW2RIO11rXVBmzRspLJS4/edit | Commons Analytics Product Needs research ]] * Feedback from the Community on the prototype data model (no link yet T358688). [] Design a list of endpoints. Each endpoint should respond to 1 question (or a family of similar questions) from the users. Each endpoint design should specify: * URL format * Metric name * Granularity * List of dimensions (for each dimension: type, format, possible values, semantics) * List of metric values * Format of the JSON results Deliverables: [] A document with the design of the endpoints