Return to Answer

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...

This is inspired by Andrew's answer on this thread and this response on another.

I think the best way we can improve the site scope is to not limit it to just the data itself. To quote Jeanne Holm from the other thread,

"A discussion of open data is limited if we only talk about a portion of the process of making data open. That process extends from a requirement to gather data to the use of that data to gain insight, create economic gain, or do social good."

So here's what I think the scope could be:

• The data itself (data-hunt)
• Gathering the data
• Using the data

Data-hunt is pretty obvious, and it's the most common thing seen so far. Gathering can be things like best practices and playbooks for entities that are trying to publish open data (licensing, releasing, etc). Using the data can include visualization, best practices for providing open APIs, and other code-y things. It doesn't have to just be code, but that's what I immediately think of as a programmer.

This obviously isn't a comprehensive list, but I think it's a start to expanding the site scope.

Edit: I just realized I said to not limit it to the data and then provided 3 things pretty limited to data. I meant to not focus on just data-hunting. Instead, I think the scope could include the process that Jeanne described.

Edit 2: Here is the kind of "code-y" question I was talking about:

Have genetic algorithms been applied to Open Data?

I would like to know what you think about having questions like that within the scope of this site. It's definitely applicable to Open Data by the way I presented it. It also fits within the idea of using data to gain insight. My concern is that people will come here with data mining questions when they should be going to a SE like Cross Validated...