Certification campaigns

A certification campaign is used to generate mass blockchain certificates. From a specified template, data is imported, encrypted and then written on the blockchain in a few clicks. The publication time usually takes a few minutes, but can take up to several hours if the blockchain is overloaded or when publishing thousands of certificates.

Tips

Only users with an administration or publication profile can launch a "New Certification Campaign".

New certification campaign

From a certificate template, click on "New campaign", then select the import file containing all the data to be certified. You need to fill this file by respecting the structure of the import file specific to the certificate template. You can add data to the imported file using the "Add Data" feature, which can be very useful in the case of a multilingual import or if you have several data files.

Warning

  • only Excel (.xslx) format is supported for import
  • only the first tab of the Excel file is supported
  • please also make sure that the file is not password protected
  • the addition of data integrates a duplicate management function: the same data added several times will not be imported more than once

Import file

The data in your import files are under your full responsibility. BCdiploma has no control over the content, except for:

  • verifying that all the columns required by the certificate template are present
  • the validity of the ISO language codes

Warning

Warning: injecting HTML into certified data is prohibited for security reasons. Requests containing HTML will be automatically rejected by the BCdiploma firewall.

Tips

In a campaign, lines in your import file with identical technical data will produce only one and the same certificate. Make sure you have different technical data (e.g. ID, email) to avoid these groupings and to produce one certificate per line.

email field

The email field is the technical field that will be used as the recipient of the email containing the certificate during an emailing campaign.

Warning

The email field must contain only one valid email address per certificate. Note that accents and quotes are not supported in the email address suffix (e.g. maé.doe@mydomain.com is not supported, but mae.doe@mydômain.com is supported)

Tips

For micro-credentials, the email field is also used as data to verify the identity of the recipient when exporting to Open Badges format. For this purpose, the email address is "hashed" and registered on the blockchain. As a result, the email addresses of micro-credentials are not modifiable.

Multilingual

If your certificate template is multilingual, you must specify the language of the certificate data for each line in your import file. The language of the line is identified by an ISO code in the "language" column of the file. For example, for a trilingual English/French/Arabic certificate, you will have 3 lines in your import file: one line per language with the ISO code of each language (en/fr/ar) specified in the "language" column.

Warning

In case your certificate template is multilingual, you must respect the following requirements of your import file:

  • 1 line per language per certificate
  • the language must be indicated in the "language" field
  • the same ID and technical information for each certificate
  • the ISO code of each line must correspond to a language supported by the template

Campaign associating files to certify

If your template allows it, you will have the possibility to associate one or more files (photos, pdf, etc.) to each certificate during a publication. Note that this process uses the same level of encryption as the certificate data.

The process of publishing data associating files to be certified is the same as for a classic campaign, completed in the following way:

In your certificate template, identify the field(s) stamped "Document" (e.g., "Supporting Photo", "Document1", etc.). In the data file to be certified, indicate, for each certificate, a file name in the relevant fields. For example "MyPhotoaCertifier-123456.pdf" or "MyDocumentaCertifier2.pdf".

When publishing, attach a compressed archive (.zip) - via the "Import file" button - containing all the files to be associated with the generated certificates, respecting the file names you indicated in the relevant fields in the previous step.