Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip

COURSE DESCRIPTION

This course describes how to start using batch card printing features in NCDB.
To use batch card printing, it is necessary to have card printer (it means not label printer!).
Please note that all pictures in this tutorial are for illustration purpose only.

You’ll be able to print your cards directly from your web browser.
Besides, you’ll learn how to set up your Card Designs using placeholders, custom fields, barcodes etc.

Before you start, it is advisable to have a look at “How to process NCDB Orders” and “How to work with Online Ordering application

...

Rotation – text rotation. Please make sure your design meets ISO standards before you overuse rotation.

Note

Important note: when the defined width of the placeholder is too short, the text that goes outside its borders will be cropped. Take this into account when defining your placeholders! In case you want to delete the placeholder, just mark it with your mouse and click “Remove Placeholder” button.

Custom fields

Custom fields are special type for optional data that can be defined differently to fit needs of every card issuer. Through custom fields, basically any value or more values can be attached to a specific card holder or card. This can be for example name of study course, student ID, blood group, card serie etc. Custom fields should reflect the “real world” – information that are tied to a person should be bound to cardholders, whereas information tied to card should be defined as card bound. Values for custom fields can be added using the API for external issuers (most recommended way for External Issuers), or manually in edit mode of cardholders/cards.

How to define new custom fields? Custom fields can be defined in NCDB -> Cards Issuers -> Custom Fields

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#E6FCFF

Uniqueness of ‘Personal ID’ and usage of custom fields

As behaviour of the ‚Personal ID‘ parameter which is a part of cardholder data. This parameter needs to be unique on a card issuer level. That means there cannot be two cardholders with identical personal IDs under one card issuer. If a card issuer tries to insert a duplicate value in this field, he will receive an error.

If, for some reason, you need to receive duplicate values from your card issuer, you can create your own custom field in NCDB → Card Issuers → Custom Fields. Each custom field needs to be assigned to one or more card issuers.

When creating a new custom field, several things need to be defined:

...

Below is the picture how to assign your custom field to a text placeholder when creating new card design. All accessible custom fields are displayed and you can just click them to add. You can also put more custom fields into one placeholder, even in combination with standard text. We are aware that Custom fields problamatic is complex and the short text above doesn’t cover it completely. In case you have some specific questions about custom fields and how to use them, feel free to ask us using our Service Desk (support@gtsalivesupport@aliveplatform.com)

...

IMAGE For “Image” placeholder, from the drop-down menu, three different types can be chosen:

...

Using the information from this excel file, you can print labels for your cards. This process includes connecting the excel file with a text editor like MS Word and creating the design of your labels there. The process of connecting MS Excel to MS Word will not be described in this tutorial, help can be found on the web. When the labels are printed, you have to tell NCDB that the print was succesfully done. This can be done through importing the modified excel “Unprocessed Entries Export” that you downloaded in previous step. Into this excel file, to the “Process result” column, write “OK” (see the picture). This way, the system will know that labels for these cards were already printed. After saving this file, import it back to NCDB (still logged in as Personalization Center user) using the “Import processed” button. At this moment, the cards that you marked with “OK” should disappear from Batch Card Printing completely and they should appear in NCDB among other issued cards.

Warning

Note: custom fields cannot be printed through label printing, but only through standard Batch Card Printing described in previous section.

🖨️ The Personalization Center

The Personalization Center is a restricted interface for an external company that prints ID cards in your country. Under the given personalization centre, you will create a user who has access to orders intended for printing but does not have the right to edit information. The PC user confirms that the card has been printed, and the order status automatically changes to the final status.

The Personalization Center is set at the NCDB - Settings - Personalization Centers

...

Use the plus button to add a new personalization centre or use the pencil button to edit the existing one.

Image Added

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#E6FCFF

The Personalization Center must always have the "Active" box checked
Default Personalization center means that it will be your default personalization center and all publishers will fall under it unless you set them differently in their details

Users of the Personalization Center

Each personalization centre must have its own users (usually the company that prints your IDs or you if you print them yourself)

You add users using the head icon in the overview of personalization centres. Fill in the required information. The user must have the checked boxes active and access to orders.In the user Roles section, always select the Personalization Center role The user then logs in to the NCDB Alive Platform via the classic login page. The user of the personalization centre only sees an overview of orders and print orders, which he can mark as printed. It does not have access to other data in the NCDB and cannot make changes to the data.

...

A view of the NCDB from the personalization centre user's side

...