Credential Management

Application visibility based on Gitlab rights and usernames

Action Repository (dataset/project/report) Storage site
Visualize repository on GUI Visible + tag [imaging_platform_dataset/project/report] Visible + tag [imaging_platform_storage_site]
Upload data (under dvc) Developer Developer
Create New Maintainer (User or imaging.platform) Maintainer (User)
Update Owner (User or imaging.platform) Owner (User)

Access Roles

This is the permission relationship between Gitlab and JISAP

Role Reports Datasets Projects Templates Storage Sites
Guest R R R R R
Reporter R R R R R
Developer C*, R C*, R C*, R C*, R R, W
Maintainer C, R C, R C, R C, R C, R, W
Owner C, R, U, D C, R, U, D C, R, U, D C, R, U, D C, R, U, D, W

C: Create R: Read U: Update D: Delete W: Upload Data

*: If the user executing the action is not, at least, MAINTAINER, then the functional user imaging.platform must be MAINTAINER of the group in order to create a JISAP-Project and then grant access to the user as MAINTAINER

JISAP Gitlab User JISAP

  • Reporter access for indexing repositories
  • Maintainer access on Storage Sites -> Access to repositories on behalf of user

Access Tokens

  • CLI Download data & development -> Personal Token
  • CI/CD pipeline execution -> Storage Token