Skip to content

Latest commit

 

History

History
75 lines (42 loc) · 5.89 KB

bSDD import tutorial.md

File metadata and controls

75 lines (42 loc) · 5.89 KB

How to upload data dictionary to bSDD

1. Prepare the content

The primary form of data upload to bSDD is a properly structured JSON file. In the data model documentation, we specify what such a file should contain and how to structure it.

You can manually create such a file by coping the JSON template, or use the Excel template instructions.

Alternatively, use one of the third-party tools to manage and upload data dictionaries in bSDD.

2. Register your organisation

Each data dictionary in bSDD is published on behalf of a registered organisation. If this is the first time you are uploading, you need to register your organization in bSDD and connect the e-mail address you used to log in to that organization. To achieve this, please fill out the Organization registration form.

As part of bSDD housekeeping, we manually review each request. For that reason, it can take up to a few days. As soon as you've received a reply, you can proceed to the next step.

Do you want to only experiment with bSDD without registering your organisation? We can add you to the DEMO organisation. For this and other requests, contact us at: bsdd_support@buildingsmart.org

3. Go to the Management portal of bSDD

Go to the Management portal: https://manage.bsdd.buildingsmart.org/.

Alternatively, use one of the third-party tools to manage and upload data dictionaries in bSDD, which integrates with the bSDD API.

Note: if the Management Portal shows an error at startup or you keep seeing the spinner icon, try pressing Ctrl-F5 to refresh the cookies. If that doesn't work, then try an "incognito" or "InPrivate" window of your browser and then navigate to the Management portal. If that still doesn't work, then contact us: bsdd_support@buildingsmart.org.

4. Log in

If you do not have a bSDD buildingSMART account yet, choose "Sign up now", otherwise choose "Sign in".

5. Upload file

Go to the "Dictionaries" tab and select your organisation from the list.

Using the "Select file" button load your dictionary JSON file.

bSDD manage

6. Press "Upload selected file"

Before each import, we recommend first using the option 'Validate only?' This will inform you of any errors or warnings without trying to import the file.

Important Uploading a new file replaces the existing dictionary with the same version.

Once ready, and if the platform returns no errors, click "Upload selected file."

Once the file has been imported, you will receive a more detailed import report by email. It might take up to 15 minutes. In case the import routine spots any errors, you will see them listed in the email.

Note: all of the steps explained above can also be automated using the bSDD API integration.

The lifecycle of the bSDD dictionary version

When you publish a new dictionary version in bSDD, it initially always has the Preview status. At this stage, you can reupload the content to modify it, activate that version, or permanently delete it. The status can be changed through the Management Portal or via the API.

Lifecycle workflow

⚠️ Once the content is activated, it will get an immutable URI, meaning the URL and content will stay in bSDD forever and can't be deleted. Changing the status to "Inactive" is possible, but the page will still show the content to support use in contractual agreements. Consider that before activating the version of a dictionary.

General guidelines

  • Fill in all the required attributes.
  • You cannot upload the content in parts. All classes and properties of one dictionary must be in one file.
  • Manage and publish translations in a separate file.
  • Make specific dictionaries; don't try to put too much data into one dictionary.
  • Link to IFC entities for increased usability.
  • Add existing properties to your content instead of replicating them.

Naming conventions and guidelines

The dictionary name needs to be unique. Avoid the use of a name that is too generic. Avoid names that conflict with other dictionaries. For example, do not create classes with an 'Ifc' prefix. Avoid replicating content from other dictionaries. Some licenses do not allow redistribution or modifications. It's a good practice to reuse content by linking it to your dictionary. For example, you can add properties from other dictionaries to your class.

Dictionary code

The dictionary code needs to be unique in the bSDD; choose one that is recognizable with the dictionary name. The dictionary code is used to generate the URIs of all the resources, so it should be short and preferably without spaces.

Property set names

Avoid using the 'Pset_' prefix. This is restricted to IFC only. Do not replicate the property or class name.