> For the complete documentation index, see [llms.txt](https://lern.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lern.sunbird.org/use/developer-guide/user-and-org-service/reports/other-jobs/state-admin-geo-report.md).
# Delete Users Assets Report
### The "Deleted Users Assets Report" provides an overview of assets (content and course assets) created by users who have been deleted from the system. The report involves the following steps:
1. **Fetch Deleted Users:** Retrieve a list of users who have been marked as deleted from the database.
2. **Extract User IDs:** Extract the unique identifiers for these deleted users.
3. **Fetch Content Assets:** Query an external API to fetch assets (such as documents, media, etc.) created by these deleted users.
4. **Fetch Course Assets:** Query an external API to fetch course-related assets (like course batches) associated with these deleted users.
5. **Fetch ML Assets from API or MongoDB**: The job queries an external API (ML\_ASSET\_SEARCH\_URL) to fetch ML assets (solutions and programs) created by the deleted users. Alternatively, if the API call fails, the job directly queries MongoDB to retrieve the required ML asset data. This involves connecting to the MongoDB instance and executing aggregate queries to filter and retrieve the relevant ML assets based on user IDs.
6. **Process DataFrames:** Integrate the dataframes for deleted users and their assets, and perform necessary processing, such as filtering and deduplication.
7. **Save Report to Blob Storage:** Save the final processed report to a cloud-based blob storage, typically in CSV format.
This report is useful for auditing, tracking, and removing assets that are no longer needed, ensuring system cleanliness and compliance with data retention policies.
\
**Data provider:**
* Cassandra - User table
* Course Batch API
* Content Search API
**Delete Asset report CSV content:**
| Column Label | Column Type | Data Type | Description |
| --------------- | ----------- | --------- | ------------------------------------------------------------------------------------------- |
| userId | Static | String | User Id of the deleted User |
| username | Static | String | Decrypted user name of the deleted user |
| roles | Static | String | Roles of the deleted user |
| assetIdentifier | Static | String | Identifier of the asset / course batch / ML program / solution |
| assetName | Static | String | Name of the asset / course batch / ML program / solution |
| assetStatus | Static | String | Status of the asset / course batch / ML program / solution i.e live/draft |
| objectType | Static | String | Object type of the asset/course batch / ML program / solution i.e QuestionSet/content/batch |
\
**Sample data:**
```
userId username roles assetIdentifier assetName assetStatus objectType
cc3220fe-ace3-4716-a3a4-4ed799740947 TestUser1 ORG_ADMIN do_11395143971887513612 Test SRK QuestionSet Live QuestionSet
ed8f22b1-1c33-4ca5-b8fd-572844ef3a7a Demouser CONTENT_CREATOR do_11395139703507353614 QuestionSet-FT-2014 Draft QuestionSet
ed8f22b1-1c33-4ca5-b8fd-572844ef3a7a DeleteuserTest BOOK_CREATOR do_11395217540852940811 sameple course Live Content
```
---
# 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://lern.sunbird.org/use/developer-guide/user-and-org-service/reports/other-jobs/state-admin-geo-report.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.