diff --git a/doc/release-notes/6510-duplicate-datafiles-and-datatables.md b/doc/release-notes/6510-duplicate-datafiles-and-datatables.md
new file mode 100644
index 00000000000..d0440374def
--- /dev/null
+++ b/doc/release-notes/6510-duplicate-datafiles-and-datatables.md
@@ -0,0 +1,24 @@
+We recently discovered that *potential* data integrity issues in
+Dataverse databases.  One manifests itself as duplicate DataFile
+objects created for the same uploaded file; the other as duplicate
+DataTable (tabular metadata) objects linked to the same
+DataFile. (GitHub issues https://github.com/IQSS/dataverse/issues/6522
+and https://github.com/IQSS/dataverse/issues/6510 respectively).
+
+Please run the diagnostic script provided at
+https://github.com/IQSS/dataverse/raw/6510-repeated-ingests/scripts/issues/6510/check_datafiles_6522_6510.sh
+[NOTE!! the branch name must be changed to "develop" in the URL above before we merge!!]
+
+The script relies on the PostgreSQL utility psql to access the
+database. You will need to edit the credentials at the top of the script
+to match your database configuration.
+
+If neither of the two issues is present in your database, you will see
+a message "... no duplicate DataFile objects in your database" and "no
+tabular files affected by this issue in your database".
+
+If either, or both kinds of duplicates are detected, the script will
+provide further instructions. We will need you to send us the produced
+output. We will then assist you in resolving the issues in your
+database.
+
diff --git a/doc/release-notes/6522-datafile-duplicates.md b/doc/release-notes/6522-datafile-duplicates.md
deleted file mode 100644
index 39abb49cd69..00000000000
--- a/doc/release-notes/6522-datafile-duplicates.md
+++ /dev/null
@@ -1,27 +0,0 @@
-In this Dataverse release, we are adding a database constraint to
-prevent duplicate DataFile objects pointing to the same physical file
-from being created.
-
-Before this release can be deployed, your database must be checked
-for any such duplicates that may already exist. If present,
-the duplicates will need to be deleted, and the integrity of the 
-stored physical files verified.
-
-(We have notified the community about this issue ahead of the release,
-so you may have already addressed it. In this case, please disregard
-this release note)
-
-Please run the diagnostic script provided at
-https://github.com/IQSS/dataverse/raw/develop/scripts/issues/6522/find_duplicates.sh.
-The script relies on the PostgreSQL utility `psql` to access the
-database. You will need to edit the credentials at the top of the script
-to match your database configuration.
-
-If this issue is not present in your database, you will see a message
-`... no duplicate dvObjects in your database. Your installation is
-ready to be upgraded to Dataverse 4.20`.
-
-If duplicates are detected, it will provide further instructions. We
-will need you to send us the produced output. We will then assist you
-in resolving this problem in your database.
-
diff --git a/scripts/issues/6510/PRE-RELEASE-INFO.txt b/scripts/issues/6510/PRE-RELEASE-INFO.txt
new file mode 100644
index 00000000000..d0440374def
--- /dev/null
+++ b/scripts/issues/6510/PRE-RELEASE-INFO.txt
@@ -0,0 +1,24 @@
+We recently discovered that *potential* data integrity issues in
+Dataverse databases.  One manifests itself as duplicate DataFile
+objects created for the same uploaded file; the other as duplicate
+DataTable (tabular metadata) objects linked to the same
+DataFile. (GitHub issues https://github.com/IQSS/dataverse/issues/6522
+and https://github.com/IQSS/dataverse/issues/6510 respectively).
+
+Please run the diagnostic script provided at
+https://github.com/IQSS/dataverse/raw/6510-repeated-ingests/scripts/issues/6510/check_datafiles_6522_6510.sh
+[NOTE!! the branch name must be changed to "develop" in the URL above before we merge!!]
+
+The script relies on the PostgreSQL utility psql to access the
+database. You will need to edit the credentials at the top of the script
+to match your database configuration.
+
+If neither of the two issues is present in your database, you will see
+a message "... no duplicate DataFile objects in your database" and "no
+tabular files affected by this issue in your database".
+
+If either, or both kinds of duplicates are detected, the script will
+provide further instructions. We will need you to send us the produced
+output. We will then assist you in resolving the issues in your
+database.
+