photools.com Community

IMatch Bug Reports and Feature Requests => Feature Requests => Archive (Feature Requests) => Topic started by: ubacher on June 15, 2017, 09:49:20 PM

Title: IM2017 IMatch.fileMove should add moved file to database.
Post by: ubacher on June 15, 2017, 09:49:20 PM
Currently the call to IMatch.fileMove moves the file but does not add it to the database.
This means that any metadata (like categories) assigned to the file before moving is lost.
Title: Re: IM2017 IMatch.fileMove should add moved file to database.
Post by: Mario on June 15, 2017, 10:10:05 PM
This function is explicitly designed for file-system operations, e.g. to enable apps written in JavaScript to move files. Same for the copy or delete file function.

IMWS may be enhanced to implement file and folder operations in a future release.
Title: Re: IM2017 IMatch.fileMove should add moved file to database.
Post by: anmue on June 19, 2017, 07:20:54 AM
+1
Title: Re: IM2017 IMatch.fileMove should add moved file to database.
Post by: Carlo Didier on June 27, 2017, 11:06:08 AM
+1
Title: Re: IM2017 IMatch.fileMove should add moved file to database.
Post by: thrinn on July 01, 2017, 06:59:00 PM
+1
But please consider my comment already added to https://www.photools.com/community/index.php?topic=6752.0 (https://www.photools.com/community/index.php?topic=6752.0):
Quote
To clarify: The existing end points for files not managed/indexed by IMatch should not be changed.
Instead, I propose an additional endpoint (or endpoints) for copying/moving/renaming files indexed by IMatch.
Title: Re: IM2017 IMatch.fileMove should add moved file to database.
Post by: Mario on July 01, 2017, 07:40:05 PM
See my replies to the feature requests about basically the same things.