I have a working API query that gets me the name o...
# troubleshoot
e
I have a working API query that gets me the name of the container and number of entities in it. But I also want to get the description of a container (aka Documentation). How do i get it? I've tried putting
description
under
name
in the query, but it returns
null
, even though documentation is not empty for this container. Is it called something different? the property like 'documentation' is not found
Copy code
{container(urn:"urn:li:container:XXX") {
  properties
  {name
  description
  } 
  entities{
    total
    start
  }
}}
📖 1
🔍 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
a
Hi, you might want to ask for institutional memory! https://datahubproject.io/docs/graphql/objects#institutionalmemory
e
@astonishing-answer-96712 like this? but it also gives me null
Copy code
{container(urn:"urn:li:container:XXX") {
  properties
  {name
  } 
  institutionalMemory{
    elements{
      url
      label
  }
  }
  entities{
    total
    start
  }
}}
a
And you’re positive that the entity in question has a description?
e
@astonishing-answer-96712 yes it has, and later on I found it within
editableProperties
, not
Propeties
or
institutionalMemory
This is a great illustration for issue with documentation: different parts of metadata ara placed into so many different objects, and it is very difficult to find what you need. Also cc @big-carpet-38439 since we've discussed this with as well. And is it intentaional to have that many kinds of objects to keep different parts of metadata in? Would't it be easier and more user-friendly to have them in same place? What is general difference between what is kept under
institutionalMemory
and other properties, like
editableProperties
?
And apart from
institutionalMemory
and
Properties
and
editableProperties
, as far as I see datasets also have different objects for
Platform
,
status
,
ownership
,
subTypes
,
customProperties
(the last one somehow also includes
schema
database
instance
and
platform
)... Is this russian-doll-like structure with many repetetive items necessary?
a
I agree with you on the confusing nature of the docs here, it’s something we’re working hard to improve at the moment
e
@astonishing-answer-96712 but while we here, could you please briefly explain what is InstitutionalMemory and how is it different from the properites? I dont' get the basic idea behind it, and the name does not give me any clues
a
I believe it’s supposed to store terms and other info related to the glossary, but it may no longer be used