Skip to content

Populate coverage_depth field with "fulltext" in KBART export#78

Merged
robertatakenaka merged 3 commits intomasterfrom
copilot/add-fulltext-value-coverage-depth
Feb 3, 2026
Merged

Populate coverage_depth field with "fulltext" in KBART export#78
robertatakenaka merged 3 commits intomasterfrom
copilot/add-fulltext-value-coverage-depth

Conversation

Copy link
Contributor

Copilot AI commented Feb 3, 2026 •
edited
Loading

EBSCO requested KBART compliance: the coverage_depth column must indicate "fulltext" for journals with full-text content per NISO RP-9-2014 guidelines. Currently returns empty string for all journals.

Changes

  • export/kbart.py:162: Set coverage_depth to "fulltext" for all journals (all SciELO journals provide full text)
  • export/kbart.py:164: Fix publisher_name to return '' instead of [] when empty (prevents type error in CSV generation)
# Before
line.append('')  # coverage_depth
line.append(' '.join(data.publisher_name) if data.publisher_name else [])

# After
line.append('fulltext')  # coverage_depth
line.append(' '.join(data.publisher_name) if data.publisher_name else '')
Original prompt

This section details on the original issue you should resolve

<issue_title>Incluir valor "fulltext" no campo coverage_depth do KBART</issue_title>
<issue_description>A EBSCO solicitou ajustes no KBART, para que estejam compatíveis com as diretrizes do KBART.

Incluir valor fulltext no campo coverage_depth. Como todos os periódicos possuem texto completo, então o ajuste pode ser aplicado para todos.

Mensagem original da EBSCO:
The coverage_depth column is blank in the files I checked. Would it be possible to supply it with “fulltext” listed for all journals that have fulltext content?</issue_description>

Comments on the Issue (you are @copilot in this section)

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 2 commits February 3, 2026 20:31
@robertatakenaka
Add 'fulltext' value to coverage_depth field in KBART export
2d92baf 
Co-authored-by: robertatakenaka <505143+robertatakenaka@users.noreply.github.com>
@robertatakenaka
Fix publisher_name field to return empty string instead of empty list
6073a33 
Co-authored-by: robertatakenaka <505143+robertatakenaka@users.noreply.github.com>
Copilot AI changed the title [WIP] Incluir valor 'fulltext' no campo coverage_depth do KBART Populate coverage_depth field with "fulltext" in KBART export Feb 3, 2026
Copilot AI requested a review from robertatakenaka February 3, 2026 20:34
@robertatakenaka robertatakenaka marked this pull request as ready for review February 3, 2026 20:50
Copilot AI review requested due to automatic review settings February 3, 2026 20:50
@robertatakenaka robertatakenaka merged commit 96efef2 into master Feb 3, 2026
2 checks passed
Copilot AI reviewed Feb 3, 2026
View reviewed changes
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the KBART export functionality to comply with NISO RP-9-2014 guidelines as requested by EBSCO. The changes ensure proper values are populated in the coverage_depth field and fix a type error in publisher_name handling.

Changes:

  • Populate coverage_depth field with "fulltext" for all journals (all SciELO journals provide full-text content)
  • Fix publisher_name to return empty string instead of empty list when no publisher name exists (prevents type error during CSV generation)

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@robertatakenaka robertatakenaka Awaiting requested review from robertatakenaka

Assignees

@robertatakenaka robertatakenaka

Copilot code review Copilot

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Incluir valor "fulltext" no campo coverage_depth do KBART

2 participants

@robertatakenaka