Is there any reason for this? Why users of the group owner can view the metadata by default, but not it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
Is there any reason for this? Why users of the group owner can view the metadata by default, but not it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
Is there any reason for this? Why users of the group owner can view the metadata by default, but not access it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
It does not make sense to me, if you can view the record you should be able to view its resources also?
The only use for such a default would be if it was common for EDITORS to have a public record, and then want to attach internal resources (like PDFs) that were only intended to be used by EDITORS responsible for the public record.
I think that would be unusual, and limiting - and not suitable for a default case.
I know it’s a long ago about this commit, “Add option to give all privileges to the group on MD creation”. I can see that can be useful for the edit privilege, but not for the dynamic and download ones.
I’ll do a PR to change this, but if you remember any good reason to keep the current behaviour let me know.
---- On Tue, 30 Jan 2024 22:14:18 +0100 Jody Garnett <jody.garnett@…31…> wrote —
Jose,
Assembling your email into:
Is there any reason for this? Why users of the group owner can view the metadata by default, but not access it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
It does not make sense to me, if you can view the record you should be able to view its resources also?
The only use for such a default would be if it was common for EDITORS to have a public record, and then want to attach internal resources (like PDFs) that were only intended to be used by EDITORS responsible for the public record.
I think that would be unusual, and limiting - and not suitable for a default case.
Is there any reason for this? Why users of the group owner can view the metadata by default, but not it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
I know it’s a long ago about this commit, “Add option to give all privileges to the group on MD creation”. I can see that can be useful for the edit privilege, but not for the dynamic and download ones.
I’ll do a PR to change this, but if you remember any good reason to keep the current behaviour let me know.
Is there any reason for this? Why users of the group owner can view the metadata by default, but not access it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
It does not make sense to me, if you can view the record you should be able to view its resources also?
The only use for such a default would be if it was common for EDITORS to have a public record, and then want to attach internal resources (like PDFs) that were only intended to be used by EDITORS responsible for the public record.
I think that would be unusual, and limiting - and not suitable for a default case.
Is there any reason for this? Why users of the group owner can view the metadata by default, but not it’s resources unless you use the previous flag to allow to edit the metadata by other Editors?
