# 6.5.2.2. Reviewing a change request

When a change request is submitted the changes are pending until they are evaluated by the Registry Administrator or the Registry Maintainer having the curation mandate over the given Geo-Object Type.

## Viewing a change request

Change requests can be searched through and viewed by users with System Administrator, Registry Administrator or Registry Maintainer roles for a given Geo-Object Type as follows:

1. Navigate to the *Change Requests* module.\\

   <figure><img src="/files/MFwQi1m1PanqOEtPY7LM" alt=""><figcaption></figcaption></figure>
2. The *Change Requests* module’s home page opens, listing all the change requests that have been submitted by users with a Registry Contributor role. Each change request is summarized by an expandable row containing information on the:
   1. *Contributor:* user who submitted the change request
   2. *Geo-Object Type:* the Geo-Object Type for which the change request was submitted
   3. *Geo-Object:* the specific Geo-Object for which the change request was submitted
   4. *Date Contributed:* the date the change request was submitted by the contributor
   5. *Status:* status of the change request; this can be one of the following:
      * *Pending:* a Registry Maintainer has either not reviewed the change request, or reviewed it but not implemented the decisions
      * *Accepted:* a Registry Maintainer has accepted all changes and implemented the decision
      * *Partial:* a Registry Maintainer has accepted only some changes and rejected others, and implemented the decision
      * *Rejected:* a Registry Maintainer has rejected all changes, and implemented the decision
   6. *Request ID:* unique identifier of the change request\\

      <figure><img src="https://lh4.googleusercontent.com/rkn4JmTflkah5yXmNtHBck8LMAQYDYq63Edh5pCHFREvoofQjgJV9PgVWBjkuTh5Ea5F_FZbqDsLO3KijwR6QkXNIWqOm0CCPmV4ds-twwhWFIsiZHl2ORkUjyW3ZEUppM8xPhnWfFw3kI2TVlEC95yH501AWM5VBLLQSviCNo0o4PVoMYNs7NlvXA" alt=""><figcaption></figcaption></figure>
3. Users can filter through the change requests by status, by using the relevant tabs at the top left.\\

   <figure><img src="/files/OyJIQWfRg7nRlD8rsLsW" alt=""><figcaption></figcaption></figure>
4. To view a specific change request, click on the arrow at the far right of the row to expand it.\\

   <figure><img src="https://lh4.googleusercontent.com/XCxYmm7Qs_bCuDZJ05zhq_PUOXcNKQL0XtVb3g-nwOv_5Crl53279QeKGzFr9nNRW5Tc0mrycaWqdMMHaGqOqyRf6GFPyLnV8AxBl3NWjEdfeQFZDTJwy9t6tqklGSajvfR9qjGOFR1hVvPRyLgoOaONAFwGv2sWraCwMphJqoKWB6Pz06lsgh8gng" alt=""><figcaption></figcaption></figure>

## Addressing a change request

1. Navigate to the *Change Requests* module.\\

   <figure><img src="/files/MFwQi1m1PanqOEtPY7LM" alt=""><figcaption></figcaption></figure>
2. Find the change request you would like to address.\\

   <figure><img src="https://lh4.googleusercontent.com/rkn4JmTflkah5yXmNtHBck8LMAQYDYq63Edh5pCHFREvoofQjgJV9PgVWBjkuTh5Ea5F_FZbqDsLO3KijwR6QkXNIWqOm0CCPmV4ds-twwhWFIsiZHl2ORkUjyW3ZEUppM8xPhnWfFw3kI2TVlEC95yH501AWM5VBLLQSviCNo0o4PVoMYNs7NlvXA" alt=""><figcaption></figcaption></figure>
3. Expand the change request to view the requested changes. The specific changes requested by the user will be marked with an orange dot in the relevant tabs. Note that a change request can contain multiple changes across a Geo-Object’s attributes and/or hierarchy information and/or geometry and/or settings, and each can be individually accepted or rejected.\\

   <figure><img src="/files/VMevkpwvAZPsq7Ew0RgZ" alt=""><figcaption></figcaption></figure>
4. Accept or reject each change using the designated buttons. If the Registry Contributor has uploaded a document to go with the change request, this can be reviewed by clicking on the attachment links under the *Reference Documents* section to download the files.\
   ![](https://lh6.googleusercontent.com/AHqDMGaSemYFilV1Hb5hjMT4Zd-vf_bY168k-K9sI__wLyTYXwgO3IiQnlfsxTndfJwisPUoQMhcBWu6r5KQswDmNfb4gk8M0nJa5E1DmxhzJQtm99Okky27Wbio39JOWSkYncmuZkwQdUhUT_1x7nEzv3JRJ5u4eWNGRrwHY_ccmtHPxqVmHICveQ)

   <figure><img src="/files/LJ6n1EIgbXMSZIUjIV1s" alt=""><figcaption></figcaption></figure>
5. Once you have made a decision on each requested change, notes can be added to the change request in the designated fields at the bottom:
   1. *Maintainer Notes:* any notes you would like to make as a reviewer of the change request, for example, reasons why you rejected certain changes
   2. *Additional Decision Makers:* any comments on the change requests from stakeholders involved in the officialization of the change request.\\

      <figure><img src="https://lh6.googleusercontent.com/P9oJb8TNiCJ3DhsY3wnGiXYy1enFAMrMUzu0BnfgcCylwZWuwB9vCUN7L9luA_WCDzjZiTnnoXMDK0jQocDeghr8cNwbEcE52hNKQeKNoqjBDkeWI_ozbnnfNd-2UYNvVPlUPm2a-C5cAWo4iQLcm3w_82IQ-yH0Nn5wmMwAfC--Nkv3At0lrm1qJg" alt=""><figcaption></figcaption></figure>
6. To finish reviewing the change request, click on **Implement Decisions**. This will commit all the changes you have accepted to the graph database.
7. You will be given the option to stay in the *Change Request* module or make further edits to the Geo-Object in the Geo-Object editing view.\\

   <figure><img src="https://lh3.googleusercontent.com/ZaqpUTtx4E5AcFbkq6ni_coGSOhof5ShmRhOZ2KbDrdQhoVlRKhb39RRnaoJkFfrZVMRX7XPv6osaNaCdg0FOVh2LKoDYKN5qjnu7-YlKAJvog2e8a2u_qN3goSWBGAYNFwbdJnCch2idNkTB1PsMKW5g6cwx5346V9BArRCcKzfdQDYUermgYHqZw" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.geoprismregistry.com/readme/current-1/geoprism-registry-tutorial/6.5-content-management/6.5.2-change-requests/6.5.2.2-review-a-change-request.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
