> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/v1/how-to-guides/workflow/how-to-remove-the-abstract-registration-deadline.md).
# How to remove the Abstract Registration Deadline
When filling out the venue request form, some PCs include an Abstract Registration Deadline in their request. After the venue is deployed, they want to remove this deadline due to a change in their workflow. Unfortunately, removing this deadline is not as simple as deleting the date from the form.
To remove the deadline:
1. [Instantiate an API 1 client](/v1/getting-started/using-the-api/installing-and-instantiating-the-python-client.md).
2. Get the id of your request form, this is located in the URL.
URL of the request form containing the request form id.
3. Run the code below.
```python
request_form_id = ''
references = client.get_all_references(referent=request_form_id)
for ref in references:
if 'abstract_registration_deadline' in ref.content:
print("deadline removed from: ",ref.id)
del ref.content['abstract_registration_deadline']
client.post_note(ref)
```
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openreview.net/v1/how-to-guides/workflow/how-to-remove-the-abstract-registration-deadline.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 `build a script that syncs our docs to a CMS` 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.
