When you import a file from NBS Building/ Landscape you will be sent an email. The email contains an attached MS Excel spreadsheet which is a record of what was imported.

This article explains the report and what we recommend checking.

When you import a live project file into Chorus we recommend saving the import report for your records.

Topics

• Reading the report
• Checking the report for what has not been imported
  • 1. Clauses that were not imported
  • 2. Clauses that contain objects or tables
  • 3. Clauses that are not-up-to-date
  • 4. Clauses that contain user guidance notes

Reading the report

• The report is split into two halves; ‘in NBS Building/ Landscape’ and ‘In NBS Chorus.
• It shows what the file contained in NBS Building/ Landscape and what was imported into Chorus.
• There is a row for every heading and clause in the NBS Building/ Landscape file.

Checking the report for what has not been imported

1. Clauses that were not imported

It is important to check the report for any clauses that did not get imported. 

The ‘Imported’ column will be set to TRUE for clauses that have been imported and FALSE for clauses that were not.

Chorus has been developed to import NBS and user-authored clauses so it unlikely clauses will not be imported but it is important to check.

If clauses are not imported you could recreate them in Chorus manually. This may be an acceptable workaround depending on how many are affected. If you do find clauses not being imported please contact NBS Customer Support so we can investigate.

2. Clauses that contain objects or tables

It is important to check the report for any clauses which contained objects or tables in NBS Building/ Landscape.

The column with heading ‘Note type’ contains three entries; Information, Warnings, Error. ‘Warning’ indicates when the clause contains objects or tables. An object could be an image or an embedded file. The ‘Notes column will say ‘Object (s) not imported’ or ‘Table(s) not imported’.

Objects and tables are not supported by Chorus and are not imported. We recommend reviewing the original file and replicating the information conveyed in the object/ table differently. This could be a text description or a hyperlink to the information if it is hosted online.

3. Clauses that are not-up-to-date

It is important to check the report for any clauses which could contain out-of-date technical information. However, depending on the project, it may be your intention to bring in historical technical information.

The import report indicates the currency of a clause where possible using the ‘Up-to-date’ column. Each row will contain one of three entries; ‘Up-to-date’, ‘Unknown. Please check guidance’ or it will be empty.

Up-to-date – means the clause was an NBS clause in NBS Building/ Landscape and it was imported as an NBS clause in Chorus. The version of the clause being imported is the same as the version it is being matched to in Chorus. For example, the clause in NBS Building/ Landscape was added from the 2020-2 July library and it was imported into the same content set update in Chorus. 

Unknown. Please check guidance – means the clause was an NBS clause in NBS Building/ Landscape and it was imported as an NBS clause in Chorus. However, the version could not be determined. In this situation, it is important to compare the clause to what the guidance says. The guidance will be the latest guidance available in Chorus for that clause. An example of something to check would be if a standard cited in the clause is different from what is in the guidance. 

Empty – means the clause was imported as a user clause in Chorus. You need to check the clause is correct but NBS cannot offer any support here. Clauses are imported as user clauses when;

a)    They were authored from scratch in NBS Building/ Landscape.

b)    They originated from NBS clauses and could not be matched to an equivalent clause in NBS Chorus.

4. Clauses that contain user guidance notes

It is important to check the report for any clauses with user guidance notes that contain images. User guidance notes found in the NBS Building/ Landscape file are imported as Spec notes in Chorus. However, images are not imported and should be transferred over manually.

The column with the heading 'Note type' will be set to 'Warning'. The ‘Notes’ column will be set to ‘User guidance image(s) not imported’.