Top Menu

Jump to content
  • Nextcloud integration
    • View all projects
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video

      Welcome to OpenProject Community

      Get an overview

      Get a quick overview of project management and team collaboration with OpenProject.
      You can restart this video from the help menu
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Boards
  • Wiki
    • Table of contents
      • Hierarchy leafFileIDs
      • Hierarchy leafOpenProject edge instance for testing
      • Expanded. Click to collapseCollapsed. Click to showPreparation and Research
        • Hierarchy leafAuthorization and authentication flow
        • Hierarchy leafDevelopment environment
        • Expanded. Click to collapseCollapsed. Click to showFile Upload
          • Hierarchy leafNextcloud's upload API
        • Hierarchy leafLink types in Nextcloud
      • Hierarchy leafRequirements and UX Workshop - November 29, 2021
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leafSequence Diagram Nextcloud Integration
        • Hierarchy leafcurl API Tests
You are here:
  • FileIDs

Content

FileIDs

  • More
    • Table of contents

Considerations about files and fileIds in Nextcloud to keep in mind
item here means files or folder

  • items don't have a creator or modifier attribute, only owner
  • items ownership is changed (but not the id) when a user receives a folder as a share and moves an item out of the share to an other location
  • if a user is deleted all items that are owned by the user are deleted
  • a received shared item can be renamed and that name will not be propagated to the owner or other share receivers
  • a rename of an item in a received folder share will be propagated to the owner and other share receivers
  • multiple names can be associated with the same fileId. e.g. :
    1. James has a folder called "Documents" with a file called "important.doc"
    2. James shares folder "Documents" with Peter
    3. James shares separately "Documents/important.doc" with Peter
    4. Peter will have receiver "important.doc" twice but both "location" of the file will have the same fileId
    5. when Peter takes the fileId and queries for its name OCP\Filles\Folder::getById() he will receive two objects and in case he renamed one of the representations of the file both of the objects will show different names

Julien approves all above statements.

Loading...