Skip to content

Implement CKAN resource versioning for Potree scene configurations #85

Description

@mosoriob

Feature Request

Implement integration with CKAN's resource versioning capabilities for Potree scene configurations to enable proper version control of collaborative edits.

Current Documentation Statement

From src/ckanext-potree/README-pipeline.md line 168:

Version Control: Benefits from CKAN's resource versioning capabilities

Additional features from lines 442-443:

Version Control: Complete history of scene modifications and contributors
Conflict Resolution: Automatic handling of simultaneous edits

Feature Description

This is a future feature / nice to have that would leverage CKAN's built-in resource versioning system to track changes to scene.json5 configurations over time.

Proposed Functionality

Core Version Control Features

  • Track versions of scene.json5 files as users make modifications
  • Provide version history interface within Potree viewer
  • Enable rollback to previous scene configurations
  • Show diff between versions for collaborative review
  • Maintain contributor attribution across versions

Advanced Collaborative Features

  • Complete History: Full audit trail of scene modifications and contributors
  • Conflict Resolution: Automatic handling of simultaneous edits by multiple users
  • Merge Capabilities: Smart merging of non-conflicting changes
  • Change Attribution: Track which user made specific modifications

Benefits

  • Enhanced collaborative workflows
  • Audit trail for research reproducibility
  • Recovery from accidental changes
  • Better conflict resolution for simultaneous edits
  • Professional version management for publications
  • Complete history of scene modifications and contributors

Implementation Considerations

  • Integration with CKAN's existing versioning API
  • UI components for version browsing in Potree viewer
  • Automatic versioning triggers on scene modifications
  • Performance impact of version storage
  • Conflict detection and resolution algorithms
  • User notification system for simultaneous edits

Priority

Low - Nice to have feature for enhanced collaboration

Labels

  • enhancement
  • future-feature
  • nice-to-have
  • collaboration
  • version-control

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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