Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[For discussion] Improvements to NOFO reimporting #125

Open
pcraig3 opened this issue Dec 19, 2024 · 0 comments
Open

[For discussion] Improvements to NOFO reimporting #125

pcraig3 opened this issue Dec 19, 2024 · 0 comments

Comments

@pcraig3
Copy link
Collaborator

pcraig3 commented Dec 19, 2024

This is a proto-story, not yet a story. It's a place to capture the discussion around reimporting.

So, one of our users mentioned that reimporting causes lost work, and if there is anything we can do about this.

When a NOFO is re-imported, the sections and subsections are completely recreated and assigned to the current NOFO object. This means that anything that's in the existing NOFO is completely wiped out by the re-import action.

I pulled some data to validate this need and saw that there is a pretty healthy amount of re-importing going on, although it is heavily concentrated in our non-Bloom users.

Some numbers for you:

total reimports (since Nov 8) 209
Bloom users reimports 57
Other users reimports 148
Highest re-imports for a single user 41 (8 individual NOFOs)
Unique NOFOs reimported 46
Average re-imports per NOFO listed 4.5
Highest re-imports for a single NOFO 17 (HRSA-25-061)
NOFOs reimported or not since Nov 7th 46 reimported; 27 not reimported

So it seems like there is reason here to try and address this in some way.

Preference goes to ideas that are easy to do.

Here are some easy ideas:

  • Get list of all subsections that have been modified since import (could display in a list like broken links)
  • Offer to create a new NOFO when there are modified subsections instead of overwriting current NOFO
  • Copy over metadata onto matching subsections.
    • For example: if we find a subsection with the same name in the same section, and it has a "page break" or "callout box" applied, we should carry that over to the new subsection

Here is a medium-effort idea:

  • If there are changed subsections, offer 3 options:

      1. Overwrite everything (current behaviour)
      1. Create a copy of this NOFO, do not overwrite it. You can manage replacing the content.
      1. Try to replace body content from subsections in new NOFO with body content of matching edited subsection in current object. (We would have to match subsections on matching section + subsection name, so this could still lose data).
@pcraig3 pcraig3 changed the title Improvements to NOFO reimporting [WIP] Improvements to NOFO reimporting Dec 19, 2024
@pcraig3 pcraig3 changed the title [WIP] Improvements to NOFO reimporting [For discussion] Improvements to NOFO reimporting Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant