Content name must be unique.
GN4 requires, by default, that content names are unique on the folder level. Thus, you can create only one content item with the name 'peace' in the current folder, but you can have more 'peace' content items as long they reside in different folders.
In case you attempt to create a duplicated article, an error message is displayed.
An alternative is to force the content name uniqueness on the system level. To do this, change the XML schema.
Names, unique on the folder level The behavior is similar as in file system, and therefore, many users are familiar with the concept. Moreover, it's very handy for the multi-publication systems: you can use the same content name, e.g. 'today briefs' in all publications. A downside may appear when you send content in another folder: the send operation is aborted if in the destination folder already exists a content item with the same name. In that case, you need to rename your content item. The way to know if the new name might be already used is to search for the designated name. Still, if there are folders where you cannot access, such folders won't be included in the search. Names, unique on the system level This approach prevents the multi-publication systems to use the same content name, e.g. 'today briefs' in all publications: if the name is already used in one publication, other publications will need to select some different name when creating content. An advantage is that there will be no problems when sending content. |