Return to Question

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.

I once flagged two link-only answers, but since we're not StackOverflow, in terms of size/#users, I think we should rather strive to comment/edit the posts, so as to make them not link-only answers. This may seem odd, since there are questions in which people actually want a reference on a specific subject, like in these questions:

• Publicly Available Datasets
• What are some easy to learn machine-learning applications?
• Publicly available social network datasets/APIs.

But I guess whenever the request is not for dataset/API/tool sources, and actually for explanations/examples on some topic, as these posts:

• Can map-reduce algorithms written for MongoDB be ported to Hadoop later?
• Open source solver for large mixed integer programming task?
• Looking for example infrastructure stacks/workflows/pipelines
• How can I predict traffic based on previous time series data?

the answers should praise this rule of thumb discussed on meta.stackexchange. So, the idea is simply to either comment link-only answers, in order to ask the OP to improve their question, or simply suggest an edit.

Now, to leave a question here: what should actually be done for link-only answers? Are these suggestions enough/reasonable, or should we flag them anyway? Any further suggestions are surely much welcome.