kerchner
commented
3 months ago Note that as of https://github.com/samvera/bulkrax/commit/0de8ee06115ff9e6e89177d93c407826ae892a7f , the following issues in Bulkrax that we need have been fixed/enhanced:
- Ability to write CSV with separate lines for parent work and child FileSets
- Ability to set embargo dates and visibility status in the CSV, for individual items (whether they are works, FileSets, etc.) as follows:
| visibility | visibility_during_embargo | embargo_release_date | visibility_after_embargo | |
|---|---|---|---|---|
| embargo | restricted | 4/19/2024 | open |
The constraint here is that Bulkrax does not appear to be equipped to set embargo statuses -- and certainly not different status for a work's metadata versus its files, as is our practice in GW ScholarSpace. This was confirmed in 2023 via Slack conversation w/Bulkrax developers. Consider contributing an enhancement to Bulkrax to implement this. Alternatively, load ETDs via bulkrax as private, followed by setting embargo statuses, followed by setting visibility to public.