> For the complete documentation index, see [llms.txt](https://jrpdocs.hyvikk.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jrpdocs.hyvikk.space/features/articles/edit-article.md).
# Edit Article
### Article Details
Update the Necessary Fields & Click on **"Update"** \[Top Right Section].
{% hint style="info" %}
**"Paper Id"** is an Auto Generated Field and cannot be Edited.
{% endhint %}
#### **Information About Fields :**
* **Title :** Article Title
* **Paper Id :** Autogenerated Article Id to Uniquely Identify the Article
* **Area of Research** : Article Subject for which the Article has been Written
* **Abstract** : A brief summary of a research article, thesis, conference proceeding, or any in-depth analysis of a particular subject and is often used to help the reader quickly ascertain the paper's purpose.
* Author Name : Name of Main Author
* Author Institute : Institute Name
* Author Email Id : Email of Main Author
* Co-Author(s) Details
* Name : Name of Co-Author
* Institute : Institute Name
* Email Id : Email of Author
* Contact Number : Primary Phone/Mobile Number
* Country : Country from which Main Author Resides
* Upload Article : RAW Research Article Submitted by Author.
* Permissible File Types : .doc , .docx
* Max File Size : As Configured in [**"Wizard Settings"**](/features/wizard-settings.md#publication-configuration)
* **Status :** Article Status
* Under Review
* Accepted
* Published
* Rejected
* Payment Status : Status of Payment made by Author after "Article" has been Accepted by Admin.
* Pending
* Paid
* Not Paid
* Select Volume : Volume Number in which the Article will be Published and Listed on Website (Current Issue, Past Issue Pages)
* Select Issue : Issue Number in which the Article will be Published and Listed on Website
* Page No(Start - End) : Start - End Page Numbers of an Article.
* DOI : DOI Number of an Article. To get DOI Number for any Article Visit :
* Date of Article Published : Article Publish Date added by Admin
* Month : Month in which Article has been Published
* Published Article : Final Verified & Formatted Article.
* Permissible File Types : .pdf
* Max File Size : As Configured in [**"Wizard Settings"**](/features/wizard-settings.md#publication-configuration)
## Review Details
Article(s) submitted by Author(s) has to be Reviewed by either Reviewer or Admin.
**Admin can do Following things in Article Review Section.**
* [**DELETE REVIEW**](/features/articles/edit-article.md#delete-review)
* [**SUBMIT REVIEW**](/features/articles/edit-article.md#submit-review)
####
#### **DELETE REVIEW**
**To Remove Invalid OR Inappropriate Review.**
* Click on **"Delete"** Button
{% hint style="info" %}
By Clicking on "Delete", any Review that was previously added in Article will be **Permanently Removed.**
{% endhint %}
#### **SUBMIT REVIEW**
**To Submit Admin Review**
* Fill Up All the Required Fields
* Navigate to Bottom of Section and Click on **"Submit"** Button to Save.
---
# 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://jrpdocs.hyvikk.space/features/articles/edit-article.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.