Differences

This shows you the differences between two versions of the page.

--- hortus:discover:projects [2026/04/01 15:47] – savino.frisardi
+++ hortus:discover:projects [2026/04/08 11:22] (current) – savino.frisardi
@@ Line 1: / Line 1: @@
-===== Projects =====
+===== Projects: understand a research context before you join it =====
-==== What is a Project in HORTUS? ====
+In HORTUS, a **Project** is the highest-level structure for organizing and presenting a research initiative. It is much more than a simple page: it is the main aggregation layer where a research team can bring together its identity, its people, its outputs, its working materials, and its scientific conversations in one coherent space.
-A Project is a structured representation of a research initiative.
+A Project helps researchers understand a research initiative as a whole. Instead of discovering isolated resources one by one, users can open a Project page and immediately see the broader context: what the initiative is about, who is involved, which resources are connected to it, what discussions are taking place around it, and how they can engage with it. For this reason, Projects are one of the most important entry points into HORTUS for researchers, contributors, and project leaders alike.
-It acts as:
+A Project in HORTUS serves **three major functions at the same time.**
-  * a contextual hub
+First, it is a **research structuring instrument**. A Project gives a clear framework to a scholarly initiative by presenting its purpose, scope, methods, and internal organization. The introductory area of the Project page allows the team to build a rich and well-structured description, section by section, paragraph by paragraph. This makes it possible to explain the scientific rationale of the project in a way that is readable, attractive, and academically meaningful. Teams can enrich this description with labels, links, and multimedia elements, turning the Project page into a living research presentation rather than a static administrative record.
-  * a collaboration space
-  * a public-facing landing page
-A project typically includes:
+Second, it is an **attraction tool for collaboration**. A well-built Project page shows not only what the project does, but also who stands behind it. Through the **Contributors** area, users can discover the members of the project, access their profiles, and better understand the human network behind the work. This is particularly valuable for young researchers and doctoral candidates, who may use Projects to identify potential collaborators, supervisors, peer communities, or research teams working on similar topics. In this sense, a Project is not only a container of information: it is a visibility and networking instrument that can stimulate contact, dialogue, and scientific exchange across the Religious Studies community.
-  * description and objectives
+Third, it is an **aggregator of resources and activity**. A Project can gather together one or many resources from the HORTUS Marketplace, allowing users to see how individual research outputs belong to a larger intellectual or collaborative effort. Through the Resources tab, a user can move from the project narrative to the outputs that have been associated with it, such as datasets, publications, tools, images, or other research objects. This makes Projects especially useful for users who want to move from discovery to understanding: instead of seeing a resource as an isolated item, they can see how it contributes to a larger research programme.
-  * members and roles
-  * linked resources
-  * events and news
-  * discussions
-{{:hortus:discover:propject_list.jpg?400|}}
+Beyond formal resources, a Project also includes a **working space for collaboration**.
+Through the **Working folder** tab, project members may access shared documents and working materials, depending on their permissions. This allows a Project to function not only as a public-facing landing page, but also as a practical collaboration environment for the team itself. In other words, a Project combines public presentation and internal work: it can be both a scholarly showcase and a workspace for ongoing research activity.
+Projects also support **scientific interaction and debate**. Through the **Discussions** tab, users can ask questions, leave comments, raise issues, and develop exchanges that remain attached to the project context. This is important because it keeps the conversation connected to the research initiative itself. Instead of scattering debate across email threads or external tools, HORTUS allows the discussion to remain visible, contextualized, and reusable for other users who later arrive on the same Project page. This makes Projects a natural place not only for collaboration, but also for community-building and scholarly dialogue.
+Another powerful aspect of Projects is their ability to include **action-oriented buttons and external links**. Project maintainers can add as many call-to-action buttons as needed to direct users toward meaningful next steps. A Project can therefore include buttons linking to a Training Centre activity, a YouTube channel, a registration form, a survey, an external repository, documentation, a website, or any other relevant destination. These buttons make the Project page dynamic and interactive: they allow the page to connect users not only to information, but also to concrete actions, both inside and outside HORTUS. This is one of the reasons why Projects can become highly effective gateways for engagement.
+Projects in HORTUS are also **hierarchical**. A Project can exist as a main project, but it can also contain one or more **sub-projects**. This is especially useful when a large research initiative includes several teams, work packages, thematic branches, or specialized developments. For example, a major project on Bibles could include one sub-project focused on a digital annotation tool, another sub-project focused on manuscript imaging, and another one focused on software creation. This hierarchy allows the platform to reflect the real structure of complex research work. It also helps users understand how different strands of work relate to each other inside the same broader initiative.
+For the user, this means that a Project is often the **best place to start** when trying to understand a scholarly activity on HORTUS. A resource tells you what has been produced. A profile tells you who a person is. But a Project shows you how people, outputs, collaboration, working documents, and research goals fit together. It gives you the narrative, the team, the outputs, the debate, and the pathways to engage.
+A good way to think about a Project in HORTUS is this:
+**A PROJECT IS THE DIGITAL HOME OF A RESEARCH INITIATIVE.**
+It explains the work, gathers the outputs, showcases the people, supports interaction, and creates bridges toward future collaboration.
+For a young researcher, this makes Projects particularly valuable. A Project page can help you discover where interesting work is happening, who is leading it, which resources have already been produced, and whether there is space to connect, contribute, or follow the initiative more closely. For an experienced researcher, it offers a powerful way to structure and present research activity in a visible, coherent, and reusable form. For a project leader, it becomes both a communication tool and a collaboration tool: a place to describe the initiative, coordinate participation, connect outputs, and sustain scholarly engagement over time.
+In practical terms, a Project page in HORTUS may include:
+  * a structured textual presentation of the research initiative
+  * tags, metadata, and contextual information
+  * linked resources from the Marketplace
+  * a list of contributors and members
+  * working folders and shared documents, depending on permissions
+  * a discussion space for scientific exchange
+  * engagement actions such as **Request to join, Favourite/Follow, Share, and Leave feedback**
+  * custom call-to-action buttons linking to internal or external destinations
+  * parent/child relationships that reflect the structure of a larger research programme
+Taken together, these elements make Projects one of the most strategic features of HORTUS. They are not just pages to describe research: they are the platform’s main way of **organizing, connecting, presenting, and activating research communities**.
 ----
-==== Your Project User Experience ====
+==== Your PROJECT User eXperience (UX) in HORTUS ====
+{{:hortus:discover:propject_list.jpg?600|}}
+^ Projects list CTA ^ How to trigger it ^ What it does for the user ^
+| **Open a project detail page** | Click the project title in the results list. | Opens the project landing page on the Intro tab so you can evaluate its scope, people, and outputs. |
+| **Filter by project type** | Use the left-side type filter. | Narrow the list to project pages or tools depending on the available options. |
+| **Search by keyword** | Enter a keyword in the left filter panel. | Narrow results to projects matching the title, description, or tags. |
+| **Save filtered search** | Use the Save filtered search control and assign a name. | Stores the filter combination so you can reuse it later. |
+| **Favourite a project** | Click the star in the list or detail page. | Adds the project to your favourites and may prompt you to follow it for notifications. |
+| **Switch view (List / Cards)** | Click the view toggle icons (list or grid) above the results list | Lets you choose how projects are displayed: a compact list for quick comparison or visual cards for easier browsing |
+| **Sort projects** | Click on a column header (Title, Maintainer, Creation date, Publication date, Tags) | Reorders the projects list based on the selected field, helping you quickly find the most relevant or recent projects |
+| **Export the current list** | Use the export control on the list page. | Downloads a spreadsheet-style snapshot for offline review or team discussion. |
+----
+{{:hortus:discover:project_detail.jpg?600|}}
-When you open a project page, you will typically see:
+^ Project detail area ^ What's in for me? ^ Typical next step ^
+| Intro tab | Abstract, scope, structured sections, maintainers, licence, keywords, and CTA buttons. | Decide whether the project is relevant to your work. |
+| Marketplace tab | All resources including Datasets, publications, tools, or related outputs attached to the project. | Open a resource detail page or note that the area is still empty. |
+| Contributors tab | Names, affiliations, and profile links of the people behind the project. | Open an expert profile or message a contributor. |
+| Working Folder tab | Shared working materials and project-level documents, depending on permissions. | Open or preview a file; move into My Workspace if you become a project member. |
+| Discussions tab | Questions, replies, debates and feedback attached to the project context. | Ask a question, leave feedback, or follow the project. |
+| Share | Opens a copy-link and social sharing dialog. | Use it when you want to disseminate the event quickly. |
+| Export to PDF | Generates a PDF with the project abstract, the contributors' card and the metadata | Use it when you want to reuse some project information for your research activities |
+| Leave feedback | Starts a feedback or comment route. | Use it when you need clarification or want to give structured feedback to organisers. |
+| Request to join | A request is sent to the project leaders | when the project is open to participation requests |
+| Add to favourites / follow | Click the star icon next to the Message button. | Save the profile to your favourites and, where available, subscribe to updates related to this expert. |
-  * Overview (main description)
-  * Members / participants
-  * Linked resources (Marketplace items)
-  * Events related to the project
-  * Discussions
-==== What you can do ====
+{{:hortus:discover:requestjoindialogue.jpg?600|}}
-Depending on your role:
+**I have found a project of interest**
+    * Use **Request to join** when the project is open to participation requests.
+    * Use **Share** when you want to send the project to colleagues without reproducing the navigation path manually.
+    * Use **Favourite and Follow** when you want to monitor updates without joining immediately.
-  * read and evaluate the project
+If you are a project lead, My Workspace later gives you the tools to invite users, review join requests, and manage project relations.
-  * join or follow the project
-  * participate in discussions
-  * contribute content (if authorised)
-  * manage the project (if maintainer)
 ----