feat: Add MODS metadata fields to complement Dublin Core in ArticleOAIIndex #1213

Rossi-Luciano · 2025-11-11T15:57:38Z

O que esse PR faz?

Adiciona 25 campos MODS (Metadata Object Description Schema) ao ArticleOAIIndex, complementando Dublin Core com metadados bibliográficos estruturados.

Campos adicionados (7 grupos):

name.* (4 campos) - Autoria com ORCID e afiliações
subject.* (4 campos) - Taxonomias controladas (WoS, CAPES, Subject Areas)
relatedItem.host.* (5 campos) - Contexto de publicação (journal, volume, issue)
part.* (3 campos) - Paginação e elocation-id
identifier.* (3 campos) - ISSNs estruturados (print/electronic/linking)
originInfo.* (3 campos) - Publisher, local, data w3cdtf
accessCondition.* (3 campos) - Licenças e políticas Open Access

Benefícios:

Métricas bibliométricas avançadas (análise por instituição, autor, área)
Compliance com mandatos de fomento (FAPESP, CNPq, CAPES)
Interoperabilidade com repositórios institucionais e sistemas CRIS
Mantém 100% compatibilidade com índice Dublin Core existente

Onde a revisão poderia começar?

Arquivo: article/search_indexes.py

Ordem sugerida:

Declaração dos campos (linhas ~60-140) - verificar nomenclatura metadata.mods.*
Métodos prepare_mods_name_* (linhas ~200-350) - extração de ORCIDs e afiliações
Métodos prepare_mods_subject_* (linhas ~350-450) - integração com taxonomias

Como este poderia ser testado manualmente?

1. Reindexar Solr:

python manage.py rebuild_index --noinput
python manage.py haystack_info

2. Verificar campos no Solr:

curl "http://localhost:8983/solr/<core>/select?q=*:*&rows=1&wt=json&indent=true"
curl "http://localhost:8983/solr/<core>/admin/luke?wt=json" | grep "metadata.mods"

3. Testar queries MODS:

# Artigos com ORCID
curl "http://localhost:8983/solr/<core>/select?q=metadata.mods.name.orcid:0000*"

# Artigos Open Access Gold
curl "http://localhost:8983/solr/<core>/select?q=metadata.mods.accessCondition.openAccess:gold"

# Artigos de categorias WoS
curl "http://localhost:8983/solr/<core>/select?q=metadata.mods.subject.wos:Medicine*"

Algum cenário de contexto que queira dar?

NA

Quais são tickets relevantes?

NA

Referências

Documentação MODS:

User Guidelines: https://www.loc.gov/standards/mods/userguide/
Journal Article Example: https://www.loc.gov/standards/mods/v3/modsjournal.xml
Subject Examples: http://www.loc.gov/standards/mods/v3/mods-3-7-subject-examples.pdf

Elementos específicos:

name: https://www.loc.gov/standards/mods/userguide/name.html
subject: https://www.loc.gov/standards/mods/userguide/subject.html
relatedItem: https://www.loc.gov/standards/mods/userguide/relateditem.html
accessCondition: https://www.loc.gov/standards/mods/userguide/accesscondition.html

Padrões relacionados:

ORCID: https://orcid.org/
ISSN: https://www.issn.org/
Creative Commons: https://creativecommons.org/licenses/

Copilot

Pull Request Overview

This PR adds 25 MODS (Metadata Object Description Schema) fields to the ArticleOAIIndex to complement the existing Dublin Core metadata with more structured bibliographic information. The additions enable advanced bibliometric analysis, better interoperability with institutional repositories, and compliance with funding agency mandates.

Key Changes:

Added 25 new MODS field declarations organized into 7 semantic groups (name, subject, relatedItem, part, identifier, originInfo, accessCondition)
Implemented 25 corresponding prepare_* methods to extract and format data from Article model relationships
Added 2 private helper methods for formatting affiliation and location data

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-12T12:09:45Z

article/search_indexes.py

+                if (pub_history.organization.acronym and
+                    pub_history.organization.acronym.strip()):
+                    pub_name += f" ({pub_history.organization.acronym.strip()})"
+
+            # Fallback para estrutura Institution legada
+            elif (pub_history.institution and
+                  pub_history.institution.institution and
+                  pub_history.institution.institution.institution_identification and
+                  pub_history.institution.institution.institution_identification.name):
+
+                inst_id = pub_history.institution.institution.institution_identification
+                pub_name = inst_id.name.strip()
+
+                if inst_id.acronym and inst_id.acronym.strip():
+                    pub_name += f" ({inst_id.acronym.strip()})"


[nitpick] Code duplication in acronym handling. Lines 1458-1460 and 1471-1472 have identical logic for appending acronyms in parentheses. Consider extracting to a helper method:

def _format_name_with_acronym(self, name, acronym): if not name: return None result = name.strip() if acronym and acronym.strip(): result += f" ({acronym.strip()})" return result

Copilot · 2025-11-12T12:09:45Z

article/search_indexes.py

+        if (hasattr(obj, 'pub_date_month') and obj.pub_date_month and
+            str(obj.pub_date_month).strip()):
+            date_parts.append(str(obj.pub_date_month).zfill(2))
+
+            if (hasattr(obj, 'pub_date_day') and obj.pub_date_day and
+                str(obj.pub_date_day).strip()):
+                date_parts.append(str(obj.pub_date_day).zfill(2))


Potential issue with date formatting: The code uses zfill(2) to pad month and day values (lines 1575, 1579), but doesn't validate that the values are numeric or within valid ranges. If pub_date_month or pub_date_day contain non-numeric strings, zfill will still work but produce invalid dates like "2023-ab-15". Consider adding validation or using proper date formatting.

Suggested change

if (hasattr(obj, 'pub_date_month') and obj.pub_date_month and

str(obj.pub_date_month).strip()):

date_parts.append(str(obj.pub_date_month).zfill(2))

if (hasattr(obj, 'pub_date_day') and obj.pub_date_day and

str(obj.pub_date_day).strip()):

date_parts.append(str(obj.pub_date_day).zfill(2))

# Validate and add month

if (hasattr(obj, 'pub_date_month') and obj.pub_date_month and

str(obj.pub_date_month).strip()):

try:

month_int = int(obj.pub_date_month)

if 1 <= month_int <= 12:

date_parts.append(f"{month_int:02d}")

# Validate and add day only if month is valid

if (hasattr(obj, 'pub_date_day') and obj.pub_date_day and

str(obj.pub_date_day).strip()):

try:

day_int = int(obj.pub_date_day)

if 1 <= day_int <= 31:

date_parts.append(f"{day_int:02d}")

except (ValueError, TypeError):

pass

except (ValueError, TypeError):

pass

Copilot · 2025-11-12T12:09:46Z

article/search_indexes.py

+    )
+
+    # MODS - originInfo
+    # Editora(s)


Spelling error: "Editora(s)" should use English "Publisher(s)" to maintain consistency with the codebase (all other comments are in English except Portuguese JUSTIFICATIVA sections).

Suggested change

# Editora(s)

# Publisher(s)

Copilot · 2025-11-12T12:09:46Z

article/search_indexes.py

+        researchers = obj.researchers.prefetch_related(
+            'researcheraka_set__researcher_identifier'
+        ).all()


The prefetch_related path 'researcheraka_set__researcher_identifier' may cause N+1 queries if researcher_identifier has foreign keys. Consider using select_related for the researcher_identifier relationship as well: prefetch_related(Prefetch('researcheraka_set', queryset=ResearcherAKA.objects.select_related('researcher_identifier')))

Copilot · 2025-11-12T12:09:46Z

article/search_indexes.py

+                    orcid = aka.researcher_identifier.identifier.strip()
+                    if orcid and orcid not in orcids:
+                        orcids.append(orcid)


[nitpick] The logic checks if orcid and orcid not in orcids before appending, which should prevent duplicates. However, this check happens inside nested loops (researchers -> aka), and the same ORCID from the same researcher could still be checked multiple times unnecessarily. The current implementation is correct but not optimal - consider collecting into a set first, then converting to list at the end for better performance with large datasets.

Copilot · 2025-11-12T12:09:48Z

article/search_indexes.py

+                location = institution.location
+
+                # Cidade
+                if location.city and hasattr(location.city, 'name') and location.city.name:
+                    parts.append(location.city.name.strip())
+
+                # Estado
+                if location.state:
+                    state_text = location.state.acronym or location.state.name
+                    if state_text:
+                        parts.append(state_text.strip())
+
+                # País
+                if location.country and location.country.name:
+                    parts.append(location.country.name.strip())
+
+        except (AttributeError, TypeError):
+            # Fallback para string simples
+            return str(affiliation) if affiliation else None
+
+        return " - ".join(parts) if parts else None
+
+    def _format_place_location(self, location):
+        """
+        Formata localização em string: "Cidade, Estado, País"
+
+        Args:
+            location: objeto Location
+
+        Returns:
+            str: "São Paulo, SP, Brasil"
+        """
+        if not location:
+            return None
+
+        parts = []
+
+        try:
+            # Cidade
+            if location.city and hasattr(location.city, 'name') and location.city.name:
+                parts.append(location.city.name.strip())
+
+            # Estado (preferir sigla)
+            if location.state:
+                state_text = location.state.acronym or location.state.name
+                if state_text:
+                    parts.append(state_text.strip())
+
+            # País
+            if location.country and location.country.name:
+                parts.append(location.country.name.strip())
+
+        except (AttributeError, TypeError):
+            return None
+
+        return ", ".join(parts) if parts else None
+


[nitpick] Code duplication between _format_affiliation and _format_place_location. Both methods have similar logic for formatting location information (city, state, country). The main difference is the separator (- vs , ) and the inclusion of institution info in _format_affiliation. Consider extracting the common location formatting logic into a separate helper method to reduce duplication.

Suggested change

location = institution.location

# Cidade

if location.city and hasattr(location.city, 'name') and location.city.name:

parts.append(location.city.name.strip())

# Estado

if location.state:

state_text = location.state.acronym or location.state.name

if state_text:

parts.append(state_text.strip())

# País

if location.country and location.country.name:

parts.append(location.country.name.strip())

except (AttributeError, TypeError):

# Fallback para string simples

return str(affiliation) if affiliation else None

return " - ".join(parts) if parts else None

def _format_place_location(self, location):

"""

Formata localização em string: "Cidade, Estado, País"

Args:

location: objeto Location

Returns:

str: "São Paulo, SP, Brasil"

"""

if not location:

return None

parts = []

try:

# Cidade

if location.city and hasattr(location.city, 'name') and location.city.name:

parts.append(location.city.name.strip())

# Estado (preferir sigla)

if location.state:

state_text = location.state.acronym or location.state.name

if state_text:

parts.append(state_text.strip())

# País

if location.country and location.country.name:

parts.append(location.country.name.strip())

except (AttributeError, TypeError):

return None

return ", ".join(parts) if parts else None

location_str = self._format_location_parts(institution.location, separator=" - ")

if location_str:

parts.append(location_str)

except (AttributeError, TypeError):

# Fallback para string simples

return str(affiliation) if affiliation else None

return " - ".join(parts) if parts else None

def _format_location_parts(self, location, separator=", "):

"""

Helper to format location as "City, State, Country" or with custom separator.

Returns None if location is not valid.

"""

if not location:

return None

parts = []

try:

# Cidade

if location.city and hasattr(location.city, 'name') and location.city.name:

parts.append(location.city.name.strip())

# Estado (preferir sigla)

if location.state:

state_text = location.state.acronym or location.state.name

if state_text:

parts.append(state_text.strip())

# País

if location.country and location.country.name:

parts.append(location.country.name.strip())

except (AttributeError, TypeError):

return None

return separator.join(parts) if parts else None

def _format_place_location(self, location):

"""

Formata localização em string: "Cidade, Estado, País"

Args:

location: objeto Location

Returns:

str: "São Paulo, SP, Brasil"

"""

return self._format_location_parts(location, separator=", ")

Copilot · 2025-11-12T12:09:48Z

article/search_indexes.py

+
+    def prepare_mods_part_elocation(self, obj):
+        """
+        elocation-id (para artigos sem paginação tradicional)


[nitpick] Inconsistent capitalization in comment: "elocation-id" starts with lowercase while all other field type comments in this section use title case or proper capitalization (e.g., "Página inicial do artigo", "ISSN da versão impressa"). Consider using "Elocation-id (para artigos sem paginação tradicional)" for consistency.

Suggested change

elocation-id (para artigos sem paginação tradicional)

Elocation-id (para artigos sem paginação tradicional)

Copilot · 2025-11-12T12:09:49Z

article/search_indexes.py

+            Exemplo: "e370704"
+        """
+        # Só retorna elocation se NÃO houver paginação tradicional
+        if not obj.first_page and obj.elocation_id:


The logic for elocation_id returns None if first_page exists, but doesn't check if first_page is actually a valid/non-empty value. If first_page is an empty string or whitespace-only, the method will return None even though there's a valid elocation_id. Consider checking: if not obj.first_page or not str(obj.first_page).strip() instead of just if not obj.first_page.

Suggested change

if not obj.first_page and obj.elocation_id:

if (not obj.first_page or not str(obj.first_page).strip()) and obj.elocation_id:

Copilot · 2025-11-12T12:09:49Z

article/search_indexes.py

+        if not (obj.journal and hasattr(obj.journal, 'publisher_history') and
+                obj.journal.publisher_history.exists()):


[nitpick] Complex nested condition is hard to read. The condition spans lines 1444-1445 and checks three levels deep. Consider extracting to a helper variable for better readability:

has_publisher_history = (obj.journal and hasattr(obj.journal, 'publisher_history') and obj.journal.publisher_history.exists()) if not has_publisher_history: return publishers

Suggested change

if not (obj.journal and hasattr(obj.journal, 'publisher_history') and

obj.journal.publisher_history.exists()):

has_publisher_history = (

obj.journal and hasattr(obj.journal, 'publisher_history') and obj.journal.publisher_history.exists()

)

if not has_publisher_history:

Copilot · 2025-11-12T12:09:49Z

article/search_indexes.py

+            if pub_name and pub_name not in publishers:
+                publishers.append(pub_name)


[nitpick] Missing strip() call on comparison. Line 1474 checks if pub_name and pub_name not in publishers but doesn't call .strip() on pub_name before the comparison, while it was stripped when building it (lines 1456, 1469). If pub_name somehow contains only whitespace after stripping during construction (which would make it falsy), this could theoretically pass the if pub_name check. However, since the strings are already stripped during construction, this is likely safe but inconsistent with the defensive pattern used elsewhere.

Suggested change

if pub_name and pub_name not in publishers:

publishers.append(pub_name)

if pub_name:

pub_name = pub_name.strip()

if pub_name and pub_name not in publishers:

publishers.append(pub_name)

- Extrai métodos auxiliares para eliminar duplicação de código - Adiciona validação de datas com verificação de ranges (mês 1-12, dia 1-31) - Otimiza queries de ORCID com Prefetch e select_related - Usa set para coleta de ORCIDs (O(1) vs O(n) em lookups) - Remove verificações hasattr redundantes em blocos try-except - Adiciona variáveis intermediárias para condições complexas - Valida valores vazios/whitespace antes de comparações

robertatakenaka · 2025-11-12T19:17:58Z

article/search_indexes.py

 from haystack import indexes
 from legendarium.formatter import descriptive_format
+from django.db.models import Prefetch
+from researcher.models import ResearcherAKA


@Rossi-Luciano não vai precisar de ResearcherAKA

robertatakenaka · 2025-11-12T19:22:28Z

article/search_indexes.py

+            )
+        ).all()
+
+        for researcher in researchers:


@Rossi-Luciano consulte o modelo Article. Veja como é a relação m2m com Researcher. Consulte o modelo Researcher. Veja que ele tem property orcid:

core/researcher/models.py

Line 77 in b48e0d7

def orcid(self):

robertatakenaka · 2025-11-12T19:25:14Z

article/search_indexes.py

+        EXEMPLO XML (MODS 3.7):
+        <name type="personal">
+            <namePart>Silva, João</namePart>
+            <nameIdentifier type="orcid" authority="orcid">
+                0000-0001-2345-6789
+            </nameIdentifier>
+            <role>
+                <roleTerm type="text" authority="marcrelator">author</roleTerm>
+            </role>
+        </name>


@Rossi-Luciano como a partir de uma lista de orcid será possível associar cada orcid ao autor correspondente corretamente?

robertatakenaka · 2025-11-12T19:31:15Z

article/search_indexes.py

+                thematic_area = thematic_area_journal.thematic_area
+
+                # Usar hierarquia: level2 > level1 > level0
+                topic_text = None


@Rossi-Luciano qual o motivo deste critério de escolha das áreas? Por que não foi usado todos os níveis?

robertatakenaka · 2025-11-12T19:34:45Z

article/search_indexes.py

+        if obj.issue and obj.issue.volume:
+            return str(obj.issue.volume).strip()
+        return None


@Rossi-Luciano troque por:

try: return str(obj.issue.volume).strip() except (AttributeError, TypeError, ValueError): return None

robertatakenaka · 2025-11-12T19:35:10Z

article/search_indexes.py

+        if obj.issue and obj.issue.number:
+            return str(obj.issue.number).strip()
+        return None
+


@Rossi-Luciano veja comentário anterior

robertatakenaka · 2025-11-12T19:35:37Z

article/search_indexes.py

+            str: Designação do suplemento ou None
+            Exemplo: "suppl.1"
+        """
+        if obj.issue and obj.issue.supplement:


@Rossi-Luciano comentário anterior

robertatakenaka · 2025-11-12T19:38:25Z

article/search_indexes.py

+        has_publisher_history = (
+            obj.journal
+            and hasattr(obj.journal, "publisher_history")
+            and obj.journal.publisher_history.exists()
+        )


@Rossi-Luciano elimine os códigos que testem o .exists() porque isso é uma consulta. Eliminando isso, as consultas ao banco de dados caem pela metade.

robertatakenaka · 2025-11-12T19:43:14Z

article/search_indexes.py

+
+        parts = []
+
+        try:


@Rossi-Luciano observe que nos próprios modelos este tipo de questão já está resolvida:

core/location/models.py

Line 554 in b48e0d7

def formatted_location(self):

robertatakenaka

@Rossi-Luciano Por favor, fiz alguns comentários que devem se estender a outros casos não comentados. Fazer as correções.

Copilot

Pull Request Overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 4 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-18T18:16:18Z

article/search_indexes.py

+            if official.issn_print and official.issn_print not in issns:
+                issns.append(official.issn_print)
+
+            if official.issn_electronic and official.electronic not in issns:


There's a typo in the attribute name. Line 1038 uses official.electronic but should be official.issn_electronic to check for duplicates correctly. This will cause the condition to fail since electronic is not a valid attribute.

Suggested change

if official.issn_electronic and official.electronic not in issns:

if official.issn_electronic and official.issn_electronic not in issns:

Copilot · 2025-11-18T18:16:19Z

article/search_indexes.py

+        """..."""
        if obj.researchers:
            researchers = obj.researchers.select_related("person_name").filter(
                person_name__isnull=False
            )
-            return set([str(researcher.person_name) for researcher in researchers])
+            return list(set([str(researcher.person_name) for researcher in researchers]))
+        return []

    def prepare_collab(self, obj):
        """This is the instituional author."""
        if obj.collab:
-            return set([collab.collab for collab in obj.collab.all()])
+            return list(set([collab.collab for collab in obj.collab.all()]))
+        return []

    def prepare_kw(self, obj):
        """The keywords of the article."""
        if obj.keywords:
-            return set([keyword.text for keyword in obj.keywords.all()])
+            return list(set([keyword.text for keyword in obj.keywords.all()]))
+        return []

    def prepare_description(self, obj):
-        """The abstracts of the articles
-        This is a property that filter by article ``DocumentAbstract.objects.filter(article=self)``
-        """
+        """The abstracts of the articles..."""


[nitpick] The docstrings for several methods have been reduced to just "..." which loses important documentation. Consider keeping the original docstrings or providing meaningful descriptions. For example, prepare_creator previously explained the select_related optimization, and prepare_description explained the data source.

Copilot · 2025-11-18T18:16:19Z

article/search_indexes.py

+    def prepare_mods_subject_area(self, obj):
+        """..."""
+        areas = []
+
+        # Padronizado: .exists() direto
+        if obj.journal and obj.journal.subject.exists():
+            for subject_area in obj.journal.subject.all():
+                if subject_area.value and subject_area.value.strip():
+                    areas.append(subject_area.value.strip())
+
+        return areas
+
+    def prepare_mods_subject_wos(self, obj):
+        """..."""
+        wos_categories = []
+
+        # Padronizado: .exists() direto
+        if obj.journal and obj.journal.wos_area.exists():
+            for wos_category in obj.journal.wos_area.all():
+                if wos_category.value and wos_category.value.strip():
+                    wos_categories.append(wos_category.value.strip())
+
+        return wos_categories


[nitpick] The docstrings for prepare_mods_subject_area and prepare_mods_subject_wos are abbreviated to "..." while other similar methods have comprehensive documentation. For consistency and maintainability, these methods should have full docstrings explaining their purpose, data sources, and MODS mapping like the other methods in this section.

Copilot · 2025-11-18T18:16:19Z

article/search_indexes.py

-                return ["com_%s" % col for col in obj.collections]
+            try:
+                return ["com_%s" % col.acron3 for col in obj.collections if col.acron3]
+            except Exception:


[nitpick] Using a bare except Exception: can hide unexpected errors and make debugging difficult. Consider catching specific exceptions like AttributeError or TypeError that might occur when accessing col.acron3. This makes the error handling more explicit and maintainable.

Suggested change

except Exception:

except (AttributeError, TypeError):

Rossi-Luciano added 27 commits November 11, 2025 12:34

Adiciona campos complementares adequados ao padrão MODS

98dd1de

Adiciona 'prepare_mods_name_text'

6059bb8

Adiciona 'prepare_mods_name_orcid'

57c8c65

Adiciona 'prepare_mods_name_affiliation'

de5fe1a

Adiciona 'prepare_mods_name_role'

80e5bfd

Adiciona 'prepare_mods_subject_keyword'

f2adc9b

Adiciona 'prepare_mods_subject_area'

14332b5

Adiciona 'prepare_mods_subject_wos'

7cd3cd1

Adiciona 'prepare_mods_subject_capes'

5de5d51

Adiciona 'prepare_mods_relateditem_host_title'

c6a7028

Adiciona 'prepare_mods_relateditem_host_issn'

b404ba8

Adiciona 'prepare_mods_relateditem_host_volume'

5b8bf29

Adiciona 'prepare_mods_relateditem_host_issue'

a11a9eb

Adiciona 'prepare_mods_relateditem_host_supplement'

cdeb223

Adiciona 'prepare_mods_part_page_start'

1814cf8

Adiciona 'prepare_mods_part_page_end'

4e038d8

Adiciona 'prepare_mods_part_elocation'

9b59d18

Adiciona 'prepare_mods_identifier_issn_print'

475723c

Adiciona 'prepare_mods_identifier_issn_electronic'

de7f71b

Adiciona 'prepare_mods_identifier_issnl'

995eb4c

Adiciona 'prepare_mods_origininfo_publisher'

072621d

Adiciona 'prepare_mods_origininfo_place'

658f825

Adiciona 'prepare_mods_origininfo_date'

d99c627

Adiciona 'prepare_mods_accesscondition_license'

297110b

Adiciona 'prepare_mods_accesscondition_licenseurl'

f79b2c0

Adiciona 'prepare_mods_accesscondition_openaccess'

a5a18aa

Adiciona métodos auxiliares privados

e90a5cc

Rossi-Luciano requested a review from robertatakenaka November 11, 2025 15:57

robertatakenaka requested a review from Copilot November 12, 2025 12:03

Copilot started reviewing on behalf of robertatakenaka November 12, 2025 12:04 View session

Copilot finished reviewing on behalf of robertatakenaka November 12, 2025 12:07

Copilot AI reviewed Nov 12, 2025

View reviewed changes

Rossi-Luciano added 2 commits November 12, 2025 12:55

Aplica formatação (black)

91e6a58

robertatakenaka reviewed Nov 12, 2025

View reviewed changes

robertatakenaka requested changes Nov 12, 2025

View reviewed changes

Rossi-Luciano added 2 commits November 18, 2025 14:04

Refatora search_indexes

442a5dc

Complementa search_indexes

77624a7

robertatakenaka requested a review from Copilot November 18, 2025 18:11

Copilot started reviewing on behalf of robertatakenaka November 18, 2025 18:12 View session

Copilot finished reviewing on behalf of robertatakenaka November 18, 2025 18:15

Copilot AI reviewed Nov 18, 2025

View reviewed changes

Rossi-Luciano added 2 commits December 6, 2025 18:28

Retorna search_indexes.py ao estado inicial

9aa77b1

Modifica article_compile.txt para considerar MODS

1d86b5d

Rossi-Luciano closed this Dec 7, 2025

	elocation-id (para artigos sem paginação tradicional)
	Elocation-id (para artigos sem paginação tradicional)

	if not obj.first_page and obj.elocation_id:
	if (not obj.first_page or not str(obj.first_page).strip()) and obj.elocation_id:

		if not (obj.journal and hasattr(obj.journal, 'publisher_history') and
		obj.journal.publisher_history.exists()):

		if pub_name and pub_name not in publishers:
		publishers.append(pub_name)

	if official.issn_electronic and official.electronic not in issns:
	if official.issn_electronic and official.issn_electronic not in issns:

feat: Add MODS metadata fields to complement Dublin Core in ArticleOAIIndex #1213

feat: Add MODS metadata fields to complement Dublin Core in ArticleOAIIndex #1213

Uh oh!

Conversation

Rossi-Luciano commented Nov 11, 2025

O que esse PR faz?

Onde a revisão poderia começar?

Como este poderia ser testado manualmente?

Algum cenário de contexto que queira dar?

Quais são tickets relevantes?

Referências

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

robertatakenaka left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Uh oh!

Copilot AI Nov 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 18, 2025

Choose a reason for hiding this comment

Uh oh!