Versioning and workflow
When you enable workflow Talend Data Catalog creates another version of the glossary named Published. The Published version is the one whose contents are to be presented to most of the users. Its contents are not directly editable (with or without permission). Instead, one edits the contents of Development version and then uses the Publish workflow step to change what is in the Published glossary.
The glossary version you are given access to when using the Browse/Explore/Search/Worksheets/Collections/etc. features is always determined by what your workflow permissions are. In particular, you will have access to:
- The contents of the Published version the glossary if you do not have any Workflowcapability object role assignments, and you will not have any ability to edit the glossary or see current edits and workflow states. You will only see what was published.
- The contents of the Development version of the glossary if you do not have any Workflowcapability object role assignments, and you will have the ability to see glossary object in their current workflow status
In this way, general users are given access to the contents of the Published glossary, and users who are editing the workflow enabled glossary will also be given access to the contents of the Development glossary.
In fact, you will also see a similar behavior in the Repository Manager.
When you expand the glossary to show its versions, you will see both the Published and Development versions, no matter what Workflowcapability object role assignments you may have.
In addition, if you open any configuration version containing the glossary, the UI will show that that configuration version contains the:
Published version of the glossary if you do not have any Workflowcapability object role assignments,.
Development version of the glossary if you do not have any Workflowcapability object role assignments, and you will have the ability to see glossary object in their current workflow status
You will always see this version as the member of any configuration version and trying to assign another version will not be possible. It is entirely system managed and presented to the user this way. It can be a bit confusing to casual users, but generally casual users do not have access to the Repository Manager.
In terms of implementation, it is the Published version of the glossary that is associated with any configuration version, even though you may see a different version in the UI.
Finally, you may associate an archived (historical) version of a glossary with a configuration, thereby making it the Published version for the purposes of presentation.