1import{A as s}from"./AppBreadcrumb-CbKlyoor.js";import{d as l,a as u,o as p,i as d,e as t,b as n,h as r,g as e,J as a,F as m,_ as g}from"./index-C1QTFfJN.js";import{P as c}from"./ThePageTitle-By5CSeF2.js";const h=l({__name:"PageDocumentation",setup(f){return(w,o)=>{const i=u("AppLink");return p(),d(m,null,[t(s),t(c,{id:"kg-about",title:"Documentation"}),t(a,{width:"big"},{default:n(()=>[o[8]||(o[8]=r("p",null," The Monarch Initiative Documentation provides comprehensive resources on the Monarch Knowledge Graph, including data sources, the KG build pipeline, query tools, and application usage. ",-1)),r("ul",null,[r("li",null,[t(i,{to:"https://monarch-app.monarchinitiative.org/","no-icon":!0},{default:n(()=>[...o[0]||(o[0]=[e(" Monarch KG Documentation ",-1)])]),_:1}),o[1]||(o[1]=e(" : The central documentation site covering KG data sources, the build process, monarch-py, the API, Neo4j access, and more. ",-1))]),r("li",null,[t(i,{to:"https://monarch-app.monarchinitiative.org/Sources/","no-icon":!0},{default:n(()=>[...o[2]||(o[2]=[e(" KG Data Sources ",-1)])]),_:1}),o[3]||(o[3]=e(" : Detailed documentation of each data source ingested into the Monarch Knowledge Graph. ",-1))]),r("li",null,[t(i,{to:"https://monarch-app.monarchinitiative.org/KG-Build-Process/kg-build-process/","no-icon":!0},{default:n(()=>[...o[4]||(o[4]=[e(" KG Build Process ",-1)])]),_:1}),o[5]||(o[5]=e(" : How the knowledge graph is assembled from download through transform, merge, and load. ",-1))]),r("li",null,[t(i,{to:"https://neo4j.monarchinitiative.org/browser/","no-icon":!0},{default:n(()=>[...o[6]||(o[6]=[e(" Neo4j Browser ",-1)])]),_:1}),o[7]||(o[7]=e(" : Query the Monarch KG directly using Cypher via the Neo4j browser interface. ",-1))])])]),_:1}),t(a,{width:"big"},{default:n(()=>[r("p",null,[o[10]||(o[10]=e(" For further assistance, check out our ",-1)),t(i,{to:"/kg/help"},{default:n(()=>[...o[9]||(o[9]=[e("How to & Help",-1)])]),_:1})])]),_:1})],64)}}}),G=g(h,[["__scopeId","data-v-04d0012f"]]);export{G as default};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.