> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/content-check-modes/table-columns.md). # Table Columns #### Download Cart ``` A cart for sending downloads to a queue ``` #### Username ``` model username ``` #### Downloaded ``` Boolean for whether the media is marked by the db as downloaded ``` #### Unlocked ``` Boolean for whether the post tied to the media is unlocked A null value from the site shows as locked ``` #### Length ``` This is the length of videos/audio N/A is used for media like pictures without a length Formated in HH:MM:SS ``` #### download\_type ``` normal, protected (DRM) or unknown ``` #### other\_posts\_with\_media ``` Identifies posts with the same media id ``` #### Mediatype ``` Type of media ``` #### Post date ``` Date the post was created/updated ``` #### Post Media Count ``` Number of media in the post this media item is in ``` #### Responsetype ``` Which API the media was retrieved from ``` #### Price ``` Price of the post the media is tied to ``` #### Post ID ``` ID for the post the media is tied ``` #### Media ID ``` ID for the media ``` #### Text ``` Text from the post ``` --- # 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://cloakedkeys.gitbook.io/ofsc/content-check-modes/table-columns.md?ask=&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.