- Print
- DarkLight
- PDF
Import Template
In the context of data migration or the appropriation of a new document management system, the creation of structures within the web interface can be a tedious task. In order to overcome this problem, the Constellio team created an import matrix in Excel format (.xls) to greatly speed up the process of entering information related to structures. In this article, we will see and explain the different components of the Excel file, as well as the best method to complete the import matrix.
Record import is an option that allows you to import the taxonomy of virtual spaces, metadata related to document management tools (classification plan, retention schedule, and administrative units), folders, containers, and documents.
1. Principle of the import template
1.1 Components in the Import Matrix
After opening the file in the previous section, you will be able to observe three distinct components:
Description field | ||
---|---|---|
1 | Metadata labels | The first line of the Excel file represents the metadata name for each column. These labels are for informational purposes only, they are not considered when importing data. |
2 | Metadata Code | The second line of the file represents a string of characters (programming strings) associated with the metadata codes for each column. |
3 | Excel Tabs | The tabs inside the Excel document represent each structure to be imported into Constellio. The tab names represent the metadata codes of the structures in the Constellio code. |
1.2 Template Tabs
Each tab in the template represents the types of records that can be imported into Constellio. These tabs represent the metadata schemas of the records to be imported. To learn more about metadata schemas, we recommend reading the article, "Metada schemas." It is important not to change the names of the tabs in the Excel document or the programming stings on line no.2, as there are mechanics for reading the contents of the Excel file, as long as you do not alter the programming elements.
Excel Tab Name | Related Metadata Schema |
---|---|
category | File Plan |
administrativeUnit | Administrative Units |
retentionRule | Retention Schedule |
uniformSubdivision | Uniform subdivision |
folder | Folders |
containerRecord | Containers |
document | Documents |
storageSpace | Boxes |
1.3 Import the template into Constellio
After completing the file of your choice, follow these steps. Information about each type of import can be found below.
- Once the file has been completed, you need to enter Constellio. Click on "Administration" in the navigation menu;
- Click on "Import Records";
- Decide whether the import should be done in a strict or permissive manner. The strict way only allows you to import the entire file if everything is compliant. Whereas, permissive import allows as much record to be imported as possible. Erroneous items will not be imported;
- Click on browse to choose the file and then on "Start Import." After processing, a message will be displayed indicating that the operation was completed successfully and the folders are created.
1.4 Example of custom metadata additions
Here are the steps to follow if you want to incorporate a new custom metadata from your Constellio environment into your Excel template. The metadata must be existing in the collection to successfully import the template.
- View metadata schemas;
- In the type of your choice, consult the metadata;
- Write down: the name of the metadata, its code and its type;
- In the Excel template, add the metadata label in the first line;
- In the second line, enter your code. After the code, you need to designate how to fill in the field. The information to be entered in this step depends on the type of metadata. You can refer to the article "Import template header configurations" for more information.
- Enter the values as expected.
2. Import Hierarchical Structures
Three structures are mandatory to properly operate Constellio's document management module: the classification plan, the retention schedule and the administrative units.
2.1 Classification Plan
To import the classification plan, here is the metadata to be filled in the template.
Metadata Code | Field Name | Type | Description |
---|---|---|---|
id | ID | Obligatory | A unique system identifier to identify the new entry in the classification plan structure. |
code | Code | Obligatory | Code associated with the topic (Coding). |
parentCode | Parent Code | Cisconstantial | Allows you to link one topic to another topic that is hierarchically higher based on the code of the parent field. |
title | Title | Obligatory | Allows you to enter the name of the topic. |
description | Description | Optional | Allows you to add a description. |
keywords | Keywords (separator=;) | Optional | Allows you to add one of the keywords, if necessary. |
retentionRules | Retention rules (separator=;) | Circumstantial | Allows you to bind one or more retention rules to a topic based on the retention rule code. |
deactivate | Disabled | Optional | Allows you to deactivate the topic, which allows you to keep what is already associated with it, but blocks the addition of new folders associated with the topic. Values to be entered: - "True" if the topic is disabled -"False" if the heading is not. |
Abbreviation | Abbreviation | Optional | Identifies an alternative, shorter name for the classification plan topic. |
2.2 Administrative Units
To import the administrative units, here is the metadata to be filled in the template.
Metadata Code | Field Name | Type | Description |
---|---|---|---|
id | ID | Obligatory | A unique system identifier for identifying the new entry in the structure of administrative units. |
code | Code | Obligatory | Code associated with the administrative unit (Codification). |
parentCode | Parent Code | Circumstantial | Allows you to link one unit to another one hierarchically higher based on the code in the parent field. |
title | Title | Obligatory | Allows you to name the administrative unit. |
description | Description | Optional | Allows you to add a description to the unit, if needed. |
decommissioningMonth | Month of disposition | Optional | Allows you to select, for information only, the month of disposition of the administrative unit. |
Address | Address | Optional | Allows you to specify the address of the administrative unit. |
Abbreviation | Abbreviation | Optional | Identify another shorter name for the administrative unit. |
deactivated | Disabled | Optional | Allows you to deactivate the unit, which allows you to keep what is already associated with it, but blocks the addition of new folders associated with the unit. Values to be entered: - "True" if the unit is disabled -"False" if the unit is not. |
2.3 Retention Schedule
To import the retention schedule, here is the metadata to fill in the template.
Metadata about the retention rule
Example of a value to enter
Code | Field Name | Type | Example | Description |
---|---|---|---|---|
id | ID | Obligatory | «1» «2» | Allows you to enter a unique value to identify the record. |
title | Title | Obligatory | "Constitution" | Allows you to name the retention rule. |
code | Rule Number | Obligatory | «111» «801» | Allows you to enter the code for the retention rule. |
description | Description | Optional | "The retention rule relates to..." | Allows you to enter the description of the retention rule. |
corpus | Corpus | Optional | "Reports 1802 v.2" | Allows you to enter the name and provenance collection number of the retention rules. |
corpusRuleNumber | Rule number (corpus) | Optional | «120» | Allows you to refer to the rule number in the original compendium. |
approved | Approved | Conditional | "True" | The retention rule is approved. |
"False" | The retention rule is not approved. | |||
approvedDate type=date pattern=yyyy-MM-dd | Approval Date (yyyy-MM-DD) | Conditional | «2020-10-01» | The entered value respects the input mask of the value. |
juridicReference | Juridic references | Optional | "Civil Code Art.X" | Allows you to enter legal references related to the retention rule. |
generalHow | General comments | Optional | "For project contracts, see..." | Allows you to enter a general note to the retention rule. |
history | History | Optional | "Formerly Rule X" | Allows you to enter a note about the history of the retention rule. |
keywords separator=; | Keywords (separator=;) | Optional | "term1; term2' | Allows you to enter keywords, separated by a semicolon. |
essentialDocuments | Essential documents? | Optional | "True" | The retention rule applies to essential documents. |
"False" | The retention rule does not apply to essential documents. | |||
confidentialDocuments | Confidential documents? | Optional | "True" | The retention rule applies to confidential documents. |
"False" | The retention rule does not apply to confidential documents. | |||
managerAdministrativeUnits | Department responsible | Conditional | "True" | The retention rule is considered to be "Open Holder". |
"False" | The retention rule sets the holders to the retention rule. | |||
administrativesUnits separator=; pattern=code | Departementcode (separator=;) | Conditional | "codeUA1; codeUA2» | Allows you to define responsible administrative units for a retention rule. |
Metadata for the Retention Period Table
Metadata Code | Field Name | Type | Governed value to enter | |
---|---|---|---|---|
copyType structure=copyRetentionRules item=X | Copy Type - Retention rule X | Obligatory | "P" | Allows you to create a primary time limit for a retention rule. |
"S" | Allows you to create a delay that is secondary to a retention rule. | |||
code structure=copyRetentionRules item=X | Code - Retention rule X | Facultative | "C1" «1» | Allows you to set the delay number. |
title structure=copyRentetionRules item=X | Title - Retention rule X | Obligatory | "Preparatory documents" | Allows you to name a retention period. |
description structure=copyRetentionRules item=X | Description - Retention rule X | Optional | "File documents here" | Allows you to describe the amount of documents affected by the retention period. |
mediumTypes structure=copyRetentionRules item=X separator=; pattern=code | Support Codes - Retention rule X (separator=;) | Obligatory | "PA" "PA; DM» | Allows you to set one or more media to a retention period based on the code of the "Media Types" value area. Basically, Constellio has these codes: -Paper = PA; -DM = Magnetic Disc or Digital Document; -Film - FI. |
contentTypesComment structure=copyRetentionRules item=X | Supports notes - Retention rule X | Optional | "R1" "R2" | Let us mention that a remark is applicable to the medium. |
activeRetentionPeriod structure=copyRetentionRules item=X | Active - Retention rule X | Obligatory | «1» «2» «75» | Allows you to enter the value of the fixed period |
«888» «999» | Allows you to enter the value of the open period. | |||
activeRetentionComment structure=copyRetentionRules item=X | Notes Active - Retention rule X | Conditional | "R1" "R2" | Let us mention that a remark is applicable to the time to the asset. |
semiActiveRetentionPeriod structure=copyRetentionRules item=X | Semi-Active - Retention rule X | Obligatory | "0" "1" "2" | Allows you to set a closed delay at the semi-active stage. |
semiActiveRetentionComment structure=copyRetentionRules item=X | Semi-Active Notes - Retention rule X | Optional | "R1" "R2" | Let us mention that a note is applicable to the semi-active delay. |
inactiveDisposalType | Inactive- Retention rule X | Obligatory | "D" "C" | Allows you to set the method of disposal at the inactive stage. |
inactiveDisposalType structure=copyRetentionRules item=X | Notes Inactive - Retention rule X | Conditional | "R1" "R2" | Let it be mentioned that a note is applicable to the inactive period for the first retention period. |
copyRulesComment separator=; | Notes on retention rule | Conditional | "R1: Keep official documents." | Allows you to enter the code of a note as well as the application note. |
2.4 Uniform subdivisions
To import the uniform subdivisions, here is the metadata to be filled in the template. Uniform subdivisions must be entered in the "uniformSubdivision" tab.
Metadata Code | Field Name | Type | Description |
---|---|---|---|
id | ID | Obligatory | A unique identifier that must be given to each of the uniform subdivisions. Uniqueness is valid only for subdivisions. When importing other items, such as the retention schedule, items can have the same identifiers as subdivisions. You can enter a sequential here or copy the code you will give to each of the elements; however, it is important to take into account the uniqueness of the identifier and not to write special characters on it. |
code | Code | Obligatory | The code of the uniform subdivision. |
title | Title | Obligatory | The title of the uniform subdivision. |
description | Description | Optional | A description of the uniform subdivision. |
Comments | Comments | Optional | Comments on uniform Subdivision. |
retentionRule separator=; pattern=code | Retention Rule Codes | Conditional | The code of the retention rule(s) related to that subdivision. If there are multiple partner rules, they must be separated by a semicolon. |
3. Import virtual spaces
The import of the taxonomy present in virtual spaces is done in Import Records.
The Excel file (ImportTaxoEspVirtEspVirt.xls) allows you to create the taxonomy inside one or more virtual space.
- Create the taxonomy in the Excel file with the following columns:
Metadata Code | Field Name | Type | Description |
---|---|---|---|
ID | ID | Obligatory | A unique identifier that must be given to each of the elements. |
Code | Code | Obligatory | The code of the taxonomy of virtual space. |
parentStorageSpace pattern=code | Parent Code | Conditional | Allows hierarchical structuring of taxonomy elements. |
Title | Title | Obligatory | The title of the virtual space taxonomy. |
description | Description | Optional | Description of the taxonomy. |
capacity | Capacity (cm) | Optional | The capacity of the space in cm. |
decommissioningType | Type of disposal | Optional | The type of disposal related to the location. |
containerType pattern=code | Container type(s) | Optional | The type of container that the location can hold. |
- To determine in which virtual space the taxonomy should be created, name the sheet with the code of the space prefixed with the term taxo and having the sequence Type as its sequence .
Example: In this example, the name of the sheet is: taxo362Type.Step to get the code for a virtual space that has already been created- Access Constellio's "Administration";
- Click on "Virtual Spaces";
- Click on "Display" the virtual space you want to retrieve the code;
- In the address bar of the browser, retrieve the last digits of the address.
- Once the file has been completed, it must be uploaded to Constellio to create taxonomies in virtual spaces. To do this, access the Constellio Administration;
- Click on "Import Records";
- Decide whether the import should be done in a strict or permissive manner. The strict way only allows you to import the entire file if everything is compliant. Whereas permissive import allows you to import as many records (therefore, users) as possible. Erroneous items will not be imported;
- Click on browse to choose the file and then on "Start Import." After processing, a message will be displayed indicating that the operation has completed successfully and the taxonomies of the virtual spaces are created.
4. Import Folders
To import your folders, here is the metadata to fill in the template. The Excel file will allow you to import folders into Constellio, but not electronic documents.
Here is the Excel template for importing folders:
For fields that refer to another record (parent folder, category, administrative unit), the link is done by the default ID, but it is also possible to specify the metadata you want to use, pattern=[metadata] in the header.
For example, to use the metadata code to the parent folder field (parentFolder), the header would be set as follows:
- parentFolder
- pattern=code
Metadata Code | Field Name | Type | Description | |
---|---|---|---|---|
id | ID | Obligatory | Text | Identifier to be given to the file. It can be sequential. |
parentFolder | Parent Code | Conditional | Text (Reference) | The identifier of the parent folder. Must refer to a folder that already exists in the system or to a new folder that is imported into the same file. |
title | Title | Obligatory | Text | Title of the folder. |
administrativeUnitEntered | Administrative Unit | Obligatory | Text (Reference) | The code of the administrative unit to which the file is associated. Must refer to an administrative unit that already exists in the system or to a new administrative unit that is imported into the same file. |
categoryEntered | File plan category | Obligatory | Text (Reference) | The section of the classification plan to which the file is to be attached. Must refer to a field that already exists in the system or to a new field that the in imports into the same file. |
retentionRuleEntered | Retention rule code | Conditional | Text (Reference) | The number of the retention rule to which the folder is associated. The record retention rule. Must refer to a retention rule that is related to the field entered. |
keywords | Keywords (separator=;) | Optional | Text (List) | Enter keywords related to this classification plan topic separated by semicolons. |
mediumTypes | Supports | Obligatory | Enumeration (List) | Indicate the support of the file. The codes for the "Media Type" value area must be entered. By default, Constellio has the following types: -PA (Paper); -DM (Magnetic Disc); -FI (Film). |
openingDate | Opening date | Obligatory | Date | Date the file was opened. Format: yyyy-mm-dd |
enteredClosingDate | Closing date | Optional | Date | Date the file was closed. Format: yyyy-mm-dd |
actualTransfertDate | Transfer Date (yyyy-MM-dd) | Optional | Date | Date the folder was transferred to semi-active. Format : yyyy-MM-dd |
actualDestructionDate | Date of Destruction | Optional | Date | Date the record was destroyed, if applicable. Format: yyyy-mm-dd |
actualDepositDate | Date of Deposit | Optional | Date | Date the file was placed on file, if applicable. Format: yyyy-mm-dd |
copyStatusEntered | Item Status Seized | Obligatory | Boolean | Corresponds to item status. P = Primary S = Secondary |
type pattern=code | Type | Optional | Reference | Corresponds to the type of folders. You must enter the code of the specific folder schema to which you want to link this folder. |
securityClearanceLevels | Security clearance | Optional | Reference | The security classification to be applied to the file. Must include the security classification wording to be applied. |
description | Description | Optional | Text | Description related to the folder. |
container | Container | Optional | Reference | Container linked to the folder. Must include the number of the means of containment. |
linearSize | Linear size (cm) | Optional | Number | Corresponds to the linear measurement of the backrest in cm. |
abbreviation | Abbreviation | Optional | Character String | Abbreviation of the folder name. |
5. Import containers
To import your contents, here is the metadata to fill in the template. The information on the containers to be imported must be entered in a spreadsheet with the title "containerRecord".
Here is the Excel template for importing containers:
Metadata Code | Field Name | Type | Description | |
---|---|---|---|---|
id | ID | Obligatory | Text | The identifier to be given to the container. It can be sequential. |
type | Type of Container | Obligatory | Reference | The code of the license plate type, as defined in the value field. |
identifier | Container No. | Obligatory | Character String | Title of the container. |
decommissioningType | Disposition type | Obligatory | Reference | The type of decommissioning. Possible values are: T = Transfer to assets C = Retention D = Destruction |
storageSpace | Storage space | Optional | Reference | The code of the location, as defined in the value field. |
full | Full? | Optional | Boolean | Whether the container is full or not. Accepted values: TRUE = Full FALSE = Not Full |
description | Description | Optional | Character String | Description of the container. |
position | Position | Optional | Character String | Position in the location. |
Capacity | Capacity (cm) | Optional | Number | Container capacity (in cm). |
administrativeUnits | Administrative Units | Obligatory | Reference | The code of the administrative unit(s) to which the file is associated. |
createdBy | Created by | Obligatory | Reference | The username of the person who created the license plate. |
modifiedBy | Modified by | Optional | Character String | The username of the last person who modified the container. |
realTransferDate | Transfer Date | Optional | Date | Date the folder was transferred to semi-active. Format: yyyy-mm-dd |
completionDate | Completion Date | Optional | Date | Completion Date Format: yyyy-mm-dd |
realDepositDate | Deposit Date | Optional | Date | Date of deposit of the container. Format = yyyy-mm-dd |
borrowed | Borrowed? | Optional | Boolean | Whether the container has been printed or not. Accepted values: TRUE = Borrowed FALSE = Not borrowed |
borrower | Borrower | Optional | Character String | The username of the person who borrowed the property. |
borrowDate | Date of Borrowing | Optional | Date | The date the container was borrowed. |
realReturnDate | Return Date | Optional | Date | Date of return of the container. Format: yyyy-mm-dd |
6. Import documents
To import the card of your documents, here is the metadata to fill in the template.
useTitleAsFilename=true
Here is the Excel template for importing document cards:
System Code | Field Name | Type | ||
---|---|---|---|---|
id | ID | Obligatory | Character String | Document ID. By default, this value is recorded in the "LegacyIdentifier" metadata and a new system id will be generated. To use the system identifier when updating existing documents instead, add the line "importAsLegacyId=false" to the header . |
type pattern=code | Type | Optional | Reference | Corresponds to the value domain of the folder type. It is possible that other metadata will become mandatory, depending on the configuration of the chosen type. If left blank, the default folder type will be used. |
folder | Folder | Obligatory | Reference | The identifier of the folder in which the document is located. |
title | Title | Obligatory | Character String | Corresponds to the title of the document card. When updating an existing document, it is possible to synchronize the title of the contained file with the title of the card by adding the line "useTitleAsFilename=true" to the header. |
keywords separator=; | Keyword | Optional | Character String (Multivalue) | Corresponds to the keywords used for the search. Use the ";" character to separate the different entries. |
description | Description | Optional | Text | Description related to the document. |
author | Author | Optional | Character String | Corresponds to the author of the document. Doesn't need to be a registered user in the system. |
Company | Organization | Optional | Character String | Corresponds to the organization. |
subject | Subject | Optional | Character String | Corresponds to the subject of the document. |
modifiedBy pattern=username | Modified by | Optional | Reference | Corresponds to the last user who modified the document card. If not specified, the user performing the import will be used by default. |
createdBy pattern=username | Created by | Obligatory | Reference | Corresponds to the user who created the document card. If not specified, the user performing the import will be used by default. |
7. Import Value Domains
To import items from a value domain, here is the metadata to fill in the template.
- You must have created your value domain in Constellio;
- Put the code of the value domain in the template tab;Value Domain CodeTo get the code of the value domain, look at your domain and take the information from the URL.
- Fill in the information to create the value domain;
- Import into Constellio.
Metadata code | Field Name | Type | Description |
---|---|---|---|
id | ID | Obligatory | Identifier of the value. |
title | Title | Obligatory | Corresponds to the title of the value. |
code | Code | Obligatory | Corresponds |
Abbreviation | Abbreviation | Optional | Corresponds to the abbreviation of the value domain. |
description | Description | Optional | Matches the description related to the value domain. |