Add API endpoint to remove a document from one folder index and add to another

[reganwolfrom]

As folders hold a list of documents within, moving a document from one folder to another would require an API call to remove the document from the source folder and add to the destination folder.

Example endpoint:

POST /documents/{id}/move
{"sourceFolder": "Client ABC", "destinationFolder": "Client ABC/Client ABC Workspace"}

NOTE: if we want to use move as the resource, we can also include siteId in future, allowing a move between folders, sites, or both, e.g., sourceSiteId

[mfriesen]

To keep the document secondary indexing flexible my proposal would be to create an API under

POST /indices/{indexType}/{operation}

So in this case there would be a
POST /indices/folder/move
{
"source":"",
"target":""
}

This would allow other types of indexing to be created with relative ease.

[reganwolfrom]

@mfriesen after deleting documents (DELETE /documents/{id}), there is a list of "folders", one for each deleted document, returning on the root folder.

{
      "path": "Document List.xlsx",
      "folder": true,
      "tags": {
        
      }
    },
    {
      "path": "Financial Sample.xlsx",
      "folder": true,
      "tags": {
        
      }
    },

[reganwolfrom]

@mfriesen when moving from a folder to root, specifying "" as the target gives a 400:
{"errors":[{"key":"target","error":"attribute is required"}]}

But when providing "/" as the target, a new folder "f#" is created in DynamoDB, and the document is moved to this folder.

Based on other concepts of root that we are using, i.e., the absence of a folder being no folder ("") instead of a root of "/", I think the blank target should be admissible. In addition, the "/" folder should not be created if "/" is provided as a destination.

Conversely, we can use "/" to signify root, and would also avoid creating the "/" folder.

[mfriesen]

Also need to support adding the same file multiple times to a folder