How alimedina18/vanessa works
Main Components
• Client/Browser: Represent how end users (researchers, students and administrators) interact with the system through a web user interface. The frontend is built mainly using HTML, CSS, and JavaScript (using Razor views).
• Presentation Layer (ASP.NET MVC):
– Controllers (e.g., AuthController, HomeController, ProyectosController, etc.) that handle incoming HTTP requests.
– Views (the folder structure under “Views”) for rendering HTML.
• Business Logic / Service Layer:
– The “Services” folder houses classes like AuthService, EmailService, and others that implement business rules.
• Data Access Layer:
– The “Data” folder contains the ApplicationDbContext (EF Core), database initialization (DbInitializer), and migrations that interact with SQL Server.
• Domain / Models Layer:
– The “Models” folder defines the business entities (e.g., Usuario, Proyecto, Publicacion, etc.) and view models.
• Infrastructure & Configuration:
– Appsettings.json files for configuration.
– Build and deployment configurations (publish profiles, service dependencies, etc.) indicate how the application is built and deployed.
• Static Assets:
– The “wwwroot” folder (both in the source and the release outputs) that serves static files such as images, CSS, JavaScript, and fonts.
• External Dependencies and Tools:
– Use hints from the README where Git, GitHub and online collaboration are mentioned.
– Also note that the project might later integrate AI modules for recommendations or connections between researchers.
Relationships and Interactions
– A user’s browser sends HTTP requests to the web server.
– The request is handled by the corresponding Controller.
– The Controller calls on one or more service classes (business logic) to process requests.
– The services access the Data Access layer (via ApplicationDbContext) to retrieve or persist domain models.
– Once complete, the Controller renders a View (using Razor) and sends a response back to the browser.
Architectural Patterns
• Layered Architecture: indicate that the UI (Views/Controllers) does not directly manage database persistence; it relies on clearly abstracted business services that call into a well-formed data access layer.
• That the project follows domain-driven design with clear Entities and ViewModels.
Relevant Technologies and Frameworks
• Frontend: HTML, CSS, JavaScript, Razor Views.
• Backend: C# using ASP.NET Core MVC.
• Database: SQL Server (with use of Entity Framework Core).
• Build/Deployment Tools: Visual Studio configuration files, .sln solution file, and publish profiles.
• Others: Git/GitHub for version control and collaboration tools.
Additional Elements to Consider
• Potential future integration points, such as an “AI Recommendation Module.”