From 8f7cea44124b805fba36790c1419e068d04b16fe Mon Sep 17 00:00:00 2001
From: sarina <sarina@axim.org>
Date: Thu, 4 Jul 2024 15:19:23 -0400
Subject: [PATCH] docs: Put OEP-32 in Needs Revision status

Partially addresses #407
---
 ...-0032-arch-unique-identifier-for-users.rst | 21 +++++++++++++++++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/oeps/architectural-decisions/oep-0032-arch-unique-identifier-for-users.rst b/oeps/architectural-decisions/oep-0032-arch-unique-identifier-for-users.rst
index b09b8c3fd..6a3bedd38 100644
--- a/oeps/architectural-decisions/oep-0032-arch-unique-identifier-for-users.rst
+++ b/oeps/architectural-decisions/oep-0032-arch-unique-identifier-for-users.rst
@@ -11,13 +11,15 @@ OEP-32: Unique Identifier for Users
    * - Title
      - Unique Identifier for Users
    * - Last Modified
-     - 2021-04-16
+     - 2024-07-08
    * - Authors
      - Brian Wilson, Robert Raposa, Nimisha Asthagiri
    * - Arbiter
      - Olga Stroilova
    * - Status
-     - Approved
+     - Needs Revision
+   * - Revision Ticket
+     - https://github.com/openedx/open-edx-proposals/issues/407
    * - Type
      - Architecture
    * - Created
@@ -25,6 +27,12 @@ OEP-32: Unique Identifier for Users
    * - `Review Period`
      - 2019-04-15 - 2019-04-29
 
+.. note::
+
+    The guidance for external ids in this OEP is currently incorrect; it has been superseded by `this ADR <https://github.com/openedx/edx-platform/blob/e1c8fb51bec2be3aa8da9750cb52b01728d1a740/openedx/core/djangoapps/external_user_ids/docs/decisions/0001-externalid.rst>`_.
+
+    The guidance in this OEP is partially correct. It is valid for internal ids, and invalid for external ids. For questions and discussion, please post on `GitHub issue 407 <https://github.com/openedx/open-edx-proposals/issues/407>`_.
+
 Decision
 ********
 
@@ -128,3 +136,12 @@ However, the introduction of a new id has large costs:
 * Data analytics is one area where, even though we don't have 100% compliance with use of the *LMS user_id*, we have enough compliance to make the data useful. Switching the user identifier for data analytics would require a large coordinated effort that would be difficult for data scientists with no benefit to them.
 
 * Adding another user id without being able to retire an old id also has the drawback of making the system less approachable, as each developer tries to learn which id to use in which situation.
+
+Change History
+**************
+
+2024-07-08
+==========
+* Change status to "Needs Revision"
+* `Discussion issue #407 <https://github.com/openedx/open-edx-proposals/issues/407>`
+* `Pull request #603 <https://github.com/openedx/open-edx-proposals/pull/603>`_
\ No newline at end of file