Pular para conteúdo

Project Backlog - ResearchDomain

This document is automatically synchronized with GitHub Issues. Last updated: 2026-03-29 01:50:53

📋 Master Issue List

Overview of all demands, their states and executors.

# Status Title Executor Sprint Milestone
# 55 🟢 [EPIC] Implement Research Production Management (Dynamic Types) @paulossjunior - Issue Base
# 49 🟢 Add resume field to Researcher entity - - Issue Base
# 34 🟢 [feat] Implement Advisorship Types and Examination Board @paulossjunior - Issue Base
# 30 🟢 [feat] Implement Article Architecture Layers @paulossjunior - Issue Base
# 29 🟢 [feat] Add Article Type (Journal vs Conference) @paulossjunior - Issue Base
# 28 🟢 [feat] Implement Article Entity and Author Relationship @paulossjunior - Issue Base
# 27 🟢 [feat] Implement Metadata Entities (Language, Award, Proficiency) @paulossjunior - Issue Base
# 26 🟢 [feat] Add Proficiencies and Awards to Researcher @paulossjunior - Issue Base
# 25 🟢 [feat] Implement Academic Education History for Researcher @paulossjunior - Issue Base
# 22 🟢 [feat] Add Sponsor Organization to Fellowship @paulossjunior - -
# 20 🟢 Feat: Implement Services and Improve Factories @paulossjunior - Issue Base
# 17 🟢 Feat: Associate Initiative to Demandante (Organization) @paulossjunior - -
# 15 🟢 Feat: Associate Initiative to External Research Group @paulossjunior - -
# 13 🟢 Feat: Associate Knowledge Area to Initiatives @paulossjunior - -
# 9 ✅ [US] Researcher Academic Metadata & Knowledge Areas - - Issue Base
# 6 ✅ [TASK] Implementation of Role-based Leadership and Many-to-Many Areas - - Issue Base
# 5 ✅ [US] ResearchGroup Categorization & Leadership Recognition - - Issue Base
# 4 ✅ [EPIC] ResearchGroup Metadata & Advanced Membership - - Issue Base
# 1 ✅ Implement ResearchGroup Feature (Entities, Repositories, Controllers) - - Issue Base

📂 Workflow States

🟢 In Progress / Todo

  • #55 [EPIC] Implement Research Production Management (Dynamic Types)
  • #49 Add resume field to Researcher entity
  • #34 [feat] Implement Advisorship Types and Examination Board
  • #30 [feat] Implement Article Architecture Layers
  • #29 [feat] Add Article Type (Journal vs Conference)
  • #28 [feat] Implement Article Entity and Author Relationship
  • #27 [feat] Implement Metadata Entities (Language, Award, Proficiency)
  • #26 [feat] Add Proficiencies and Awards to Researcher
  • #25 [feat] Implement Academic Education History for Researcher
  • #22 [feat] Add Sponsor Organization to Fellowship
  • #20 Feat: Implement Services and Improve Factories
  • #17 Feat: Associate Initiative to Demandante (Organization)
  • #15 Feat: Associate Initiative to External Research Group
  • #13 Feat: Associate Knowledge Area to Initiatives

✅ Done / Released

  • #9 [US] Researcher Academic Metadata & Knowledge Areas
  • #6 [TASK] Implementation of Role-based Leadership and Many-to-Many Areas
  • #5 [US] ResearchGroup Categorization & Leadership Recognition
  • #4 [EPIC] ResearchGroup Metadata & Advanced Membership
  • #1 Implement ResearchGroup Feature (Entities, Repositories, Controllers)

📝 Detailed Backlog

[OPEN] #55 [EPIC] Implement Research Production Management (Dynamic Types)

  • Executor: paulossjunior
  • Labels: feature, epic
  • Milestone: Issue Base

Description:

Proposta de Issue (GitHub)

Título: [EPIC] Implement Research Production Management (Dynamic Types) Descrição: Implementação da entidade ResearchProduction e suas camadas arquiteturais (Repository, Service, Controller) para suportar produções acadêmicas além de artigos científicos, incluindo Livros, Capítulos e Software. A entidade ProductionType será uma entidade independente para permitir tipos dinâmicos. Referências: FR-07 em docs/requirements.md. Campos (MANDATÓRIOS): - Label: epic - Type: feature - Milestone: Issue Base - Project: The Band Project - Assignee: @paulossjunior

Tarefas: - [x] Atualizar documentação (requirements.md, sdd.md, entities.md). - [ ] Implementar entidade ProductionType. - [ ] Implementar entidade ResearchProduction. - [ ] Implementar relacionamento Many-to-Many entre Researcher e ResearchProduction. - [ ] Criar interfaces e implementações de Repositório (Postgres). - [ ] Criar camada de Serviço e Controller. - [ ] Adicionar testes unitários e exemplos no demo.

[OPEN] #49 Add resume field to Researcher entity

  • Executor: -
  • Labels: feature, task
  • Milestone: Issue Base

Description: This issue tracks the addition of a resume field (Text) to the Researcher entity to store a brief professional summary.

Tasks: - [ ] Update documentation (entities.md, sdd.md). - [ ] Add resume field to Researcher entity in researcher.py. - [ ] Update ResearcherController to support the new field. - [ ] Add unit tests for the field.

Details: - Label: task - Type: feature - Project: The Band Project - Assignee: @paulossjunior

[OPEN] #34 [feat] Implement Advisorship Types and Examination Board

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Enhance Advisorship with types/program/institution and create Examination Board entity for defense committees.

[OPEN] #30 [feat] Implement Article Architecture Layers

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Create Repository, Service, and Controller for Article entity following strict layered architecture.

[OPEN] #29 [feat] Add Article Type (Journal vs Conference)

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Add ArticleType Enum (PERIODICO, EVENTO) and update Article entity to distinguish publication types.

[OPEN] #28 [feat] Implement Article Entity and Author Relationship

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Implement Article entity with Many-to-Many relationship to Researcher. - Article Entity - Researcher Relationship (Authors) - Tests

[OPEN] #27 [feat] Implement Metadata Entities (Language, Award, Proficiency)

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Refactor metadata into dedicated entities to support normalization. - Language Entity - Proficiency Entity - Award Entity - Citation Names as String

[OPEN] #26 [feat] Add Proficiencies and Awards to Researcher

  • Executor: paulossjunior
  • Labels: feature
  • Milestone: Issue Base

Description: Add (JSON List) and (JSON List) to Researcher.

[OPEN] #25 [feat] Implement Academic Education History for Researcher

  • Executor: paulossjunior
  • Labels: feature, us
  • Milestone: Issue Base

Description: Implement requirement FR-01-E and FR-01-F. Store academic history (graduation, master, phd) for researchers, distinct from Knowledge Areas.

[OPEN] #22 [feat] Add Sponsor Organization to Fellowship

  • Executor: paulossjunior
  • Labels:
  • Milestone: -

Description: Implement requirement FR-05-H as detailed in docs/requirements.md. A Fellowship must now be associated with an Organization that acts as its sponsor.

[OPEN] #20 Feat: Implement Services and Improve Factories

  • Executor: paulossjunior
  • Labels: feature, task
  • Milestone: Issue Base

Description: Implement the service layer for the recently added domain entities and refactor ServiceFactory for better maintainability.\n\nRef: docs/requirements.md (FR-05-C, FR-05-E, FR-05-G)

[OPEN] #17 Feat: Associate Initiative to Demandante (Organization)

  • Executor: paulossjunior
  • Labels: epic
  • Milestone: -

Description: Implement Many-to-One relationship between Initiative and Organization (Demandante).\n\nRef: docs/requirements.md (FR-05-D)

[OPEN] #15 Feat: Associate Initiative to External Research Group

  • Executor: paulossjunior
  • Labels: epic
  • Milestone: -

Description: Implement ExternalResearchGroup entity and many-to-many relationship with Initiative.\n\nRef: docs/requirements.md (FR-05-C)

[OPEN] #13 Feat: Associate Knowledge Area to Initiatives

  • Executor: paulossjunior
  • Labels: epic
  • Milestone: -

Description: Implement Many-to-Many relationship between KnowledgeArea and Initiative entities.\n\nRef: docs/requirements.md (FR-05-B)

[CLOSED] #9 [US] Researcher Academic Metadata & Knowledge Areas

  • Executor: -
  • Labels: feature, us
  • Milestone: Issue Base

Description:

Description

As a researcher, I want my profile to include my academic links (CNPq, Google Scholar) and my specialized knowledge areas so that I can be correctly identified within the research domain.

Acceptance Criteria

  • Researcher entity supports cnpq_url (optional string).
  • Researcher entity supports google_scholar_url (optional string).
  • Researcher can be associated with multiple KnowledgeAreas (Many-to-Many).
  • Code must follow TDD (Tests First).
  • Documentation updated (requirements.md, sdd.md).

Technical Metadata

  • Documentation: Updated in docs/requirements.md (FR-01-C, FR-01-D).
  • Architecture: Domain Layer update.

[CLOSED] #6 [TASK] Implementation of Role-based Leadership and Many-to-Many Areas

  • Executor: -
  • Labels: feature, task
  • Milestone: Issue Base

Description:

Description

Implement the technical changes for Role integration, Many-to-Many KnowledgeAreas, and Temporal Membership.

Associated US

Associated with #5

Technical Tasks

  • [ ] Integrate Role entity and create default roles ("Leader", "Researcher").
  • [ ] Implement KnowledgeArea and group_knowledge_areas association table.
  • [ ] Update ResearchGroup and TeamMember (from eo_lib) schemas.
  • [ ] Implement membership/leadership temporal logic (start_date, end_date).
  • [ ] Update Controllers and Factories.
  • [ ] Verify with unit tests and demo script.

Definition of Done

  • Code passes all tests.
  • Documentation updated.
  • Pull Request created targeting developing.

[CLOSED] #5 [US] ResearchGroup Categorization & Leadership Recognition

  • Executor: -
  • Labels: feature, us
  • Milestone: Issue Base

Description:

Description

As a researcher, I want my research group to be correctly categorized with multiple Knowledge Areas and linked to external directories (CNPq) so it can be correctly found and its leadership recognized.

Parent Epic

Associated with #4

Acceptance Criteria

  • Researchers can assign multiple Knowledge Areas to a group.
  • Researchers can set the group's web page and CNPq link.
  • Leadership status is clearly defined by role and duration.

[CLOSED] #4 [EPIC] ResearchGroup Metadata & Advanced Membership

  • Executor: -
  • Labels: feature, epic
  • Milestone: Issue Base

Description:

Description

Implement metadata enhancements for ResearchGroups, including CNPq integration, site links, multiple knowledge areas (Many-to-Many), and Role-based temporal membership management (Leadership).

References

Detailed in: - docs/requirements.md - docs/sdd.md - docs/specifications.md

Acceptance Criteria

  • ResearchGroup supports cnpq_url and site.
  • ResearchGroup can be associated with multiple KnowledgeAreas.
  • TeamMember uses Role (specifically "Leader" for leadership roles).
  • TeamMember tracks start_date and end_date.
  • All layers (Domain, Infrastructure, Service, Controller) updated.

[CLOSED] #1 Implement ResearchGroup Feature (Entities, Repositories, Controllers)

  • Executor: -
  • Labels: enhancement, feature
  • Milestone: Issue Base

Description:

Context

Implement the core entities for the ResearchDomain library as specified in the updated documentation.

Requirements

  • A ResearchGroup is a Team.
  • A ResearchGroup must have at least one Researcher.
  • A ResearchGroup is present in a Campus.
  • A Campus is in a University.

Proposed Changes

  • Implement University (Organization), Campus (OrganizationalUnit), ResearchGroup (Team), and Researcher (Person).
  • Implement specialized repository interfaces and SQLAlchemy strategies.
  • Implement specialized controllers.

References

Detailed in docs/requirements.md, docs/sdd.md, and docs/specifications.md.