2.3 Getting familiar with the LCA Collaboration Server dashboard
The figure below shows the dashboard of the LCA Collaboration Server, this is the first page after login. The icons in the top right corner are explained in this table.
Icon | Feature |
---|---|
Dashboard, takes user back to home page | |
Admin area (creating users, teams, etc.), only for admin users. | |
Task log, brings back to task overview (optional feature) | |
Log-out | |
Review mode (on/off), enables to add comments on datasets, ready for review | |
Debugging (on/off) , show detailed error stacktraces, only for admin users |
To the left of the dashboard we have a menu:
Activities tab: displays the latest activities relating to the repositories the user is involved with. It is a log of the commits, tasks and comments.
Repositories tab: is the central place for the repositories1 the user is involved with. Repositories can be managed from here, including creating a new repository, or importing one.
Groups tab: holds the groups that the user is part of. A group is made up of a team of users that works on a number of repositories. For example, if a new member joins an LCA team working with 5 repositories in the LCA Collaboration Server, this new user can join the “group” containing those 5 repositories and have access to all of them at once instead of having to be added to each of the repositories individually. Once a group is entered, the user can add tags, or add and edit the members, depending on their user role (jump to section).
Tags: this tab brings the user to the tag cloud (experimental feature).
Clicking on the user’s name in the bottom left corner of the LCA Collaboration Server dashboard opens the user dashboard, see the following figure. This gives access to account properties, messaging and notification settings. The dashboard may look slightly different for members with different user rights.
2.3.1 Expanding on the repository dashboard
After clicking on a repository in the repository library (Figure: The LCA Collaboration Server dashboard), the following dashboard is displayed:
The first tab, Repository, shows the information of the repository. Further down, there is the “Metadata” section, a great opportunity to document the database. The repository ID is the “groupname/repositoryname”. The repository name can be changed following:
Move -> Name
Activities logs the activities of the repository (i.e. commits or comments to the repository), which are also displayed in the “Activities” of the main menu.
The Data sets tab allows one see all of the data in the repository, and to download and export repositories and datasets through the download feature shown in the figure below. It allows one to download individual versions (commits) of a repository as JSON-LD or ILCD.
The Commits tab logs all of the commits to the repository.
The Comments tab holds all of the comment history of comments to committed processes.
Adding tags to repositories can be done in Repository tab. Individual datasets can also be tagged, as well as full repositories.
The Members tab holds a record of both the members of the repository, and the members of the repository through a group. Members can be added and deleted here, and the user roles described in a following subsection can also be changed.
Furthermore, the “owner” of the repository will be able to see the following managing tools for their repository:
More on user roles will be explained in a following subsection, and these buttons will also be explained in advanced features.
2.3.2 Expanding on the admin area dashboard
One can access the admin area by clicking on the icon. The icon can only be seen by data managers, user managers, or server administrators. The regular user cannot see it. From the admin area, one can create, delete or manage repositories, users, groups of repositories and teams of users. In Settings the admin user can configure the Collaboration Server and enable or disable features.
2.3.3 Groups and user roles
The group feature allows one to create working groups to which a repository or several repositories (see below) can be assigned. A working group can be managed by assigning different user roles to its members.2 A summary of the differences is displayed in the table below.
Rights | Reader | Contributor | Reviewer | Editor | Owner |
---|---|---|---|---|---|
Read repositories and fetch contents | x | x | x | x | x |
Commit data to repositories | x | x | x | x | |
Comment specific fields of data sets | x | x | x | ||
Review comments | x | x | x | ||
Manage comments | x | x | |||
Manage reviews | x | x | |||
Create repositories | x | ||||
Edit repository members | x | ||||
Adjust settings | x | ||||
Move repositories | x | ||||
Delete repositories | x | ||||
Generate change log | x |
A repository is the equivalent to a database in openLCA and consists of grouped data sets (projects, product systems, processes, flows, indicators and parameters and background data). Basically, a repository mirrors the local openLCA databases of the working group’s users.
Data manager (administrate libraries) and user manager (create users and teams) are other additional roles.