There's no easy way to export an individual NOFO object or to import one (other than using a Word document).
Exporting a NOFO from prod and then importing locally would make debugging much easier. It should only be available for superadmin users, (not just anyone with a NOFO builder account). It would make sense if this was something we could do through the admin UI (/admin), not the regular UI (that uses USWDS).
Probably the best would be to export it as a JSON file to set us up for a future where the NOFO Builder has an API as well. In our future API, we probably don't want every data element, but for admin exports we definitely do.
Note: Disregard any of the audit logs that come with the NOFO, as we typically don't use those for anything.
Summary
There's no easy way to export an individual NOFO object or to import one (other than using a Word document).
Exporting a NOFO from prod and then importing locally would make debugging much easier. It should only be available for superadmin users, (not just anyone with a NOFO builder account). It would make sense if this was something we could do through the admin UI (
/admin), not the regular UI (that uses USWDS).Probably the best would be to export it as a JSON file to set us up for a future where the NOFO Builder has an API as well. In our future API, we probably don't want every data element, but for admin exports we definitely do.
Note: Disregard any of the audit logs that come with the NOFO, as we typically don't use those for anything.
This story requires: