-
Notifications
You must be signed in to change notification settings - Fork 5
User groups and roles
This page describes the different user groups and roles on DAILP’s website, which determines the permissions and level of access for each type of user.
A “User” refers to a single account registered in AWS Cognito and represents one or more people accessing the DAILP website. Users are encouraged to keep one account per person, but DAILP doesn’t strictly enforce this in order to accommodate our multigenerational work teams.
Each User has one (or more) Role(s). “Roles” define what a user can or cannot do on the DAILP website. The roles a User can have are Admin, Editor, Contributor, Reader, and Visitor.
An Admin has permission to manage project sites and collections. An Admin can do everything an Editor can do, and has the following permissions:
-
Admin permissions that manage project sites allow them to:
- Add users and limiting access of other users
- Add new project site pages
- Create menu items and arranging them on the webpage
- Assign roles to particular users
- Create a bio page for project team members
- Curate metric reports and Dashboards
- Identify and assigning pages under project menus (e.g. stories, events, news)
- Determine the design elements of the project site (e.g color, images, motion etc)
-
Admin permissions that manage collections allow them to:
- Create new collections
- Publish collections or hiding collections on the project site
- Create or re-organizing the Table of Contents
- Add new pages to collections (e.g. chapter introductions, front matter and back matter)
- Add a new manuscript for a collection
- Create free-text options to form drop-down lists for document metadata (e.g. subject headings).
- Select the user/editor feature standards that will be used in a collection
An Editor can do everything a Contributor can do, and has the following permissions:
-
Editor permissions that manage project sites allow them to:
- Add a project page to the menu
- Add stories and bios about team members working on a collection
- Edit existing project site pages
-
Editor permissions that manage collections allow them to:
- Select default audio shown to readers
- Review and accepting contributions
- Edit translations to an English word
- Edit collection page contents
- Add and editing metadata on documents
- Edit new pages to collections (e.g. chapter introductions, front matter, back matter)
- Identify item and manuscript translation as complete
A Contributor can do everything a Reader can do, and has permissions which allow them to:
- Contribute audio by recording and saving audio
- Transcribe the syllabary
- Contribute to phonetic spellings
- Save all their own contributions and general commentary
- Delete their own contributions and general commentary
- Add tags to Dashboard
- Segment morpheme-boundaries
- Label the morphemic segment
- Add linguistic commentary
- Parse words
- Add phonemic representation (tones)
- Draft pages for a project page/story
A Reader has limited permissions on the website which allow them to:
- Read public site materials
- Add comments
- Save items to Dashboard
A Visitor is a User with no permissions beyond reading public material on the website.
- CARE Principles
- Collective Decision-Making Process
- Data Resilience
- Culturally-Sensitive Information
- UX Design
- Metadata
- User Contributed Audio
- Audio Data Process
- Manuscript Annotation and Analysis
- Language Specific Limitations
- Annotation and Analysis (Before 2024)
- Code Standards
- AWS Diagnostics and Triage Guide
- Cloud Architecture
- Development Environments
- Data Representation
- Data Migration
- User Groups and Roles
- Wordpress Content
- Web Design & Accessibility