Archiving nodes and Media

See node status in e.g. Content

Add a status of "Archived" and maintain a separate register of archived material

In a dynamic site, redundant pages should be retained after being unpublished. There are many reasons for this of which the most important is for evidence in court proceedings.

This is not the same as revisioning (although it is related).

An example would be where a placeholder page is created and a new node, perhaps of a different type, replaces it in due course.

When documents and media are unpublished, they remain in the Content lists, which creates long lists that can be confusing where documents have similar titles.

It would be very helpful if an unpublished node or media could be marked as "archived" and a separate archive content/media list made available so that only current documents, including unpublished documents, appear in the active lists.

So far as I can see, there is no reason to remove the archived documents from the current datatable which would, of course, require massive work.

I have found that this issue has been rumbling around since D6 and so there is obviously interest in it but various attempts to address it with modules have foundered. As this is part of Core, perhaps it is a development / feature that will be useful.

Comments

VortexCentrum created an issue. See original summary.

cilefen’s picture

Status: Active » Postponed

Please cite the other efforts to accomplish this.

cilefen’s picture

Is there a reason core's Content Moderation along with some user-side edits to the default content View could not do this today?

wim leers’s picture

Status: Postponed » Postponed (maintainer needs more info)

#4++

vortexcentrum’s picture

Gosh. I'd have to look at that. It doesn't seem like the best way to achieve it from an ordinary user's perspective.

I was hoping that the process could be built into the existing published/unpublished/delete action dropdown in the content page and that such an approach would be transparent to a content editor.

At its simplest, the addition of "archive" would change the Status shown in the Content page.

This would allow for visual differentiation between unpublished and archived content and for the filter to display only draft / unpublished / "depublished" (i.e. was published but now is not) items.

The question of whether to maintain a separate archive datatable is related but separate and I can see that that would be much more complicated.

I'll look at content moderation and views but if this is a widespread a "wish list" item as I think it is (or should be), then perhaps it should be in the features request queue.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Wonder if this could be closed? Seems a moderation state for Archive with a view should cover this.

cilefen’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)