You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an admin user can press "Add Permission" in the data release module to give a user permission to a specific Data Release File, or to data release files with a specific version.
The dropdown list in this is not user friendly, as it is sorted by ACSII character, and not alphabetical. For instance if we have Alaska, albino, Bob then the list of users would be Alaska, Bob, albino. It should sort them while ignoring the case.
Then, if they would like to remove permissions from that user, they can only remove permissions to a version, and not to a specific file
There should be a feature to edit a specific data release entry, and manage the permissions per-user there, as well as hide or delete the file
CCNA OVERRIDE PRs
Good news! An implementation of this was already done on the forked repository for CCNA.
Note that there are a lot of PRs involved, I added them all so that you can have a history of the implementation, but it may be helpful to just compare the aces/LORIS version to the latest one on CCNA
The feature was originally added while CCNA was on Loris v23, and was upgraded in PR 6632 to work with LORIS v24.1. Further changes to the module may have been done on LORIS core between v24.1 and now.
You should use this as a baseline for your implementation, however you can definitely improve on it if need be!
New edit Data Release form:
The text was updated successfully, but these errors were encountered:
skarya22
added
Proposal
PR or Issue suggesting an improvement that can be accepted, rejected or altered
GSOC
Google Summer of Code related
labels
May 14, 2024
Describe the feature
Alaska, albino, Bob
then the list of users would beAlaska, Bob, albino
. It should sort them while ignoring the case.CCNA OVERRIDE PRs
New edit Data Release form:
The text was updated successfully, but these errors were encountered: