> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/release-6.0.0/learn/functional-capabilities/asset-sourcing.md).

# Asset Sourcing

For a meaningful discovery of assets, assets can be crowdsourced, tagged to relevant frameworks, and contributed using an asset sourcing web app.

Some of the features that ED leverages from Asset sourcing are, allowing users to

1. Create asset taxonomy for content
2. Identify framework categories
3. Associate assets with multiple types such as audience type, topic, etc.
4. Create framework - Organization and target framework
5. Meaningfully review, publish the asset
6. Create customised collections such as Textbook, Courses, etc.
7. Associate assets with collections
8. Create and publish a sourcing project with a defined scope of assets to be sourced and a schedule
9. Review the nominations to a sourcing project from contributors
10. Review the asset contributions to a sourcing project from the approved set of contributors
11. Curate and publish the assets for consumption
12. Enroll as a contributor
13. Nominate to one or more sourcing projects
14. Contribute assets to the approved sourcing projects
15. Get the consumption details of the assets that got published for consumption
16. Check various reports such as Collection level gap report, Folder level gap report, Visitor's report, etc.

The above capabilities of Asset Sourcing are derived from components of Sunbird CoKreat. You can find details by clicking on the link [here](/release-6.0.0/learn/functional-capabilities/product-and-developers-guide/asset-sourcing.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ed.sunbird.org/release-6.0.0/learn/functional-capabilities/asset-sourcing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.