The problem is, this quote is from the developers, and is regularly referred to in the how-to documentation here. If this is not the reality of the implementation, one of two things needs to happen:
-
The documentation needs to change so that it clearly reflects the reality of the active feature.
-
The active feature needs to be updated to reflect the original design and intent.
This is the understanding I have of an archive; in order to change it, you must remove it, physically, from the archive. It would make sense for similar behavior in digital form.
The problem I’m having is the functional difference between closed and archived is so minimal as to be nearly pointless. Closed or archived; closed means closed to further comments, to me. Archived means “can no longer be changed” when compared specifically to closed.
Unlisting is an entirely different function unrelated to archiving, and isn’t relevant here. That’s why it’s a different function separate from archiving.
In my situation, I don’t want to unlist the damn things, I just want people to stop replying to them! They have useful historical information, they’re just no longer relevant to current complaints/functionality. If I only want them accessible by link, then I’d unlist them.
That’s the whole point of closing, and later archiving.
As for real-world comparisons… archives on the web, particularly of forums, are always read-only. They’re provided for historical purposes, not “let’s update this when we need to.” You look, but you don’t update. That’s why you have them. This feature is not, currently, functioning like an actual archive. You’re not intended to add to a digital archive. You may add new items to the archive, but you don’t open up existing ones and make changes. If you need to do that, they shouldn’t be in the archive because they’re active and relevant.
If you want something that is no longer relevant but is still updatable, you close it. Closing being a status that is irrelevant to TL4 and above makes sense.