Smithsonian / Smithsonian/caas-aspace-scripts

[FEATURE] Update report_grouppermissions.py to Match Report Needs

Open
#25 0 comments 0 reactions 1 assignee View on GitHub

@crugas is already working on this.

Since Jan 24, 2025.

enhancement
Dominant language
Python
Stars
1
Forks
0
Avg merge
4d 5h
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.
Enhance the report_grouppermissions.py script in the following ways:

  • Add repository specific permissions per column on each user group sheet to highlight any differences between repos
  • Group all repo user groups together
  • Add a column for repo code only
  • Highlight any permissions in group_permissions that are not consistent with ASpace defaults
  • Add columns per repo-user group in each sheet to cross-examine permissions against all_permissions and defaults
  • Add the SI groups as separate sheets si-assessments, si-authorities, si-background-jobs, si-classifications, si-agent-contact-info
  • Mark: Another small useful comparison would be one worksheet with 2 columns: repo, group count; and then another worksheet with 3 columns that lists repo, group name, count of users assigned to that group.

TIP: keep a constant file in your local repo to keep a list of permissions and user groups for defaults – like listed here: https://github.com/Smithsonian/caas_aspace_group_baselines/blob/3b3260247f43c6f585300c19f1f93a5d1969ce7d/backend/model/repository.rb

Describe the solution you'd like
I'll need to update the script like above to make it more usable/understandable for future reports.

Describe alternatives you've considered
Some of this could be cleaned up with Excel, but I'd like to get as much done using Python so the process is more easily repeated in the future.

Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.