Added DIP removal BEFORE dedup suppression warning

.gitignore

@@ -4,3 +4,4 @@ docs/
 public/
 content/.copy
 .post-*/
+content/.DS_Store

content/posts/149-Dealing-with-Alma-Dedup-and-FRBR/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Dealing with Alma Dedup and FRBR" 
 publishDate: 2024-12-19 12:48:37
-last_modified_at: 2024-12-19 12:48:46
+last_modified_at: 2024-12-20T08:45:33
 draft: false
 description: A public blog post copied from `Dealing-with-Alma-Dedup-and-FRBR.md` in my private repo at https://github.com/Digital-Grinnell/Migration-to-Alma-D.
 supersedes: 
@@ -19,8 +19,6 @@ azure:
 
 Together, Alma and Primo (mostly Primo) apply "dedup" and "FRBR" (Functional Requirements for Bibliographic Records) rules that unexpectedly "group" similar titles together.  Since the objects migrating from Islandora to Alma are all intended to be single and un-grouped (unless they are parts of a compound object where we expect and an intentional "grouping" of records), we need to take action to deal with these rules.  Unfortunately, we cannot just turn the rules off or universally modify them since those rules also apply to ALL bib records, not just digital items.
 
-When records are "grouped" together 
-
 # Understanding the Rules
 
 I have yet to see these rules in-the-flesh, but the observed effects suggest that...
@@ -71,6 +69,10 @@ The following email and Slack excerpts chronicle steps taken to deal specificall
 
 Eventually, after about an hour the targeted group of bibs was "disolved" yielding two distinct records as was intended, rather than a group with two "versions". 
 
+{{% alert %}}
+Experience with PHPP Community Contribution objects having identical titles of "411 First Avenue" suggests that DIP records --see post [Discovery Import Profile (DIP) Record Removal](../150-discovery-import-profile-dip-record-removal/)-- **MUST be removed BEFORE running the dedup suppression** job, otherwise the dedup may not be successfully suppressed.
+{{% /alert %}}
+
 ## Suppressing Dedup and FRBR Rules
 
 The workflow needed to suppress grouping of specific records is documented at https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/090Dedup_and_FRBR_for_Primo_VE/Suppressing_Groups_of_Records_from_Dedup%2F%2FFRBR_for_Primo_VE.  Note that while this is a "post-processing" step, it's useful only AFTER records have been imported, it does appear to "dissolve" existing unintended grouping as was suggested in the email excerpt which appears in `Ex Libris support suggested this...` above. 

layouts/shortcodes/alert.html

@@ -1,2 +1,7 @@
 {{ $_hugo_config := `{ "version": 1 }` }}
-<div class="original">{{ .Inner }}</div>
+<style>
+  .alert {
+    border: 2px red solid;
+    }
+</style>
+<div class="original alert">{{ .Inner }}</div>