A request that was declined, and the reasoning — a second dataset

A request that was declined, and the reasoning — a second dataset Writing it up because I had to work it out twice and would rather nobody else did.

Process question about how this site works.

I have read the guidelines and the trust-level page and I still have a question about the mechanism rather than the rule. Specifically, I would like to understand the reasoning behind it, because I suspect the reasoning is better than the rule sounds.

Not a complaint. If the answer is "because of a failure mode you have not seen yet", I would like to hear about the failure mode.

Cross-referencing: if you notice two pages that should reference each other but do not, suggest the cross-reference.

I read the opening post twice before replying, because I had assumed the opposite.

Request a new maintained page: if a question recurs, has a good marked solution, and contains a worked example, it is a candidate for promotion to a maintained documentation page. Post your nomination in this subcategory with a link to the topic.

I disagree with the reply above, and I think the disagreement is substantive rather than terminological.

The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.

Translation suggestions: if a maintained page should exist in another language, suggesting it here helps the maintainers prioritise multilingual work.

Correction requests: if you spot an error in a maintained page, note it here with the specific correction. The maintainer will review and update if justified.

Coming back to post #5, because the follow-up matters more than the original answer.

Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.

Picking up post #5: that is the part I would want checked first.

Format suggestions: if you think a maintained page could be clearer in its presentation (different section structure, different examples, added graphics) suggest the change.

Worth separating two things that post #5 runs together.

Accessibility feedback: if you have trouble accessing or reading a maintained page (screen reader issues, contrast problems, small text) report it. Accessibility matters.

post #9 is right about the mechanism and I think understates the practical bit.

Authority and authorship: if you think a maintained page needs input from someone with specific expertise (a clinician, an analytical chemist) suggest who might contribute.

Flag a page that has drifted: if you notice a maintained page has information that is outdated (dates that have passed, regulatory changes, new evidence) post a flag so the maintainers see it.

Suggesting content for a page: if you know a maintained page is missing something important, post a suggestion with specific content you think should be added.

Picking up post #10: that is the part I would want checked first.

Authority and authorship: if you think a maintained page needs input from someone with specific expertise (a clinician, an analytical chemist) suggest who might contribute.

Coming back to post #12, because the follow-up matters more than the original answer.

Two things before anyone answers the substance.

First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.