In this page, you will find information to the configuration options that you have for your National Documents instance.
The different areas described below are available for set up in the Excel template for configuration, that you will/have receive/d, and that you can define based on your needs or usage of the application:
Folder structure & Role mapping
Folder structure for TC/SC/WG, folder names, folder documents types and permissions. We recommend to keep configurations simple and harmonized and have the same default folder structure for TCs, SCs and WGs. If needed, these can be different.
Folder names
The proposed configurations are based on the 2020 ISO default folder template.
Document types
In the Documents platform, content types can be forced based on folders. This avoids having inconsistencies in the documents location. For example, we recommend to not allow documents of type "Ballot" allowed in the "Meetings" folder since this can be confusing for experts.
Please note that the following documents types are N documents:
- General
- Meeting
- Decision (i.e. Resolution and recommendation)
- Ballot
- Project
- NEW Publication: This new document type is mainly aimed to circulate Publications that require an additional security level, as Publication document type is by default watermarked-on-the-fly with the user email address & date of download. Read more about configuration options. Should you be interested in hearing more, please contact isolutions@iso.org
N documents have specific additional meta data (Meeting > Agenda, Minutes etc) and a lifecycle can apply (publication required, frozen edition after publication etc).
The following document types are not N documents and therefore do not need publication and only have a title and a description as available meta data:
- File
- Folder
- Link
Permissions
R: Stands for Read
W: Stands for Write (and delete)
Greyed out cells cannot be changed
- Committee roles: these roles apply at the level of the national committee only. For example, when the user administrator assigns a role of committee member to a user on a specific national committee
- Structure role: these roles apply to the entire technical committee structure. For example, the national secretary of TC 1 is automatically granted read access on committee TC 1/SC 3.
- Tenant role: these roles apply on all national committees. For example an employee of your organization can be granted read access to all national committees simply by assigning the role of employee of your organization in the Global Directory.
General settings
| Option | Possible values | Description |
|---|---|---|
|
Tenant folder (1st level) |
NSB Acronym |
The tenant folder is the root folder in which all committees and content are stored. |
|
Tenant (2nd level) |
i.e. Technical groups, Governance groups, etc. |
This is the default configuration for regrouping technical committees. While most NSBs only manage technical groups (in which case, the tenant = "technical groups"), some NSBs also manage national governance groups with a different configuration and have two tenants setup. Both tenants are regrouped under one tenant folder. |
|
Subtenant (originator) (optional 3rd level) |
ETCI committees, any technical sector that needs a different configuration setup (different folders or different permissions) |
This is an optional level in which different configuration can be defined based on e.g. an originator |
|
Committee field |
All, Technical, Policy development, Governance, External, Non technical |
The different fields are: Technical, Policy development, Governance, External, Non technical (same as for ISO committees). A field type allow a different configuration based on the type (e.g. Technical committees could have a configuration and Governance committees could have a different configuration). If set to "All" then the configuration for all fields will be the same. |
|
Committee levels |
We recommend having unified configurations regardless of the committee level (TC, SC, WG), but different configuration could apply. |
|
|
Folder structure template |
Name of a configuration describing the default committee folder structures allowed items per folder and permissions. |
|
| National projects | ||
|
National project picker activated |
TRUE/FALSE |
Defines if the NPP widget should be displayed (this option is not yet available and is reserved for a future usage) |
|
National project stages |
TRUE/FALSE |
For Project documents, a new field called "stage" is available. This field includes the main project national stages: NP - New Proposal, WD - Working Draft, CD - Committee Draft, DTR - Draft Technical Report, DTS - Draft Technical Specification, WA - Workshop Agreement, SR - Systematic Review, DAmd - Draft Amendment, Cor - Corrigendum, DS - Draft Standard, FDS - Final Draft Standard, Pub - Published, Other |
|
National ballots |
||
|
National ballot picker Activated |
TRUE/FALSE |
Display the national ballot picker when uploading documents of type Ballot. This feature requires National Ballots as it will be linked to national ballots of the committee. |
|
National ballot documents widget displayed |
TRUE/FALSE |
Display the Ballot documents widget which list ballots and their related documents for open and ballot closed in the last 12 months |
|
National meetings |
||
|
National meeting picker activated |
TRUE/FALSE |
Display the national meeting picker when uploading documents of type Meeting. This feature requires National Meetings as it will be linked to national meetings of the committee. |
|
National meeting documents widget activated |
TRUE/FALSE |
Display the Meetings documents widget which lists national meetings and their related documents for open and meetings closed in the last 12 months |
|
Documents |
||
|
National documents widget activated |
TRUE/FALSE |
Display the widget for national documents (only for ISOlutions members) |
|
International documents widget activated |
TRUE/FALSE |
Display the widget for mapped ISO/CEN documents (for NMC and ISOlutions members) If activated, the widget is only displayed if the committee mirrors at least an ISO or CEN committee |
|
Decision subtypes to exclude |
Resolutions, Recommendation, Decision |
The Decision type can have the 3 subtypes: Resolutions, Recommendation and Decision. If one of these subtypes should be excluded then it should be listed in this field By default "Decision" is excluded |
|
Multiple coversheet templates |
TRUE/FALSE |
Allow to create multiple coversheet templates with different information and logos. Required for ISO members delegating standard development to different SDOs (e.g. UNI) |
|
N-document life-cycle model |
Classic, Available at creation time, Hybrid, None |
The life cycle defines what needs and can be done once an N documents is uploaded. The 4 recommended options are:
|
|
Email to members available to Contributors |
TRUE/FALSE |
Contributors can use the Email to member feature in the Member list |
|
NEW Email notifications: allow senders to select a subset of the audience of the committee. |
TRUE/FALSE (default: FALSE) |
When notifying a document or sending an email to members from Documents, the sender can select manually people in the member list (VS all the committee) |
|
Multiple Notification Templates |
TRUE/FALSE |
The NSB has multiple notification templates |
|
Automatic Notifications |
TRUE/FALSE |
The NSB uses the automatic documents notification scheduler |
|
NEW Exclude international folder from automatic Notifications |
ISO/CEN folder name(s) to be excluded. |
The NSB excludes some folder of the ISO or CEN top default folder structure. One of the folder usually excluded is the Ballots folder since NSBs using NEB already get a copy through National Positioning Ballots. |
| Use cross-committees documentation folder? | TRUE/FALSE | For each tenant/working area configuration, a dedicated documentation folder can be specify with permissions related to that particular tenant/working area. For example, for a "Technical group" tenant/working area, one would want all people registered in a technical committee to have access to the national support documentation while and have the User administrators and staff of the NSB to have write permissions. In parallel, a national governance tenant/working area might only have read permissions for people registered in the national governance committees. The recommendation is to have one folder set at root level (tenant folder) so a general common documentation folder can be accessed by all national users. |
Members List
Roles and order in which they should be displayed in the Member and Access list.
Columns to display/hide (e.g. Role, Appointed by, Salutation, Name, Email, Phone) on the Member and Access list.
Branding
The logo of your organization and color them is used to brand your national environment. We therefore require the following information:
Logo specification (preferably provide a logo in vector format).
The NSB might have a different logo versions (small, big) and "inversed" logo for dark backgrounds.
RGB or hex color codes for the top line of the user interface and the notifications
Example of logo in notifications
Example of logo in PDF cover pages
Example of logo and color theme in the header of the user interface
Folders migration mapping
The table shows which source folders are migrated to which destination folder, as well as source folders which will not be migrated.