Skip to content

Archived Layer retention and versioning (particularly in the superuser project) is incoherent #955

Description

@underbluewaters

The setting for Archived Layer Retention seems to be working well, with archived layer versions older than 30 days (or whatever the retention setting) being deleted. The problem is, the newest version is retained and labeled as "Version 1"... That isn't right, and can make reasoning about the status of the layer list confusing. I was trying to understand the difference between the newest Marine Regions EEZ layer and the one we started with, and was confused when there was only a single "Version 1". This would likely be an issue with all projects, but is particularly frustrating in the superuser project. I was tempted to just store all layer versions indefinitely, but the issue there is that the CRW products are updated every 24 hours. We really need to discard older versions in that case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions