-
Notifications
You must be signed in to change notification settings - Fork 16
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
Project Scope. First Draft. #11
Comments
User problem Use cases
Functionality (note: ranked with a score from 1-6, with 1 - very important and main functionality and 6 - nice thing to have).
|
Thanks! That looks like a great start already. We can just pick the most important functionality and try to split it even more looking into what exactly do we need.
But even before going into nitty-gritty details for the functionality, UI, data and other. There are still some unanswered questions.
|
The specific database I spoke of is proprietary to our research group. I may be able to get a large data cut for developmental purposes. We can discuss that more for sure.
Twitter users are able to turn on/off geotagging in their preferences. From our own estimates, ~2% of all tweets are geotagged.
We are making OSS that any researcher, with a database of tweets (which are freely obtainable via the public Twitter API), can utilize. HealthMap (of which I am a member) is run out of Boston Children's Hospital and uses various forms of digital data to track disease spread. Primarily, this has been from news articles, blogs, governmental reports, etc. We have done a bit of work in the social media space, but much of this is not live on HealthMap.org (rather, it has been in various side projects). One goal of this endeavor is to use this OSS, and our own tweet database, to push our results to HealthMap.org and other research projects we run.
This needs to be fleshed out...
Anyone can use the OSS project. They will need to acquire their own tweets, but as I said this is free through the public Twitter API. |
Great! Thanks for answering those. I wanted to be sure that the project is not related to some proprietary code base or organization. Furthermore, sometimes it is very helpful to get new people along so far if they know that everything is open sourced and available for the public. I think the next step would be to discuss the first milestone in the channel. Next, document everything discussed here in this Issue, to make it available for everyone and for comments. Finally, create list of Tasks/Issues to work on and start developing. |
Sounds great - I agree completely! On Thu, Feb 19, 2015 at 9:31 PM, Alexey Novak [email protected]
|
So here are the basic requirements we want to build for the first version discussed during our last meeting in Slack
|
This sounds good to me - thanks Alexey! On Mon, Mar 2, 2015 at 8:49 PM, Alexey Novak [email protected]
|
I think this project is missing a Project Scope. Before jumping into actual development or designs or UI it would be great to outline main functionality we are trying to achieve here. We need to highlight main functionality and think of the ways how they would help to resolve "real-life problems" for users who will be using TweetGeoViz
Jared is it possible for you to formulate and to write down user problems and use cases for TweetGeoViz. What exactly this project is help to resolve? How it can be helpful to others? What examples and use cases for the project you foresee?
After you have user problems, could you to think of the main functionality points of the App and listed them here. Also rank them from 1 to 6 from (1 - very important and main functionality and 6 - nice thing to have).
Once we have this preliminary set we can discuss it during our next online meetup and try to figure out the first milestone with its features. This will spec out what EXACTLY we are trying to build and what UI, tools, components and modules we need to build.
The text was updated successfully, but these errors were encountered: