missing Tags

[swschilke]

Hi, I would like to have a tag für nlu, Graphrag (didn't check ;-)), Podcast etc.
ThanX

[idoshamun]

Hi @swschilke,

I'm not aware of nlu and graphrag. Can you elaborate please?

[swschilke]

NLU is natural language understanding, a step further from natural language processing (nlp) GraphRAG is also a step further from RAG, just with a knowledge graph for representing the (private) information Hope this explains it Podcast, would be for podcasts or podcast episodes which are published in the genre or domain

…

On Sun, 4 Aug 2024, 10:04 Ido Shamun, ***@***.***> wrote: Hi @swschilke <https://github.com/swschilke>, I'm not aware of nlu and graphrag. Can you elaborate please? — Reply to this email directly, view it on GitHub <#1313 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADE66ATNH5EDXTLVH5X4Y2DZPXN7VAVCNFSM6AAAAABLZ333POVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMRTGQYDCNY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[idoshamun]

We currently have NLP and RAG, not the specific ones you mentioned. Once we have enough posts about NLU and GraphRAG you can expect to have them as tags :)

[swschilke]

Maybe the poeple tag it NLP or RAG as there is no Tags for NLU or GraphRag - if they are there the posts will come ;-)

…

On Sun, Aug 11, 2024 at 9:39 AM Ido Shamun ***@***.***> wrote: We currently have NLP and RAG, not the specific ones you mentioned. Once we have enough posts about NLU and GraphRAG you can expect to have them as tags :) — Reply to this email directly, view it on GitHub <#1313 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADE66AQ6CDTZXQCXUHA5HN3ZQ4ILFAVCNFSM6AAAAABLZ333POVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZQGMYDIMI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nimrodkra]

Our system automatically identifies and selects the tags. It doesn't rely on human input. The auto-tagging system looks into the content itself and what keywords are in it, and based on that, it determines if there's "enough content" for a certain tag. If more people wrote content (or published videos) about NLU and GraphRAG out there on the internet, the likelihood for these tags to be added to daily.dev would increase. In other words, the bottleneck is not the tagging system, it's the shortage of such content online.

If you know any publications that specialize in this niche, feel free to suggest them here, and we will look into it (just make sure it complies with the content guidelines first)

[swschilke]

So some links like this: https://arxiv.org/abs/2404.16130 https://github.com/microsoft/graphrag https://www.microsoft.com/en-us/research/project/graphrag/ https://youtu.be/jCjyaQL-7mA https://www.ontotext.com/knowledgehub/fundamentals/what-is-graph-rag/ https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/ https://neo4j.com/blog/graphrag-manifesto/ https://docs.llamaindex.ai/en/stable/examples/query_engine/knowledge_graph_rag_query_engine/ https://neo4j.com/developer-blog/graphrag-ecosystem-tools/ https://jeongiitae.medium.com/from-rag-to-graphrag-what-is-the-graphrag-and-why-i-use-it-f75a7852c10c https://bhavikjikadara.medium.com/graphrag-advanced-data-retrieval-for-enhanced-insights-bcef777404d2

…

On Mon, Aug 12, 2024 at 9:17 AM Nimrod Kramer ***@***.***> wrote: Our system automatically identifies and selects the tags. It doesn't rely on human input. The auto-tagging system looks into the content itself and what keywords are in it, and based on that, it determines if there's "enough content" for a certain tag. If more people wrote content (or published videos) about NLU and GraphRAG out there on the internet, the likelihood for these tags to be added to daily.dev would increase. In other words, the bottleneck is not the tagging system, it's the shortage of such content online. If you know any publications that specialize in this niche, feel free to suggest them here, and we will look into it (just make sure it complies with the content guidelines <https://docs.daily.dev/docs/for-content-creators/content-guidelines> first) — Reply to this email directly, view it on GitHub <#1313 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADE66AXLPWH6CNOFDRMAWKTZRBOQLAVCNFSM6AAAAABLZ333POVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZRGA3DQMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>