Document Access Feature (Public Links) – Server Side Refactoring

[mahid797]

Refactor the server-side architecture for the Document Access feature to enable dynamic visitor fields using JSON storage, improve schema consistency, and set the foundation for future analytics and link preference updates. These changes will ensure a scalable, professional, and future-proof backend for handling document sharing via public links.

---

Overview

• Refactor the Link → DocumentLink model to improve naming conventions and add dynamic visitor field support via JSON.
• Rename and update the LinkVisitors → DocumentLinkVisitor model to use JSON-based visitor data while allowing future expansion without additional migrations.
• Improve uniqueness constraints, field naming consistency, and ownership clarity.
• Prepare the groundwork for future features, including link preference updates (e.g., expiration time, public/private toggling, alias changes) and analytics tracking for views/downloads.

📢 Note:
While this issue covers schema changes and backend logic for the Document Access feature, client-side adjustments will be addressed in a separate issue.
Future enhancements (such as the Analytics API and Link Creation Update) will also be tracked in subsequent issues.

References

• Client-Side Refactoring Issues:
  • Document Access Feature (Public Links) – Client Side Refactoring #217
  • Link Creation Feature – Client Side Refactoring #218

📄 Note:
It is strongly recommended to read through all related issues (both Server Side and Client Side) before beginning development to ensure a full understanding of the scope, dependencies, and overall feature flow. This will help avoid redundant work and ensure consistency across all components.