I have several people working on the database in parallel, some of them are required to make changes to a limited set of groups each day, others should only use it as read-only.
For the read-only mode, I have to use the web interface, which is the only way to provide read-only. This is good enough, but offering a read-only mode for the native application would be better.
For the people bringing changes in parallel, the risks of damage to the database (mistakes such group move or deletion) are doubled, which brings me to these feature suggestions:
— record a log of all changes brought by a user (group/file rename/move/copy/replicate/modify/create so that I can search for potential mistakes after a day’s work and revert to previous backups before they are overwritten)
— and/or display the changes when launching the database synchronisation (in order to allow canceling it and fixing any mistake before retrying)
— also, allow a permissions system on the database so that an administrator would be able to define in which parts of the database a specific user is able to change and/or create and/or move and/or rename groups/files (even though inheritance would likely be hard to define because of replicant groups)
Some nice additional features would be:
— being able to undo a file/group rename
— apparently in some cases rotating JPGs lowers the quality because the resulting file size is half of the original file, so for now I have to do that externally in the Preview application, so what would be great would be a lossless JPG rotation based on the orientation metadata