Restricted Classification Editor Instance Lists

When editors select an association slot for editing this causes the TMCore EPiServer Module to request the first page of topic to be associated with the current page. The items in the instance list are sorted alphabetically. In some solutions this may cause undue load to be placed on the database server as it sorts lists of potentially tens of thousands of topics. Typically, this type of role would be hidden, but in some cases it may be required to allow the editor to classify using this role, but not to display the list of instances by default.

In this case adding an NPCL extension to the source role of type http://psi.networkedplanet.com/extensions/episervermodule/disallowUnrestrictedSearch with the value true will prevent users from listing all topics of valid types.

For example: if documents and themes are connected by

When classifying a Theme if you wish to force editors to specify a search string in the "select instance" tab to find documents then you should add an NPCL extension of type http://psi.networkedplanet.com/extensions/episervermodule/disallowUnrestrictedSearch with the value true (the value is not case sensitive) to the source role type: http://psi.networkedplanet.com/assocs/DocumentHasThemeTarget.

An NPCL extension is modelled by creating a topic that is an occurrence type that is an instance of a topic with the subject identifier http://www.networkedplanet.com/psi/npcl/meta-types/npcl-extension-type. Consult the TMCore07 documentation for more information about NPCL extensions.