I have a need to create "custom" browse paths for entities (datasets, but also datajobs, and other entities I will create myself). I notice that dataset browse paths "behave well" - ie you can see them on the landing page (or almost), etc etc. datajob browse paths, unfortutately, I can only see once I get on the datajob via the standard path (clicking on Tasks etc). Am I doing something wrong? Also, is there any way to make browse paths "first-class citizens" so they appear at the landing page (or almost?). The reason is that my users may have their own "lingo" about things, and I want to enable them to navigate the datahub world using that "lingo" (so I would create paths like '/Experiments/data/absorptions/nickel...') - and would like to give users an "easy" way to get at the start of the navigation-as-per-their-worldview page

Hi @late-zoo-31017 here’s a datajob on demo https://demo.datahubproject.io/tasks/urn:li:dataJob:(urn:li:dataFlow:(airflow,dag_abc,PROD),task_123)/Documentation?is_lineage_mode=false

Sorry crazy day yesterday so I did not respond. Yes I see the datajob above. What I meant was different: Let's say my users are biologists/pharma people, non-technical, that are researching COVID. For them "Tasks/Pipelines/etc..." does not mean much. They would ideally want to see, at the main page (or easy access from there) something like /COVID/Vaccines/<vaccine name>/simulation/<simulation name> -> (at this point pointing to the datajob + input/output files in lineage - this part is fine). Basically something adapted to their way of thinking (their view of the world. Not datahub's, or mine)

@late-zoo-31017 let me think about this a bit and get back to you