Modifying the language file to show things at the top of an asset
Hi all,
On our data issues we have a number of attributes that appear by default (if they exist) on the top of the asset page. In this case, we have the date the issue was created, and some responsibilities.
I’ve found what looks to be the right section in the language file:
##
## Page definition '/page-definitions/dsm/dataissue/dataissue'.
##
#Tue Dec 12 10:55:30 GMT 2017
pagedefinition.dataissue.createdon=Created on
pagedefinition.dataissue.view.resolutions.name=Resolutions
pagedefinition.dataissue.view.violations.name=Violations
pagedefinition.dataissue.view.violations.description=The list of governance assets that are violated by this issue.
pagedefinition.dataissue.assignees=Assignees
pagedefinition.dataissue.view.resolutions.description=The list of governance assets that resolve this issue.
pagedefinition.dataissue.requester=Requester
pagedefinition.dataissue.reviewers=Reviewers
And this is what I see on the asset page:
So I assume because I can see the created on date and things like the Requester and Reviewer roles in this file, they’re the responsibilities that show up at the top.
Onto my problem: I want to add another role to this list. The role is “Issue Manager”. To do this, I added the line:
pagedefinition.dataissue.issuemanager=Issue Manager
But it doesn’t seem to have worked. I created a backup, downloaded it, updated the language file (en.i18n, which I believe is our default language, not en_GB.i18n), reuploaded and restored from it. I’ve heard that it can take quite a while to update, but I did this several days ago now, so I think I’m definitely doing something wrong.
Is there any documentation on how to modify this file? Could someone point me in the right direction? I’m not really sure why the date is listed in the language file either, is this something I have to update?
Thanks!
Ann Wuyts
·4 years ago · EditedHi Arthur, thank you for the update! And yes, this documentation was based on the ‘Old Navigation’ (if I can call it that).
I’ve informed the PM looking into custom asset pages of this thread, and if I’m not mistaken the ‘last modified by’ is mentioned/voted upon extensively on Ideation as well. So we’ll take this into account when improving asset pages.
arthurburkhardt
·4 years ago · EditedThanks @ann.wuyts
In this case, I think the documentation you linked to is outdated, because the syntax has changed in the meantime.
Old notation
New notation
The main issue is that it then becomes the default on ALL assets, which is rarely useful.
I’m very much looking forward the better UI configuration capabilities: choose which role appear on the banner/asset page, higher information density with multiple columns, etc.
For example, I was presenting Collibra to a business intelligence analyst, and he asked me this simple question: when was the asset created/modified and by whom?
This very basic and ubiquitous information is nowhere to be found on the asset. Even worse, some information such as the “last modified by” is not available AT ALL through the Collibra UI. The only option is to go to the API.
I lost the confidence of quite a few internal users because of this lack of basic capabilities.
Ann Wuyts
·4 years ago · EditedAs custom page definitions are not supported -nor advised, to be honest- this is not documented. For smaller snippets - the page definition overrides - there is an input field in Console under ‘UI Configuration’. My coding knowledge is too limited to give you a helpful example for adding and styling an additional role on the Issues Page. It is possibly worth to look at https://productresources.collibra.com/kb_article/changing-the-avatar-settings-in-the-title-bar-v5/ . While the code will not be the same, it might be you can apply this to the issues page.
We have an Idea titled ’ Provide an option to hide reviewers displaying in issue asset page’ on the Ideation portal. Could you add your vote and voice/use case there as well? It would then not only be ‘hide’, but also change or display additional roles.
Ann Wuyts
·4 years ago · EditedHi Daniel,
Using the language file you can only translate / adjust existing page elements, you can not add them. What you could do, for example is use the role type ‘Assignees’ and rename that to ‘Issue Manager’:
pagedefinition.dataissue.assignees=Issue ManagerTo add an additional role, you would need to write your own custom page definition, or use a page definition override.
arthurburkhardt
·4 years ago · EditedIs it possible to write our own page definitions, @ann.wuyts?
That would be awesome! Is there any documentation available?
danielcousins
OP4 years ago · EditedCould you point me in the direction of some documentation on this process? Or perhaps provide some guidance if there isn’t any documentation available?
Many thanks for your other suggestion. Not sure how manageable it is though, think things could get messy and confusing for users. Will need to test out and see how it looks.