Updated documentation, reflecting the organization=>group change

Author: LaurensRietveld

docs/triply-api/index.md

@@ -77,7 +77,7 @@ https://api.INSTANCE/datasets/ACCOUNT/DATASET/
 Upper-case letter words must be replaced by the following values:
 
 - `INSTANCE` :: The host name of the TriplyDB instance that you want to use.
-- `ACCOUNT` :: The name of a specific user or a specific organization.
+- `ACCOUNT` :: The name of a specific user or a specific group.
 - `DATASET` :: The name of a specific dataset.
 
 Here is an example of a URI path that points to the Triply API for the Pokémon dataset:

docs/triply-db-getting-started/admin-settings-pages/index.md

@@ -20,7 +20,7 @@ The general overview gives an insight into the software version of the instance.
 
 ### Accounts overview
 
-The accounts overview shows how many organizations and users are in this instance. The organizations and users are shown in a counter if no limit is set. If a limit is set on the number of organizations and/or users of the instance a gauge is shown.
+The accounts overview shows how many groups and users are in this instance. The groups and users are shown in a counter if no limit is set. If a limit is set on the number of groups and/or users of the instance a gauge is shown.
 
 
 ### Data overview
@@ -126,7 +126,7 @@ For editing the side-wide prefixes follow the next steps:
 
 ## Roles page
 
-The roles page allows administrators to manage the roles that can be assigned to organization members. Roles define which actions organization members can perform within an organization. Roles only apply to organization members, not to personal accounts.
+The roles page allows administrators to manage the roles that can be assigned to group members. Roles define which actions group members can perform within a group. Roles only apply to group members, not to personal accounts.
 
 The roles page is accessible by clicking on the "Admin settings" link in the user menu (top-right corner) and clicking the "Roles" tab.
 
@@ -137,10 +137,10 @@ TriplyDB includes two built-in system roles that cannot be deleted:
 
 <dl>
   <dt><code>owner</code></dt>
-  <dd>Full access to all account resources and settings, including the ability to manage organization members and their roles.</dd>
+  <dd>Full access to all account resources and settings, including the ability to manage group members and their roles.</dd>
 
   <dt><code>member</code></dt>
-  <dd>Can manage resources (datasets, queries, stories) but cannot manage organization members or delete the organization.</dd>
+  <dd>Can manage resources (datasets, queries, stories) but cannot manage group members or delete the group.</dd>
 </dl>
 
 
@@ -165,7 +165,7 @@ Custom roles can be edited or deleted at any time from the roles page using the
 
 ### Assigning roles
 
-Roles are assigned to organization members in the member settings of each organization. Organization members with sufficient permissions (such as owners) can assign roles to other members. See [Organization.addMember()](../../triplydb-js/organization/index.md#organizationaddmemberuser-user-role-role) for how to assign roles programmatically.
+Roles are assigned to group members in the member settings of each group. Group members with sufficient permissions (such as owners) can assign roles to other members. See [Group.addMember()](../../triplydb-js/group/index.md#groupaddmemberuser-user-role-role) for how to assign roles programmatically.
 
 
 ## Account overview page
@@ -180,7 +180,7 @@ The filters on top of the table can be used to filter the following columns:
   <dd>The name of the account, you can order the table based on the alphanumeric ordering, and filter based on the sequence of characters appearing in the filter. The name is also a URL that brings you to the location of the account. </dd>
 
   <dt>Type</dt>
-  <dd>Type of the account, this can either be 'Organization' or 'User'. In the filter you can select a specific account type or 'All' account types.</dd>
+  <dd>Type of the account, this can either be 'Group' or 'User'. In the filter you can select a specific account type or 'All' account types.</dd>
 
   <dt>Display name</dt>
   <dd>The display name of the account, often an account has both a name and a display name. The display name is not limited to a specific set of characters, as it is not used as an URL. You can order the table based on the alphanumeric ordering, and filter based on the sequence of characters appearing in the filter. </dd>
@@ -214,7 +214,7 @@ For each account you can execute the following actions:
 
 <dl>
   <dt>Open account settings</dt>
-  <dd>For each account, there is a button such that the administrator can directly go to the account settings of the user or organization. The account settings are behind the `cogwheel` button. </dd>
+  <dd>For each account, there is a button such that the administrator can directly go to the account settings of the user or group. The account settings are behind the `cogwheel` button. </dd>
 </dl>
 
 
@@ -227,15 +227,15 @@ The type of account can be observed based on the following icons:
 
 | **Icon**              | **Account type** |
 | --------------------- | ---------------- |
-| ![](../../assets/organization.png) | organization     |
+| ![](../../assets/organization.png) | group            |
 | ![](../../assets/user.png)         | user             |
 
 
 ### Create a new user
 
 New users can only be created by administrators by performing the following steps:
 
-1. Click on the “Admin settings” link in the user menu (top-right corner) and click the “Accounts” tab. This brings up an overview of all users and organizations on the TriplyDB instance.
+1. Click on the “Admin settings” link in the user menu (top-right corner) and click the “Accounts” tab. This brings up an overview of all users and groups on the TriplyDB instance.
 
 2. Click the “Add user” button.
 

docs/triply-db-getting-started/data-stories/index.md

@@ -18,8 +18,8 @@ As shown in the image below, in the top right corner of the page, there is a men
 
 - **Story settings**: Here you can change the title and the access level of your story.
 - **Change banner**: Here you can change the banner, just choose an image that you want as your banner (wide images work best).
-- **Copy**: To copy the story to a different user or organization.
-- **Transfer**: To transfer the story to a different user or organization.
+- **Copy**: To copy the story to a different user or group.
+- **Transfer**: To transfer the story to a different user or group.
 - **Embed**: HTML to embed the story in a web page using an iFrame.
 - **Print**: Dialog and print options to print the story.
 - **Delete**: To delete the story.

docs/triply-db-getting-started/reference/index.md

@@ -23,25 +23,25 @@ The Access Level control (see [Figure 1](#fig-access-level-control)) is availabl
 
 ### Access Level meaning
 
-What an Access Level means, depends on whether content belongs to a user or to an organization. The following table contains the meaning of the Access Levels for content that belongs to a user:
+What an Access Level means, depends on whether content belongs to a user or to a group. The following table contains the meaning of the Access Levels for content that belongs to a user:
 
 | **Icon**                       | **Access Level** | **Meaning**                                                                       |
 | ------------------------------ | ---------------- | --------------------------------------------------------------------------------- |
 | ![](../../assets/private.png)  | Private          | Content is only accessible to you.                                                |
 | ![](../../assets/internal.png) | Internal         | Content is accessible to anyone who is logged into the same TriplyDB environment. |
 | ![](../../assets/public.png)   | Public           | Content is accessible to anyone on the Internet.                                  |
 
-The following table contains the meaning of the Access Levels for content that belongs to an organization:
+The following table contains the meaning of the Access Levels for content that belongs to a group:
 
 | **Icon**                       | **Access Level** | **Meaning**                                                                       |
 | ------------------------------ | ---------------- | --------------------------------------------------------------------------------- |
-| ![](../../assets/private.png)  | Private          | Content is only accessible to organization members.                               |
+| ![](../../assets/private.png)  | Private          | Content is only accessible to group members.                                      |
 | ![](../../assets/internal.png) | Internal         | Content is accessible to anyone who is logged into the same TriplyDB environment. |
 | ![](../../assets/public.png)   | Public           | Content is accessible to anyone on the Internet.                                  |
 
 Access Levels cannot be specified for the following content. This means that this content is always publicly accessible:
 
-- Organizations, including their metadata and members.
+- Groups, including their metadata and members.
 - Users, including their metadata.
 
 ### Access Level dependencies
@@ -65,9 +65,9 @@ These access levels are often used for the following workflow:
 
 ## Roles
 
-TriplyDB uses roles to control what actions organization members can perform. While [Access Levels](#access-levels) control *who can see* content (visibility), roles control *what actions* members are allowed to take within an organization.
+TriplyDB uses roles to control what actions group members can perform. While [Access Levels](#access-levels) control *who can see* content (visibility), roles control *what actions* members are allowed to take within a group.
 
-Roles only apply to organization members. Personal user accounts are not affected by roles.
+Roles only apply to group members. Personal user accounts are not affected by roles.
 
 ### System roles
 
@@ -76,13 +76,13 @@ Two system roles are always available:
 | **Role**     | **Description**                                                                                      |
 | ------------ | ---------------------------------------------------------------------------------------------------- |
 | `owner`      | Full access to all account resources and settings, including member management.                       |
-| `member`     | Can manage resources (datasets, queries, stories) but cannot manage members or delete the organization. |
+| `member`     | Can manage resources (datasets, queries, stories) but cannot manage members or delete the group.      |
 
 ### Custom roles
 
-Administrators can create custom roles with a specific subset of permissions. This allows organizations to grant exactly the level of access that is appropriate for each member. For example, a custom role could allow read access to all datasets without the ability to create new ones, or grant write access without the ability to manage SPARQL services.
+Administrators can create custom roles with a specific subset of permissions. This allows groups to grant exactly the level of access that is appropriate for each member. For example, a custom role could allow read access to all datasets without the ability to create new ones, or grant write access without the ability to manage SPARQL services.
 
-Custom roles are configured by administrators in the [Admin Settings](../admin-settings-pages/index.md#roles-page). Roles are assigned to members in each organization's member settings.
+Custom roles are configured by administrators in the [Admin Settings](../admin-settings-pages/index.md#roles-page). Roles are assigned to members in each group's member settings.
 
 ### API token permissions
 

docs/triply-db-getting-started/viewing-data/index.md

@@ -137,7 +137,7 @@ It is sometimes useful to share a SPARQL query with somebody else, or to have a
 
 ### Transfer a SPARQL query
 
-The SPARQL queries could be transferred to another account or an organization. To do that, go to the setting field at the query page,
+The SPARQL queries could be transferred to another account or a group. To do that, go to the setting field at the query page,
 
 ![Transfer a SPARQL query](../../assets/where-find-transfer.png)
 
@@ -149,19 +149,19 @@ and then choose where the SPARQL query should be moved to:
 
 ![Transfer a SPARQL query](../../assets/transfer-to-organization.png)
 
-After the destination is set you would be redirected to the SPARQL query new page. The SPARQL query could be transferred from an account to an organization and vice versa.
+After the destination is set you would be redirected to the SPARQL query new page. The SPARQL query could be transferred from an account to a group and vice versa.
 
 ### Copy a SPARQL query
 
-Users can copy SPARQL queries to another account or an organization. To do that, click on three dots in the upper right corner of the query and choose the copy option:
+Users can copy SPARQL queries to another account or a group. To do that, click on three dots in the upper right corner of the query and choose the copy option:
 
 ![Copy query](../../assets/copyQuery.png)
 
 Then, choose where the SPARQL query should be moved to:
 
-![Select organization](../../assets/selectOrganization.png)
+![Select group](../../assets/selectOrganization.png)
 
-After setting the destination, you will be redirected to the SPARQL query new page. The SPARQL query can be copied from an account to an organization and vice versa.
+After setting the destination, you will be redirected to the SPARQL query new page. The SPARQL query can be copied from an account to a group and vice versa.
 
 ## ElasticSearch
 

docs/triplydb-js/account/index.md

@@ -2,7 +2,7 @@
 
 # Account
 
-Instances of the `Account` class denote TriplyDB accounts. Accounts can be either organizations ([`Organization`](../organization/index.md#organization)) or users ([`User`](../user/index.md#user)).
+Instances of the `Account` class denote TriplyDB accounts. Accounts can be either groups ([`Group`](../group/index.md#group)) or users ([`User`](../user/index.md#user)).
 
 Account objects are obtained by calling the following method:
 
@@ -39,7 +39,7 @@ The `metadata` argument optionally specifies the access level and other importan
     <p>The access level of the dataset. The following values are supported:</p>
     <dl>
       <dt><code>'private'</code> (default)</dt>
-      <dd>The dataset can only be accessed by organization members.</dd>
+      <dd>The dataset can only be accessed by group members.</dd>
       <dt><code>'internal'</code> </dt>
       <dd>The dataset can only be accessed by users that are logged into the TriplyDB server.</dd>
       <dt><code>'public'</code></dt>
@@ -309,36 +309,37 @@ const newStory = await user.addStory('name-of-story', {
 ```
 
 
-## Account.asOrganization()
+<a id="accountasorganization"></a>
+## Account.asGroup()
 
-Casts the TriplyDB account object to its corresponding organization object.
+Casts the TriplyDB account object to its corresponding group object.
 
-Class [Organization](../organization/index.md#organization) is a specialization of class [Account](#account).
+Class [Group](../group/index.md#group) is a specialization of class [Account](#account).
 
-Calling this method on an `Organization` object does nothing.
+Calling this method on a `Group` object does nothing.
 
 ### Examples
 
-The following snippet retrieves the account named `'Triply'` and casts it to an organization:
+The following snippet retrieves the account named `'Triply'` and casts it to a group:
 
 ```ts
 const account = await triply.getAccount('Triply')
-const organization = account.asOrganization()
+const group = account.asGroup()
 ```
 
 ### Alternatives
 
-This method is not needed if the organization is directly retrieved with the specialization method [`App.getOrganization(name: string)`](../app/index.md#appgetorganizationname-string).
+This method is not needed if the group is directly retrieved with the specialization method [`App.getGroup(name: string)`](../app/index.md#appgetgroupname-string).
 
 The following snippet returns the same result as the above example, but in a more direct way:
 
 ```ts
-const organization = await triply.getOrganization('Triply')
+const group = await triply.getGroup('Triply')
 ```
 
 ### See also
 
-This method returns an organization object. See class [Organization](../organization/index.md#organization) for an overview of the methods that can be called on such objects.
+This method returns a group object. See class [Group](../group/index.md#group) for an overview of the methods that can be called on such objects.
 
 
 ## Account.asUser()
@@ -370,7 +371,7 @@ const user = await triply.getUser()
 
 ### See also
 
-This method returns an organization object. See class [Organization](../organization/index.md#organization) for an overview of the methods that can be called on such objects.
+This method returns a user object. See class [User](../user/index.md#user) for an overview of the methods that can be called on such objects.
 
 
 ## Account.ensureDataset(name: string, metadata?: object)
@@ -490,13 +491,13 @@ The information object for accounts includes the following keys:
   <dd>An array containing the pinned items (datasets, stories and queries) for the account.</dd>
 
   <dt><code>type</code></dt>
-  <dd>The account type: either <code>organization</code> or <code>user</code>.</dd>
+  <dd>The account type: either <code>org</code> (for a group) or <code>user</code>. The <code>org</code> value is preserved for backwards compatibility — groups were previously called organizations.</dd>
 
   <dt><code>role</code></dt>
   <dd>The role of the account</dd>
 
   <dt><code>orgs</code></dt>
-  <dd>An array of organizations of which the account is a member.</dd>
+  <dd>An array of groups of which the account is a member.</dd>
 
   <dt><code>Email address</code></dt>
   <dd>The email address of the account.</dd>
@@ -549,7 +550,7 @@ A pinned item is an item that is displayed in a prominent way on the account web
 
 ### Order considerations
 
-The order in which the pinned datasets are returned reflects the order in which they appear on the organization homepage (from top-left to bottom-right).
+The order in which the pinned datasets are returned reflects the order in which they appear on the group homepage (from top-left to bottom-right).
 
 ### Examples
 
@@ -939,8 +940,8 @@ async (ctx) => {
   // Specify the environment variable, if necessary
   const _dataset =
     process.env['MODE'] === 'Production'
-      ? (await app.triplyDb.getOrganization(organization)).getDataset(dataset)
-      : (await app.triplyDb.getUser()).getDataset(organization + '-' + dataset)
+      ? (await app.triplyDb.getGroup(group)).getDataset(dataset)
+      : (await app.triplyDb.getUser()).getDataset(group + '-' + dataset)
 
   // Update the display name
   if (displayName) await (await _dataset).update({ displayName })