[3] Enable CSV parser enabled in Bulkrax

[DiemBTran]

Summary

The librarians would like to use a CSV parser to import works, and would like that to be enabled in Bulkrax.

Acceptance Criteria

• [ ] CSV Parser is available as a selection option for importers.

Note: this originally had the acceptance criteria of "CSV Parser is enabled in Bulkrax for new mappings". However in conversations during 2022-10-24 sprint planning, we acknowledged that both the CSV parser and the OAI QDC parser would have the same mappings. The mappings are tracking in scientist-softserv/adventist-dl#152 ([3]DC term metadata mapping) and the OAI QDC parsing is tracking in scientist-softserv/adventist-dl#182 ([5] Fix OAI QDC import). The idea being that if we get the mapping right for the CSV parser we get the mapping right for the OAI QDC parser.

Screenshots or Video

Testing Instructions

Notes

Confused how to fill this out? Check out the playbook

[DiemBTran]

Linked items:

Relates to:

• Epic: CSV Importer that accepts DC

[DiemBTran]

Related MRs:

• Enabling the CSV Parser !202

[DiemBTran]

Jeremy Oct 2022:

---

At present we have a custom OAI QDC Parser that could likely be removed in favor of the latest Bulkrax parser. Restoring the CSV Parser looks to be an adjustment of the ./config/initializers/bulkrax.rb.

[DiemBTran]

This passes SoftServ QA: See attached screenshot.

tested on:

• https://sdapi.s2.adventistdigitallibrary.org/importers/new?locale=en

---

In the drop-down for parsers, you should see two options:

• [x] "OAI - Adventist Digital Library"
• [x] "CSV - Comma Separated Values"

CSV and OAI parsers are enabled in Bulkrax. Mappings will be addressed in scientist-softserv/adventist-dl#152([3]DC term metadata mapping)

[DiemBTran]

Needs further review:

1. When selecting the Parser, selecting CSV should not display the Parser, Base url, Metadata prefix, or Set (source) fields. Those fields should only display for OAI parsers
2. Visibility, Rights statement, and Override rights statement appear twice on the form.

per the slack conversation, this should not be. jeremy stated that the fix is most likely in main but not pushed to staging yet.

[KatharineV]

Looks good on staging and production.