Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add User Groups Report #1502

Merged
merged 2 commits into from Apr 9, 2019
Merged

Add User Groups Report #1502

merged 2 commits into from Apr 9, 2019

Conversation

sdm7g
Copy link
Contributor

@sdm7g sdm7g commented Apr 1, 2019

Add a user (permission) groups report.

Description

Report lists all users and identifier, name, department, email, telephone, source, is_system_user (bool), is_hidder_user (bool), title, and descriptions of the permission groups they belong to.

    {
      "id": 1,
      "identifier": "admin",
      "name": "Administrator",
      "department": null,
      "email": null,
      "telephone": null,
      "source": "DBAuth",
      "is_system_user": 1,
      "is_hidden_user": 0,
      "title": null,
      "groups": [
        {
          "description": "Administrators"
        }
      ]
    },

On PDF and HTML output formats, SYSTEM_USER and/or HIDDEN_USER is appended to the source line if those values are true; otherwise they are not indicated. But boolean values are output for JSON or CSV output.

Related JIRA Ticket or GitHub Issue

Motivation and Context

Tracking and managing users and their permission group membership.

How Has This Been Tested?

This has been in production use locally for some time, however other locales and bug fix to PDF were recent additions.

Only tested with English locales (en.yml). Other locales were generated from google translate and are not guaranteed to be accurate.

Reports modules have fairly localized scope: should not affect anything else.

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@lmcglohon lmcglohon merged commit 2dcf1b8 into archivesspace:master Apr 9, 2019
@lmcglohon lmcglohon added this to the 2.6.0 milestone May 7, 2019
@cdibella cdibella added the community code contributed by community members not on or contracted by the ArchivesSpace program team label Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community code contributed by community members not on or contracted by the ArchivesSpace program team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants