> For the complete documentation index, see [llms.txt](https://ifhp-2.gitbook.io/ifhp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ifhp-2.gitbook.io/ifhp/community-data/implementation-details-and-faqs.md). # Implementation Details and FAQs ## Is there any underlying schema for the community data? Yes, for each data that is uploaded, it is assumed that there is a simple schema for that, although it is static for now, in the future, it has to go through the ontologies. ## Can the community datasets be uploaded by any user? No, currently only the IIIT D faculty can upload the datasets by going to the URL , this is currently not based on role-based access, which could be worked on in the future. ## In which database and collection is these consents are stored and managed? The community datasets are stored in **the current user** database and **UploadFiles** collection. ## --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ifhp-2.gitbook.io/ifhp/community-data/implementation-details-and-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.