Fix #3747: Switch showcase instances on frontpage from vivo:faculty a…

[zparvez2z]

Pull Request: Switch showcase instances on frontpage from vivo:faculty and vivo:department to foaf:person and foaf:organization

VIVO GitHub issue: #3747 Switch showcase instances on frontpage from vivo:faculty and vivo:department to foaf:person and foaf:organization

What does this pull request do?

This PR addresses issue #3747 by changing the homepage showcase to use the broader classes foaf:Person and foaf:Organization instead of the more specific vivo:FacultyMember and vivo:AcademicDepartment. This change makes the homepage more inclusive by displaying all persons and organizations rather than just faculty members and academic departments.

What's new?

• Changed the SPARQL query in homePageDataGetters.n3 to use foaf:Organization instead of vivo:AcademicDepartment
• Updated JavaScript files (homePageUtils.js and theme-specific versions) to use foaf:Person instead of vivo:FacultyMember
• Updated "View All" links in both standard and theme-specific JavaScript files to point to the more general classes
• Updated the faculty member count logic in lib-home-page.ftl to check for Person instead of FacultyMember
• Updated section headers in templates to reflect the broader classes (People instead of Faculty, Organizations instead of Departments)

How should this be tested?

1. Run VIVO with these changes and view the homepage
2. Verify that the "Meet our people" section now displays a broader range of individuals, not just faculty members
3. Verify that the "Organizations" section shows all organizations, not just academic departments
4. Click the "View All" links to confirm they go to the correct URLs using foaf:Person and foaf:Organization
5. Check the network requests in browser developer tools to confirm the data service calls are using the correct class URIs

Additional Notes:

• This change may affect the content displayed on the homepage, as it will now include all persons and organizations, not just faculty and departments
• The section headers have been updated for consistency with the broader classes being used
• No additional dependencies are required for this change
• The theme-specific versions of the files have also been updated to maintain consistency