DOCSP-49594 -- Migration of financial services docs

[xargom]

Staging 1
Staging 2
Staging 3
Staging 4
Staging 5
Staging 6
Staging 7
Staging 8
Staging 9

Landing Page

DOCSP-49597

Epic: DOCSP-49594

[netlify]

✅ Deploy Preview for docs-atlas-architecture ready!

Name	Link
🔨 Latest commit	150d499
🔍 Latest deploy log	https://app.netlify.com/projects/docs-atlas-architecture/deploys/68362b95bd8b19000811d5c6
😎 Deploy Preview	https://deploy-preview-193--docs-atlas-architecture.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[nvillahermosa-mdb]

Tagged the two SVG images where it expects a width and height attribute in the SVG file itself. Those are the ones causing warnings. You can also look at sol_lib_doc.svg for another example of an image that has those attributes.

[nvillahermosa-mdb]

It looks like the build expects "width" and "height' elements in the SVG file itself, not in the rST that references it. For example

[xargom]

Yup, this solved it. Thanks!

[xargom]

Tried adding the "width" and "height" values multiple times for both images. It solved the build warning but failed at rendering. Worth noticing that they already have multiple instances of these values. I went back to the initial version of the files' code.

[nvillahermosa-mdb]

Fair enough. We might have to adjust these in whatever program was used to create them to fully resolve the warnings, which I think is a stretch for content migration.

[nvillahermosa-mdb]

Feedback for "Assessing Business Loan Risks"

[nvillahermosa-mdb]

Suggested change

	.. figure:: /includes/images/industry-solutions/chatGPT-flood-risk-assessment.png
	.. figure:: /includes/images/industry-solutions/GPT-flood-location-specific-answer-png.png

This should be this image.

[nvillahermosa-mdb]

Suggested change

	leveraging Geospatial Queries to discover floods within five kilometers of the proposed
	leveraging `geospatial queries <https://www.mongodb.com/docs/manual/geospatial-queries/>`_ to discover floods within five kilometers of the proposed

Added ref from original article

[nvillahermosa-mdb]

Suggested change

	`MAAP partner <https://www.mongodb.com/services/consulting/ai-applications-program>`_
	`MAAP <https://www.mongodb.com/services/consulting/ai-applications-program>`_ partner

Splitting this out as it is in the original article, so it doesn't look like one big link

[nvillahermosa-mdb]

Interactive Banking feedback

[nvillahermosa-mdb]

Suggested change

	leveraging `Vector Search
	leveraging `MongoDB Atlas Vector Search

Matching link text from article

[nvillahermosa-mdb]

Suggested change

	- By `using Atlas Vector Search
	- By using `Atlas Vector Search

Link text adjustment.
As far as the link itself -- it's the right one from the original article, but that has a lot of ad / search metadata in it. Do we want all that in this article? Is the tracking info accurate if users are clicking the article from our solutions library? I'm wondering if this URL was originally used in error, compared to something like https://www.mongodb.com/products/platform/atlas-vector-search which we use elsewhere in this article.

[nvillahermosa-mdb]

Fraud Solution feedback -- this one looks good, but it uses a deprecated product.

[nvillahermosa-mdb]

The "Atlas App Services" link is broken and redirects back to "Products", but this is also true in the original article. It looks like they're deprecated. For migration purposes, the article looks good, but we might want to figure out some wording and put a disclaimer at the top that links to that page.

We could update the URL in this article to go to that docs page, so users can see it's deprecated. Same with the repeated URL at the end.

[nvillahermosa-mdb]

Broken app services link again, like the current live article.

[nvillahermosa-mdb]

Card Fraud Solutions feedback

[nvillahermosa-mdb]

Suggested change

	1. **Data sourcing**
	1. **Data sourcing**

Adding a newline to fix nesting

[nvillahermosa-mdb]

Another link to the deprecated App Services, which we may want to point at the docs page instead.

[nvillahermosa-mdb]

Oddly, the original article uses "Key Considerations" here. I'm fine with keeping Key Learnings for consistency, but wanted to make a note of it.

[nvillahermosa-mdb]

Vector Search Fraud Prevention + AML feedback.

[nvillahermosa-mdb]

Suggested change

	This solution will look at how the convergence of real-time analytics `using MongoDB Atlas
	This solution will look at how the convergence of real-time analytics using `MongoDB Atlas

Moved over the link text for consistency

[nvillahermosa-mdb]

Suggested change

	By incorporating {+avs+}, institutions can: - Build intelligent applications
	powered by semantic search and generative AI over any type of data. - Store vector
	embeddings right next to source data and metadata–vectors inserted or updated in the
	database are automatically synchronized to the vector index. - Optimize resource
	consumption, improve performance, and enhance availability with `Search Nodes
	<https://www.mongodb.com/docs/atlas/atlas-search/atlas-search-overview/>`__. - Remove
	operational heavy lifting with the battle-tested, fully managed |service-fullname| modern,
	multi-cloud database platform.
	By incorporating {+avs+}, institutions can:
	- Build intelligent applications powered by semantic search and generative AI
	over any type of data.
	- Store vector embeddings right next to source data and metadata–vectors
	inserted or updated in the database are automatically synchronized to the
	vector index.
	- Optimize resource consumption, improve performance, and enhance availability
	with `Search Nodes <https://www.mongodb.com/docs/atlas/atlas-search/atlas-search-overview/>`__.
	- Remove operational heavy lifting with the battle-tested, fully managed
	|service-fullname| modern, multi-cloud database platform.

Line breaks and indentation to fix bulleted list rendering

[nvillahermosa-mdb]

Open Finance Data Store feedback

[nvillahermosa-mdb]

This is a correct migration of the article as is, but should probably be a heading in the final version. Nice work on formatting this article in general, I like the cleanup!

[nvillahermosa-mdb]

Suggested change

	**Step 4: Run it locally** Set up a virtual environment using Poetry, install
	dependencies, and start the backend with uvicorn. Ensure the service runs on the correct
	port for API communication.
	**Step 4: Run it locally**
	Set up a virtual environment using Poetry, install dependencies, and
	start the backend with uvicorn. Ensure the service runs on the correct
	port for API communication.

Adding a missed line break for formatting